Migrating to MetaFrame XP

Welcome to Citrix Western Regional WebConference!

What are we trying to do here?

 to provide timely, easily accessible technical information regarding

Citrix technologies.

 to ensure that you have a consistent way to get current information

regarding 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

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

Who are my regional Citrix SE contacts?

Who are these guys?

 NorCal (Northern California)

Arlo Paranhos, SE Manager, Western Region [email protected]

Jason Gradel, SE, [email protected]

 LA/Orange County

Vinny Sosa, SE, [email protected]

 Southwest (Southern California, Arizona, Southern Nevada, Hawaii) Bill Rice, SSE, [email protected]

Matt McGrigg, SE, [email protected]

 _{Rocky Mountain (Utah, Colorado, ?)}

Paul Smith, SE, [email protected]

 _{Northwest (Oregon, Washington, Idaho, Alaska)}

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

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

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}

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

‘Mixed Mode’ IS…

XP

XP

Server Farm

Server Farm

1.8

1.8

Server Farm

‘Mixed Mode’ is NOT…

Mixed mode is not designed to be a permanent solution.

Termsrv

Mixed Mode – Architecture Comparison

Mixed Mode – Architecture Comparison

MetaFrame XP (Native Mode)

IMA Svc Other IMA Srvrs

(TCP)

NFuse

XML Svc

ICA Client

HTTP

HTTP & XML

CMC TCP

TCP PN Virtual

Termsrv

Mixed Mode – Architecture Comparison

MetaFrame XP (Mixed Mode)

‘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}

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.

Migration Strategies



Flash Upgrade



Parallel Migration

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.

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

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

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.

Scenario 1: Single site, single farm migration

High level steps (‘rolling’ upgrade):

1. Create IMA Data Store if necessary

2. Upgrade a server besides the ICA master browser

 Install in interoperability mode when prompted

 Apply upgrade licenses to XP farm

3. Upgrade remaining servers

4. Switch to XP native mode

Scenario 1: Single Site Single Farm Migration

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.

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

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

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

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”

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 [email protected] Jason Gradel, SE, [email protected]

 _{LA/Orange County}

Vinny Sosa, SE, [email protected]

 _{Southwest (Southern California, Arizona, Southern Nevada, Hawaii)}

Bill Rice, SSE, [email protected]

Matt McGrigg, SE, [email protected]

 _{Rocky Mountain (Utah, Colorado, ?)}

Paul Smith, SE, [email protected]

 _{Northwest (Oregon, Washington, Idaho, Alaska)}