Migrating to MetaFrame XP

1. Migrating to MetaFrame XP

2. Welcome to Citrix Western Regional WebConference! • What are we trying to do here? • to provide timely, easily accessible technical information regardingCitrix technologies. • to ensure that you have a consistent way to get current informationregarding Citrix technologies. • to provide you with regular access to Citrix technical resources. • Who can participate? • Any administrator or integrator of Citrix technologies (feel free to tell your friends). • How are we attempting to do it? • www.egroups.com, territory based ‘newsletter’ lists* • Regular technical Web Conference training sessions • *Note: It is only necessary to subscribe to the group for your territory.

3. Welcome to Citrix Western Regional WebConference! • How do I participate in the egroups lists? • Northwest (Oregon, Washington, Idaho, Alaska, Northern Nevada) groups.yahoo.com/group/citrixnw • NorCal (Northern California) groups.yahoo.com/group/citrixnorcal • LA/Orange County groups.yahoo.com/group/lao_cug • Southwest (Southern California, Arizona, Southern Nevada, Hawaii) groups.yahoo.com/group/citrixsw • How do I use these groups? • Join to receive proactive technical/training information via e-mail • Visit the ‘Calendar’ section of your territory’s group for training information • Visit the ‘Files’ section of your territory’s group for pertinent file uploads (presentations, utilities, newsletters, etc.)

4. Who are my regional Citrix SE contacts? • Who are these guys? • NorCal (Northern California) Arlo Paranhos, SE Manager, Western Region arlo.paranhos@citrix.com Jason Gradel, SE, jason.gradel@citrix.com • LA/Orange County Vinny Sosa, SE, elvin.sosa@citrix.com • Southwest (Southern California, Arizona, Southern Nevada, Hawaii) Bill Rice, SSE, bill.rice@citrix.com Matt McGrigg, SE, matt.mcgrigg@citrix.com • Rocky Mountain (Utah, Colorado, ?) Paul Smith, SE, paul.smith@citrix.com • Northwest (Oregon, Washington, Idaho, Alaska) Rick Dehlinger, SSE, rick.dehlinger@citrix.com

5. What are we going to cover today? • Agenda • Why Migrate to MetaFrame XP? • What ‘Mixed Mode’ is (and is NOT) • Architectural comparisons • Migration strategies • Using NFuse as a bridging technology • Sample migration scenarios • Lessons learned • Additional resources • Questions and feedback

6. What will not be covered today? • MetaFrame XP Architecture • Independent Management Architecture • IMA Data Store (DS) • IMA Zones • IMA Data Collectors (DC) • Connectivity methods • Program Neighborhood App Set • Custom ICA connection • ICA files • NFuse • UDP or TCP browsing

7. Why Migrate to MetaFrame XP? • Increased farm scalability and stability • Simplified license management and activation • Printer management • Resource Manager, Installation Manager, Network Manager • Enhanced NFuse integration • Active Directory User Principal Name support • Client time zone support • Less server to server network traffic • 1.8/FR1 enhancements integrated and available to more clients

8. ‘Mixed Mode’ IS… • Mixed mode is designed to facilitate migration to MetaFrame XP with little or no end user disruption. • Provides support for: • Published app migration • App load balancing • Subnet license pooling • Existing NFuse, PN, and Custom ICA connections XP Server Farm 1.8 Server Farm

9. ‘Mixed Mode’ is NOT… • Mixed mode is not designed to be a permanent solution. • Interoperability is achieved by emulating the services and communication mechanisms used by MF1.8

10. Mixed Mode – Architecture Comparison MetaFrame 1.8 Other PN Srvrs (named pipe) NFuse XML Svc HTTP PN Named Pipe PN Svc PN Virtual Channel Local NT Registry ICA Client UDP 1604 ICA Browser Svc QServer UDP 1604 AppCfg NT Reg (remote regedt) Termsrv MFAdmin WinstationAPI (RPC)

11. Mixed Mode – Architecture Comparison MetaFrame XP (Native Mode) Other IMA Srvrs (TCP) NFuse HTTP XML Svc HTTP & XML IMA Svc TCP ICA Client PN Virtual Channel CMC TCP

12. Mixed Mode – Architecture Comparison MetaFrame XP (Mixed Mode) Other IMA Srvrs (TCP) Other PN Srvrs (named pipe) NFuse HTTP HTTP & XML XML Svc PN Named Pipe IMA Svc PN Svc PN Virtual Channel Local NT Registry ICA Client UDP 1604 ICA Browser Svc QServer UDP 1604 AppCfg NT Reg (remote regedt) Termsrv MFAdmin WinstationAPI (RPC)

13. ‘Mixed Mode’- What am I missing? Until you get to native mode, you can’t take full advantage of some XP features: • Increased farm scalability and stability • Advanced printer management • UPN support • Simplified license management and activation • 1.8 license gateways are not supported • MetaFrame connection licenses are equally distributed among subnets, but can be modified through CMC

14. Attributes of ‘Mixed Mode’ A couple things to remember… • On first XP install, if 1.8 is detected on the segment, it will offer to run in mixed mode. • If yes, legacy admin tools are automatically installed. • Admins must use two sets of tools to manage a mixed farm. • appcfg.exe shipped on XP is same as 1.8/SP2. Older versions may not be able to manage apps published with newer versions. • Apps may be published on 1.8, then XP, NOT the reverse.

15. Migration Strategies • Flash Upgrade • Parallel Migration • Rolling Upgrade (using Mixed Mode)

