1 / 43

Technical Analysis of Parallel Mode Migration from MetaFrame 1.8 to MetaFrame XP

Learn about the technical architecture variances, migration strategies, and benefits of migrating from MetaFrame 1.8 to MetaFrame XP in parallel mode. Discover why migrating to MetaFrame XP can enhance enterprise scalability, reduce network traffic, streamline management, and save costs.

virginiamathis
Download Presentation

Technical Analysis of Parallel Mode Migration from MetaFrame 1.8 to MetaFrame XP

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Technical Analysis of Parallel Mode Migration fromMetaFrame 1.8 to MetaFrame XP David Hart & Patrick Boucher Systems Engineers – Southern & Northeast Regions Citrix Systems Inc.

  2. Non Disclosure Agreement • This presentation is confidential. By virtue of your relationship with Citrix, you are bound to retain in confidence all information in this presentation.

  3. Learning Objectives • Understand technical architecture differences between MetaFrame 1.8 and MetaFrame XP • Overview different migration strategies • Understand how MetaFrame 1.8 and MetaFrame XP work in parallel migration • Bridging different MetaFrame XP and 1.8 Farms using the Web interface for MetaFrame XP

  4. Agenda • Customer hesitations regarding MetaFrame XP • Why migrate to MetaFrame XP? • Architecture - MetaFrame 1.8 vs. MetaFrame XP • Migration strategies overview • Focus on Native-Mode Parallel Migration • MetaFrame XP migration methodology • Tech Tips for successful Parallel-Mode Migration • MetaFrame XP technical migration resources

  5. Customer Hesitations Regarding MetaFrame XP Some reasons users choose not to migrate MetaFrame 1.8

  6. After the MetaFrame XP TCO and ROI Pitch • If it’s not broke, why fix it? • No longer have Subscription Advantage • We will wait until Windows 2000->2003 • Web applications will replace MetaFrame XP • We tried the 90-day evaluation with no luck

  7. Why Migrate to MetaFrame XP? • Increased enterprise farm scalability and stability • Less server-to-server network traffic • Centralized control with the Management Console for MetaFrame XP • Integrated advanced management capabilities • Simplified license management and activation • Printer management & driver replication • Delegated Administration • User Policy Support • Application-based Load Management • License Pooling • MetaFrame XP Server for Windows with Feature Release 3 prepares for Microsoft Server 2003 Less Administration =$Saved Money$

  8. Technical ArchitectureMetaFrame 1.8 vs. MetaFrame XP MetaFrame XP – Built for the Enterprise

  9. MetaFrame 1.8 Farm MetaFrame XP Farm MetaFrame 1.8 & XP Farms • Server Farms in MetaFrame 1.8 are collection of servers on a given network that may be managed as single unit • Server Farms in MetaFrame 1.8 may also be defined by sharing common Program Neighborhood • Server Farm in MetaFrame XP defines Scope of Management • MetaFrame XP farms operate across enterprise network via Independent Management Architecture

  10. Independent Management Architecture (IMA) • Single point of access for information and control of MetaFrame XP Components • Infrastructure for remote administration of Server Farms • Single management interface supporting current and future administration abilities • Extensible and supportable server to server communications architecture

  11. The Management Console MetaFrame XP Windows2000 Server Windows Server 2003 MetaFrame XP NT 4.0 TSE Independent Management Architecture DB LoadManager Installation Manager Resource Manager Security Services • Central Data Store • SQL, Oracle, Access, MSDE MetaFrame XP IMA Backbone

  12. MB MB MB MF Admin MF Admin MF Admin Farm Management with MetaFrame 1.8 Server Farm Scope Subnet 10.1.X.X Subnet 10.2.X.X Subnet 10.3.X.X

  13. DC DC TheManagement Console Farm Management for MetaFrame XP CrossMultiple Subnets Zone 1 Zone 1 Subnet 10.1.X.X Subnet 10.2.X.X Data Collector for each Zone Zone 2 Data Store Central Data Store for Farm Information Subnet 10.3.X.X

  14. Improved ICA Performance

  15. MetaFrame XPNative-Mode and Interoperability-Mode UnderstandingMetaFrame XP Operation Modes with MetaFrame 1.8

  16. MetaFrame XP Native Mode • Server to server communication via IMA Service communicates over TCP port 2512 • Program Neighborhood service and ICA Browser service for MetaFrame 1.8 disabled • The Web Interface for MetaFrame XP communicates over TCP port 2513 • MetaFrame XP connection licenses not pooled with MetaFrame 1.8 servers • Network utilization more efficient because ICA Browser traffic not broadcast-based

  17. MetaFrame XP Interoperability-Mode • MetaFrame XP and MetaFrame 1.8 Servers interoperate when Interoperability-Mode enabled • Legacy Program Neighborhood service and ICA Browser service enabled on MetaFrame XP • Servers communicate over UDP Port 1604 for MetaFrame 1.8 communication • MetaFrame XP communication is IMA protocol over TCP port 2512

  18. Remind Your Customers Interoperability-Mode Is NOT designed to be a permanent solution!

  19. Native-Mode Architecture The Web Interface for MetaFrame XP Other IMA Servers (TCP2512) HTTP XML Svc HTTP & XML IMA Service TCP80 ICA Client PN Virtual Channel TCP 2513 The Management Console

  20. Interoperability-Mode Architecture The Web Interface for MetaFrame XP Other IMA Srvrs (TCP) Other PN Srvrs (named pipe) HTTP XML Svc PN Named Pipe HTTP & XML Local W2K/NT Registry PN Service PN Virtual Channel ICA Client UDP 1604 ICA Browser Service QServer UDP 1604 IMA Service AppCfg The ManagementConsole TCP 2513 NT Reg (remote regedt) MFAdmin Termsrv Winstation API (RPC)

  21. Migration Strategies Anatomy of MetaFrame 1.8 to MetaFrame XP Migration

  22. Migration Strategies • Flash Upgrade • Interoperability-Mode Migration • Incremental in-place migration • Parallel Migration • Migrate several existing MF 1.8 Servers to new MetaFrame XP Server Farm • Create new MetaFrame XP Server Farm with clean System OS and service pack installs

  23. Flash Upgrade Flash Upgrade • All servers are upgraded to MetaFrame XP during scheduled maintenance window • Highly centralized and/or cloned server environments • Smaller or less critical server farms • Unattended and cloned installs for all but first server in an XP Farm (MSFT Access Data Store only) • See MF XP Administrator’s Guide and Advanced Concepts Guide

  24. Get all Technical Details onInteroperability-Mode Migration • Technical Breakout Session: Migrating to Citrix MetaFrame XP Server via Interoperability-Mode • Presenter: Patrick Boucher

  25. Parallel Migration – Technical Considerations • MetaFrame XP servers built/upgraded in Native-Mode • MetaFrame 1.8 and MetaFrame XP servers do not communicate • Possible additional hardware and licenses • Users may be manually migrated in proportion to servers and licenses • Publish MetaFrame 1.8 and MetaFrame XP applications to distinct user groups • Prevent redundant icons (if using the Web Interface) • MetaFrame XP applications published manually (the Management Console) rather than migrated

  26. Parallel Migration Advantages: • No Program Neighborhood and ICA Browser traffic when in Native-Mode • Potential issues with migrating publishedapplications are eliminated Disadvantages: • Published applications not available from one ProgramNeighborhood application set • Consider using the Web Interface for Windows XP • Servers that are migrated to MetaFrame XP will require published applications created and configured manually

  27. Consolidated Parallel Migration – Type I Migrate Existing MF 1.8 Servers to new XP Server Farm Consider when: • Keeping existing Published Application deployments • Use existing servers in Farm during migration • Allowing native IMA communication and access to full MetaFrame XP feature set during migration Process: • During migration create new MetaFrame XP Farm • Migrate existing MetaFrame 1.8 servers and join new MetaFrame XP Farm in Native Mode

  28. Scratch Parallel Migration – Type II New MetaFrame XP Server Farm - Clean System Installs Consider when: • Re-deploying published application installations • Potentially using new server hardware • Implementing Directory Services architecture - i.e. Active Directory (AD) Novell Directory Services (NDS) • Need for “Clean” system migration Process: • Install OS, MetaFrame XP, and applications on existing or new hardware (Scripted Install/Cloned) • Create new MetaFrame XP Farm and join new servers to Farm • Migrate existing Meta Frame 1.8 users to new MetaFrame XP Farm

  29. The Web Interface For MetaFrame XP: Bridging Technology The Web Interface hides complexity from end users. For migration, used to aggregate applications from multiple Farms • Citrix MetaFrame XP Server for Windows • Citrix MetaFrame 1.8 Server for Windows • Citrix MetaFrame Server, Version1.x, for UNIX Operating Systems Farm II Farm I the Web Interface Farm III Farm IV

  30. MetaFrame XP Migration Methodology Plan for the Future & Make it Work Today

  31. Citrix MetaFrame XP Migration Methodology • Test • Simulate production environment as closely as possible • Regression test applications • Scalability testing • End to end test of architecture • Pilot • Production users and systems • User acceptance and business sign-off • Rollout • Full production implementation • Change Management • Changes tested prior to implementation in production environment • Test -> Pilot -> Production (Always Document) • Clean up BEFORE migrating • Get clients to consistent level • A consistent stable environment will help to mitigate risk

  32. Tech Tips for Successful Parallel-Mode Migration Technical Points to Consider before Migrating to Citrix MetaFrame XP for Windows

  33. The Web Interface for MetaFrame XP • Requirements for Farm Bridging • The Web Interface for MetaFrame XP • Minimum Version 1.6x and Project Columbia 6.01.038 • Works, Not Supported by Citrix, www.citrix.com/cdn • Recommended Version released with Citrix MetaFrame XP Server for Windows with Feature Release 3 • Redundant Web Interface Servers with Network Load Balancing • The Web Interface pointing to MetaFrame XML servers • MetaFrame 1.8 Server: Master and Backup browsers with Citrix with Feature Release 1 and Service Pack 3 • MetaFrame XP Server with Feature Release 1 and Service Pack 3: Zone Data Collector and server set to “Most Preferred” • XML service on MetaFrame 1.8 and XP servers • Windows NT 4.0/2000 IIS share port 80 XML service • Recommend separate XML service port for troubleshooting

  34. Configure the Web Interface 1.6x with Project Columbia Aggregate multiple MetaFrame XP and MetaFrame 1.8 farms editing “config.txt” • %Rootdrive%\Inetpub\wwwroot\Portal\config ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; Configuring XML Services ; ; NFuse_Farm=Farm 1 name, 0, server1, server2, server3 NFuse_Farm=MetaFrame XP Farm,0,mfxp NFuse_Farm=MetaFrame 1.8 Farm,0,mf18 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; Syntax: NFuse_Farm=Farm-name, load-balance-flag, xml-addr[:xml-port][|ssl-addr[:ssl-port]] [, ...]

  35. Add Descriptive Farm Names Farm Application Enumeration Order Define Farm XML Servers and Load Balancing Configure the Web Interface with MetaFrame XP with Feature Release 3

  36. MetaFrame XP Native-Mode Security: Microsoft Active Directory (AD) • Citrix recommendations for Active Directory • Server farm is in a single AD forest • All MetaFrame XP servers reside in same domain • No trust relationships with non-AD domains • Use Domain Global Groups for published application and network printer access • Windows 2000 and/or Windows Server 2003 • User Principal Name (UPN) not supported by Windows NT Server 4.0 even with AD Services Interface • Else use AD - PDC Emulator in AD mixed mode for domainname\username login

  37. MetaFrame XP Application Migration MetaFrame 1.8 applications can fail to migrate Command for published application greater than 256 characters HKLM\System\CurrentControlSet\Control\Citrix\ManagedApplications\AppName\ServerName Working directory for the published application greater than 256 characters HKLM\System\CurrentControlSet\Control\Citrix\ManagedApplications\AppName\ServerName\WorkDirectory Publishing same applications to MetaFrame 1.8 and MetaFrame XP farms not recommended Switching back and forth between Native and Interoperability modes not recommended

  38. Simplified License Activation • Included with Citrix MetaFrame XP Server for Windows with Feature Release 3 • “mlicense” command line tool • Add and activate multiple licenses • Text file  xml file • xml file into CAS  xml file (activation codes) • xml file  activates licenses

  39. Simplified License Activation - continued CAS updated to support multiple license activations via license file upload New utility supports installation of multiple licenses via license file Lics. License activation file is processed by new utility and all licenses are activated Lics. Simplifying task of entering and activating many licenses * Licensing can be simplified to a few steps regardless of license SKU’s

  40. Miscellaneous Migration Tools & Tips • Migrate Installation Management Services 1.0b application packages deployed - MetaFrame 1.8 • Utility found on MF XP Installation Manager CD • \support\debug\i386\Im_app_upgrd.exe • Do not remap drive letters during upgrade if originally mapped during MetaFrame 1.8 install

  41. 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

  42. TM Citrix Authorized Training • With Citrix Training: • Learn tips and techniques for managing andadministering 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 Administration • CTX-6100 Citrix Core Technologies and Architecture • Citrix Certified Integration Architect (CCIA) program to be launched in Q4 2003 • Available Worldwide from 350 CALCs • Training Locations from www.citrix.com/training • MetaFrame XP Migration Course: • Citrix MetaFrame 1.8 to MetaFrame XP Course# CTX-1210

More Related