290 likes | 301 Views
Migrating to Citrix MetaFrame XP via Interoperability Mode. Patrick Boucher & David Hart Systems Engineers – Northeast & Southern Regions Citrix Systems Inc. Agenda. Identify different migration strategies Interoperability Mode Client Considerations Useful Tools and Tips Questions.
E N D
Migrating to Citrix MetaFrame XP via InteroperabilityMode Patrick Boucher & David Hart Systems Engineers – Northeast & Southern Regions Citrix Systems Inc.
Agenda • Identify different migration strategies • Interoperability Mode • Client Considerations • Useful Tools and Tips • Questions
Migration Methodology • Analysis • Design • Build and Test • Rollout Technical Breakout: • Process for Migrating to Citrix MetaFrame XP
Migration Option 1 - Flash • Create a New XP Server Farm with Clean System Installs • Why? • Re-deploy or re-configure application installations • Implementation of a new architecture • Allows for use of native IMA communication and access to full MF XP feature set during migration • “Clean” system migration • How? • Install OS, MF XP, and applications on existing or new hardware • Create XP Farm and join new servers to the Farm • Considerations: • Application access and load balancing will not work across 1.8 Farm and new XP Farm during migration • Web Interface could be leveraged to assist with this process • Automated Server Builds could help speed migration
Migration Option 2 - Parallel • Migrate Existing MF 1.8 Servers to a New XP Server Farm • Why? • Keep existing application deployments • Allows for use of native IMA communication and access to full MF XP feature set during migration • How? • During migration create a new MF XP Farm • Migrate existing 1.8 servers and join them into the new XP Farm • Considerations: • Application access and load balancing will not work across 1.8 Farm and new XP Farm during migration. Load balancing will work within each Farm • Web Interface could be leveraged to assist with this process Technical Breakout: • Technical Analysis of Parallel Mode Migration from MetaFrame 1.8 to MetaFrame XP
Migration Option 3 - Interoperability • Migrate Existing MF 1.8 Server Farm • Why? • Use existing servers in the server farm during migration • How? • During migration create a MF XP Farm with the same name as 1.8 Server Farm • Migrate servers one at a time while the Farm is on line • Considerations • Existing MF 1.8 applications will be migrated to XP • Applications will be load balanced across XP and 1.8 Farms • Both 1.8 traffic and XP IMA traffic will exist on network Interoperability mode is designed to facilitate migration to MetaFrame XP; it is not designed to be a permanent solution
What is Interoperability Mode • Legacy services installed • XP servers to 1.8 servers • Program Neighborhood • ICA Browser • One application set
What is Interoperability Mode (cont.) • Load balancing across all servers • Master ICA Browser • XP Server by default • 1.8 ICA license gateways disabled • 1.8 ICA gateways supported • ICA Client broadcasts • ICA Browser Server responds • 1.8 and XP servers in Interop mode • License pooling • Between XP and 1.8 servers • Must be on same subnet
Use Interoperability Mode to: • Migrate users to a XP farm seamlessly • Migrate only, NOT a permanent solution • Emulate the services used by MetaFrame 1.8
Interoperability Mode provides support for: • Migrating ONE MetaFrame 1.8 Farm • Required 1.8 and XP farms have same farm name • Farm name is not case sensitive • Published application migration • Command for published application is greater than 256 characters • HKLM\System\CurrentControlSet\Control\Citrix\ManagedApplications\AppName\ServerName • Working directory for the published application is greater than 256 characters • HKLM\System\CurrentControlSet\Control\Citrix\ManagedApplications\AppName\ServerName\WorkDirectory • Application load balancing • Basic subnet license pooling • Program neighborhood client connections
MetaFrame 1.8Architecture Client Components Server Side Other PN Srvrs (named pipe) MetaFrame 1.8 Architecture Local NT Registry XML Svc Web Interface PN Svc PN Named Pipe HTTP & XML PN Virtual Channel HTTP ICA Browser ICA Client UDP 1604 UDP 1604 QServer AppCfg NT Reg (remote regedt) WinstationAPI (RPC) Termsrv MFAdmin
MetaFrame XP Architecture Client Components Server Side Other IMA Srvrs (TCP) MetaFrame XP (Native Mode) Web Interface XML Svc IMA Svc TCP HTTP & XML HTTP PN Virtual Channel ICA Client TCP CMC
Client Components Client Components Server Side Other PN Srvrs (named pipe) Other IMA Srvrs (TCP) XML Svc XML Svc TCP PN Named Pipe Web Interface Web Interface Local NT Registry IMA Svc PN Svc HTTP & XML HTTP & XML HTTP HTTP PN Virtual Channel PN Virtual Channel ICA Client ICA Client UDP 1604 ICA Browser UDP 1604 QServer CMC TCP NT Reg (remote regedt) AppCfg WinstationAPI (RPC) MFAdmin Termsrv Architecture of Interoperability-Mode
Running in Interoperability Mode • Requires two sets of tools • Published Application Manager • Load Balance Manager • Resource Manager • Installation Manager • Citrix MetaFrame Management Console • Published Application list should be static • Editing/viewing will break load balancing • New applications MUST be published first in PAM, then within the CMC
Get to Native Mode and take full advantage • Increased farm scalability and stability • Advanced printer management • Active Directory UPN support • Centralized control and Management • Simplified license management and activation • Mlicense.exe • Improved ICA protocol
Web Interface • Web Interface Migration • Web Interface 1.5 minimum • Leverages XML Port • Simplest Migration
Program Neighborhood Program Neighborhood Migration • Propagate TCP/IP + HTTP changes to PN Client OR • Force Native XP servers to respond to broadcasts
QPRINTER qprinter [/replica][/imprmapping mappingfilename] • /replica • Displays all the current print driver replication entries queued for distribution and not yet completed • /imprmapping mappingfilename • Imports printer mappings from the file specified by mappingfilename into the data store • Located in the \support\debug\i386 folder on the Citrix MetaFrame XP media
QUERY LICENSE query license [/server:servername | /all] [/?] • /server:servername • The Citrix server to be queried. The default is the current Citrix server. • /all • Displays information about all licenses on the network.
QUERY SERVER • query server • /license • Displays user licenses • /app • Displays application names and server load • /gateway • Displays configured gateway addresses • /serverfarm • Displays server farm names and server load • /load • Displays load data on selected server
Where to go from here? • MetaFrame XP migration documentation • Migrating from MetaFrame 1.8 to MetaFrame XP (CCS) • Advanced Concepts for MetaFrame XP 1.0 Guide • MetaFrame XP 1.0 Administrator’s Guide • Citrix MetaFrame XP Migration and Upgrade Guide • Planning Your MetaFrame XP Deployment • Citrix Solutions Knowledgebase & Support • http://www.citrix.com/support
TM Citrix Authorized Training • With Citrix training: • Learn tips and techniques for managing and administering Citrix software • Obtain valuable lab time for hands-on practice • Prepare for Citrix certification exams • Learn quickly and efficiently in the classroom • New courses and certification include: • CTX-7201 MetaFrame Secure Access Manager • CTX-6100 Citrix Core Technologies and Architecture • Citrix Certified Integration Architect (CCIA) program to be launched in Q4 2003 • Available worldwide from 350 Citrix Authorized Learning Centers (CALCs) • To find a CALC near you, go to Training Locations from www.citrix.com/training