16. Migration Strategies – Flash Upgrade • All servers are upgraded to MetaFrame XP during scheduled network maintenance window • Consider this for highly centralized and/or cloned server environments. • Citrix now supports both unattended and cloned installs for all but the first server in an XP farm. • Specific documentation in Admin Guide. • Note: Repeated licenses will give an error upon migration to IMA Data Store.

17. Migration Strategies – Parallel Migration • Build 2 separate farms, move users/apps from one 1.8 to XP • 1.8 and XP servers do not communicate with each other, so no need for Mixed Mode on XP. • Consider this for fast growing installs, new Win2K rollouts, or multi-site scenarios. • May require additional hardware and licenses. • Alternately, users may be manually migrated in proportion to servers. • XP apps are published manually rather than migrated. • Publish 1.8 and XP apps to distinct user groups to prevent redundant icons. XP Server Farm DC NFuse MB 1.8 Server Farm

18. Migration Strategies – Rolling Upgrade • Upgrade MetaFrame 1.x servers, one at a time, running the XP farm in ‘Mixed Mode’ until all upgrades are complete. • Consider this for very large farms and/or farms that must not be down for any period of time. • Set-up during upgrade of first server in the farm • XP and 1.8 farm names must match • XP server will win ICA browser election • (except 1.8 sp1 MB hardcode) • ‘Mixed Mode’ applies to all XP servers in the farm • PN and ICA browser services run on all XP servers • Existing apps are migrated to IMA data store (1 time) • Any appcfg.exe changes made to 1.8 apps after migration are not updated to the data store

19. NFuse as a ‘Bridging Technology’ • NFuse allows administrators to hide farm complexity from the end user. • Particularly useful for Parallel upgrades, and for multi-farm consolidations • It can be used to present applications from an arbitrary number of farms in a single interface. • Allows admins to change farm configurations without touching the user. • MetaFrame 1.8, XP or Unix

20. Scenario 1: Single site, single farm migration • High level steps (‘rolling’ upgrade): • Create IMA Data Store if necessary • Upgrade a server besides the ICA master browser • Install in interoperability mode when prompted • Apply upgrade licenses to XP farm • Upgrade remaining servers • Switch to XP native mode • Enable/disable UDP browsing as needed

21. Scenario 1: Single Site Single Farm Migration (switching to native mode)

22. Scenario 1: Single site, single farm migration (enabling/disabling UDP browser)

23. Scenario 1: Single site, single farm migration • Single Farm Migration Tips: • Use ‘Flash Upgrade’ strategy if possible. • Pay attention to hard coding of 1.8 ICA MB preferences • 1.8 SP1 (hardcoded) master browser won’t let XP win an election • Avoid publishing new apps or changing app configuration while in XP interoperability mode. If necessary, create/modify apps in 1.8 first, then XP. • Use NFuse and/or auto-client update to distribute new ICA clients.

24. Scenario 2: Multi-Farm Consolidation • High level steps: • Plan for managing user connectivity to farms • If possible, use NFuse as a multi-farm portal • Upgrade first farm (including switch to native mode) or build new ‘Master’ XP farm (in native mode) • Perform upgrades of other 1.8 servers (one farm at a time) joining them to the ‘Master’ XP farm • Some manual cleanup of duplicate app names may be necessary

25. Scenario 2: Multi-Farm Consolidation • Multi-Farm consolidation tips: • Key: managing user connectivity. • If possible, use an NFuse portal pointing to multiple farms. NFuse can play a HUGE role here! • If using PN, add/change Application Set objects and server location/browser type. • If using single published app, may need to modify server location/browser type. • If using ICA file(s), may need to modify server location/browser type. • Use NFuse and/or auto-client update to distribute new clients.

26. Lessons Learned • NFuse is a MUST for complex projects • MetaFrame 1.8 to XP upgrade works well • Use XP native mode where possible • When XP interoperability mode is used, change to native mode immediately when upgrades complete • Turn on ‘Server Responds to UDP broadcasts’ in CMC if any clients will use UDP for app enumeration • MetaFrame for UNIX user licenses are not pooled with MetaFrame XP servers

27. Additional Resources • Presentations (web conference topics) • Connectivity Methods and NFuse • Introduction to MetaFrame XP • Architecting a Native MetaFrame XP Environment • NFuse with MetaFrame XP and Project Columbia • Advanced Concepts of MetaFrame XP (March 15th) (presentations posted on Yahoo! Groups sites, topics given periodically) • Documentation • Citrix ‘MetaFrame XP Best Practices’ document • MetaFrame XP Admin Guide • MF Install and Tuning Tips.pdf (posted to Yahoo! Groups sites, except Admin Guide) • Tools • Project “Columbia” (surprise! Posted to Yahoo! Groups sites)

28. Questions and Feedback Please direct un-answered questions and ANY feedback regarding these sessions (positive or negative) to your regional Citrix SE: • NorCal (Northern California) Arlo Paranhos, SE Manager, Western Region arlo.paranhos@citrix.com Jason Gradel, SE, jason.gradel@citrix.com • LA/Orange County Vinny Sosa, SE, elvin.sosa@citrix.com • Southwest (Southern California, Arizona, Southern Nevada, Hawaii) Bill Rice, SSE, bill.rice@citrix.com Matt McGrigg, SE, matt.mcgrigg@citrix.com • Rocky Mountain (Utah, Colorado, ?) Paul Smith, SE, paul.smith@citrix.com • Northwest (Oregon, Washington, Idaho, Alaska) Rick Dehlinger, SSE, rick.dehlinger@citrix.com