Anatomy of a MetaFrame 1.8 to MetaFrame Extended Platform Migration

1. Citrix Confidential

2. Anatomy of a MetaFrame 1.8 to MetaFrame Extended Platform Migration Randy Jacques, Senior Director - CCS Scott Thompson, Senior Architect - CCS

3. 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. Citrix Confidential

4. Non Disclosure Agreement • Please… • No Photography • No Audio Recording • No Video Recording • Please turn cell phones to vibrate (silent) Citrix Confidential

5. Agenda • Migrating from MF 1.8 to MF XP • Migration Methodology • Migration Options • Architecture Overview of Interoperability • Migration Process and Implementation Best Practices • Questions Citrix Confidential

6. Migration Methodology POC Analysis Design Test Pilot Rollout Citrix Confidential

7. Migration Methodology • Methodology for Upgrade of MF 1.8 to MF XP • Proof of Concept • Prove XP technical concept to the business • Analysis • Review existing infrastructure environment to identify potential risk areas and requirements for the migration • Determine scope of migration • Design • Determine future XP architecture • Identify migration strategy • Develop migration architecture • Development of support procedures and training Citrix Confidential

8. Migration Methodology • Methodology for Upgrade of MF 1.8 to MF XP • Test • Simulate production environment as closely as possible • Regression test applications • Scalability testing • End to end test of the architecture • Pilot • Production users and systems • User acceptance testing as well as business sign-off • Rollout • Full production implementation Citrix Confidential

9. Migration Methodology • Key Points • Test • All proposed changes should be thoroughly tested • Change Management • All changes should be tested prior to implementation in the production environment • Test -> Pilot -> Production • Clean up BEFORE migrating • Get clients to consistent level • A consistent stable environment will help to mitigate risk • Test, Test, Test Citrix Confidential

10. Migration Options • Migration Option 1: Migrate Existing MF 1.8 Server Farm • Why? • Large existing server farm deployments • 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 • Enable Mixed Mode in the XP Server Farm during install of 1st XP Server • Migrate servers one at a time while the Farm is on line Citrix Confidential

11. Migration Options • Migration Option 1: Migrate Existing MF 1.8 Server Farm • Considerations: • Existing MF 1.8 Applications will be migrated to XP • First XP Server becomes ICA Master Browser • Applications will be load balanced across XP and 1.8 Farms • License pooling will function between 1.8 and XP servers on a subnet basis • ICA license gateways created with MF 1.8 will not function for license pooling across subnets • Both 1.8 traffic and XP IMA traffic will exist on network • Load balancing algorithms are different while in mixed mode • Managing published applications during interoperability must be done with two utilities, Published Application Manager (appcfg.exe) for 1.8 and Citrix Management Console (CMC) for XP • Mixed mode is designed to facilitate migration to MetaFrame XP; it is not designed to be a permanent solution. Citrix Confidential

12. Migration Options • Migration Option 2: Migrate Existing MF 1.8 Servers to a new XP Server Farm • Why? • Keep existing application deployments • Use existing servers in the server farm during migration • 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 • NFuse could be leveraged to assist with this process Citrix Confidential

13. Migration Options • Migration Option 3: Create a New XP Server Farm with Clean System Installs • Why? • Re-deploy or re-configure application installations • Potentially use new server hardware • 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 • NFuse could be leveraged to assist with this process • Automated Server Builds could help speed migration Citrix Confidential

14. Architectural Overview • MetaFrame XP: Native Mode vs. Mixed Mode • Native Mode • The legacy Program Neighborhood Service and ICA Browser services are installed but disabled • The native XP ICA Browser and Program Neighborhood subsystems are enabled • Server to server communication via the IMA Service uses the IMA protocol over TCP port 2512 • Command line utilities use IMA RPC calls to communicate with the Remote Administration Subsystem • Mixed Mode • Allows MetaFrame XP server farm to interoperate with a MetaFrame 1.8 server farm • Accomplished by adding the legacy Program Neighborhood Service and ICA Browser services to XP Servers • Provides limited pooling of connection license counts between MetaFrame 1.8 and MetaFrame XP servers • Servers communicate over UDP Port 1604 for MF 1.8 communication, MF XP communication is IMA protocol over TCP port 2512, thereby increasing network traffic • Command line utilities use UDP Port 1604 to communicate with the ICA Browser Service Citrix Confidential

15. Migration Process and Best Practices • Migration Steps: Analysis – Review of Existing Infrastructure Environment • Farm Structure • Single Farm that spans two network subnets • ICA Gateway exists between subnets • 50 Servers running MF 1.8 FR1 • Applications • 25 Published Applications Load balanced • Servers are mixed with different application groups • Application Delivery Method • Users currently connect with the Program Neighborhood Client • Client is configured for TCPIP-HTTP using the XML Service (No UDP Browsing) • Users • 2000 users currently access the applications within the MF 1.8 Farm Citrix Confidential

16. Migration Process and Best Practices • Existing Infrastructure Environment Citrix Confidential

17. Migration Process and Best Practices • Migration Steps: Design • Determine Native XP Architecture • Determine Zone and Data Collector strategy • Determine IMA Data Store (local or remote) Citrix Confidential

18. Migration Process and Best Practices • Planned Native XP Architecture • Singe XP Farm • Remote Database for IMA Data Store • One XP Zone that spans both network subnets • One dedicated XP Data Collector • Applications delivered via NFuse Citrix Confidential

19. Migration Process and Best Practices • Planned Native XP Architecture Citrix Confidential

20. Migration Process and Best Practices • Migration Steps: Design • Determine Native XP Architecture • Determine Zone and Data Collector strategy • Determine IMA Data Store (local or remote) • Identify Migration Strategy • Option 2: Migrate Existing MF 1.8 Servers to a new XP Server Farm Citrix Confidential

21. Migration Process and Best Practices • Migration Strategy – Migrate Existing MF 1.8 Servers to a new XP Server Farm • Why? • Avoid the limitations of Mixed mode • It is difficult to upgrade 50 servers overnight • Keep existing applications • How? • Phased upgrade process during scheduled periods to migrate servers, applications, and users • Leverage NFuse to combine MF 1.8 and XP server farms into single location (portal) Citrix Confidential

22. Migration Process and Best Practices • Migration Steps: Design • Determine Native XP Architecture • Determine Zone and Data Collector strategy • Determine IMA Data Store (local or remote) • Identify Migration Strategy • Option 1: Migrate Existing MF 1.8 Servers to a new XP Server Farm • Define Migration Architecture Citrix Confidential

23. Migration Process and Best Practices • Migration Architecture Citrix Confidential

24. Migration Process and Best Practices • Migration Steps: Design • Determine Native XP Architecture • Determine Zone and Data Collector strategy • Determine IMA Data Store (local or remote) • Identify Migration Strategy • Option 1: Migrate Existing MF 1.8 Servers to a new XP Server Farm • Define Migration Architecture • Identify Users for Pilot Implementation Citrix Confidential

25. Migration Process and Best Practices • Migration Steps: Test • Simulate the planned production environment • Server hardware, network setup, NT domain Structure • Regression test applications on XP • Application integration and functionality testing • Perform scalability testing • Server hardware and network Citrix Confidential

26. Migration Process and Best Practices • Migration Steps: Rollout • Pilot Planned MetaFrame XP environment Citrix Confidential

27. Migration Process and Best Practices • Pilot Implementation • Configure NFuse site to combine data from MF 1.8 and XP Farms • New clients can be distributed via the NFuse site • Open TCP ports 2512 for IMA internal server to server communication and 2513 for CMC communication • Install and configure remote database • Install MetaFrame XP on new server to be new dedicated XP Data Collector • Configure XP Zone Citrix Confidential

28. Migration Process and Best Practices • Pilot Implementation (cont.) • During the first scheduled period migrate a group of MF 1.8 servers to XP • For each application identify two servers that have the application and migrate them to XP • These servers will be able to support load balancing for all published applications • Change group permissions to published applications to support initial upgrade • First subset of users should be able to access applications from the XP Farm without affecting existing MF 1.8 Farm users • Published Application permissions will need to be modified in both Farms to support this process – remove first subset of users from user groups that are applied to existing MF 1.8 published applications and XP migrated applications, create new user groups and apply them to the migrated MF XP published applications Citrix Confidential

29. Migration Process and Best Practices • Pilot Implementation (cont.) • Migrate users to pilot environment • Perform usability testing by pilot users • After user acceptance, obtain business sign-off to continue into rollout Citrix Confidential

30. Migration Process and Best Practices • Migration Steps: Rollout • Pilot Planned MetaFrame XP environment • Production Rollout Citrix Confidential

31. Migration Process and Best Practices • Production Rollout • Continue to Migrate existing MF 1.8 servers into the new XP Farm during scheduled periods • Along with this process additional groups of users can be migrated Citrix Confidential

32. Questions?

33. Citrix Confidential