metaframe xp

MetaFrame XPPresented by Rick Dehlinger

Senior Systems Engineer

Citrix Systems, Inc.

What are we going to cover today?

Intro to MetaFrame XP What is MetaFrame XP? What’s new in MetaFrame XP? How is MetaFrame XP Packaged?

New Terms and Architectural Concepts

MetaFrame XP Features (technically speaking)

Intro to Management Tools in MetaFrame XP

Time permitting: Migrating to MetaFrame XP Useful XP Command Line Utilities

How do I stay on top of stuff like this?

Participate in the CitrixNW Yahoo! group Self maintaining ‘newsletter’ style list Used to communicate pertinent technical/training info to Citrix

users/integrators in Northwest Sign up at http://groups.yahoo.com/group/citrixnw

Participate in Multi events and Web Conferences Web Conferences every Thursday See http://groups.yahoo.com/calendar/citrixnw for schedule and

participation instructions

Don’t worry about writing EVERYTHING down today Download this presentation from http://groups.yahoo.com/files/citrixnw

“RD Face to Face Version x.zip”

http://groups.yahoo.com/calendar/citrixnw

http://groups.yahoo.com/files/citrixnw

Intro MetaFrame XP

What is MetaFrame XP?

The next generation of Citrix’s application deployment PLATFORM.

The product of a ground up reassessment by our engineers coupled with your input on what enterprise class server based computing should be.

Built to eliminate current and future obstacles to speed, performance and control while maintaining backward compatibility for ease of migration.

Everything you have seen in 1.8/FR1 and MORE.

What’s new in MetaFrame XP?

Citrix Management Console Application-based load management

‘Load Management’ in XPa and XPe

System monitoring and analysis ‘Resource Manager’ in XPe

Application packaging and delivery ‘Installation Manager’ in XPe

Network management ‘Network Manager’ in XPe

Printer management Shadowing enhancements Client time zone support Enhanced scalability

What’s new in MetaFrame XP?

Reduced IT administration Reduced network traffic Centralized license management

Enterprise-wide license pooling Enhanced license availability

Active directory support NFuse ready (turnkey NFuse) ICA client extensibility MetaFrame and WinFrame interoperability

‘Mixed’ or ‘Interoperability’ mode

How is it Packaged?

MetaFrame XPs

MetaFrame XPa

XPs plus: Load Management

MetaFrame XPe

XPs plus: Load Management Resource Management Installation Management Network Management

Licensed per Connection! Deploy as many servers as you need…

New Terms and Architectural

Concepts

New Terms

IMA: Independent Management Architecture

Data Store: Central configuration database

LHC: Local Host Cache. Persistent data cache that exists on each server.

Data Collector: Manages dynamic data and client enumeration/resolution (replaces ICA Master Browser).

Zone: Deliberate grouping of XP servers, each with it’s own Data Collector.

CMC: Citrix Management Console (replaces MF 1.8 administration tools).

What is IMA? Why is it important?

IMA… Is a TCP based, event driven messaging bus, used by

MetaFrame servers and management tools communication.

Is a modular and easily extensible subsystem capable of supporting current and future MetaFrame products and tools.

Overcomes the scalability constraints of the MetaFrame 1.8 Platform, allowing us to scale environments to new levels.

Allows us to administer any farm from a central tool (CMC) that doesn’t have to run on a MetaFrame server.

Will allow Citrix to add functionality to the Platform independent of the base server.

MetaFrame XP NT 4.0 TSE

MetaFrame XP Win2K

Central Data Store

•SQL, Oracle, Access

Load Management

Services

Installation Management

Services

Resource Management

Services

Independent Management Architecture (IMA)

Citrix Mgt. Console

DB

Security Services

Independent Management Architecture

MetaFrame Server Farms

MetaFrame 1.8:

•Server Farms in MetaFrame 1.8 are a collection of servers on a given broadcast segment that are be managed as a single unit.

•Server Farms in MetaFrame 1.8 may also be defined by sharing a common ‘Application Set’.

MetaFrame XP:

•The Server Farm in MetaFrame XP defines the scope of management as well as the ‘Application Set’.

•Server Farms in MetaFrame XP are designed to operate across segments, and are managed through the Citrix Management Console.

Server Farms with MF 1.8: ICA Browser

Segment 110.1.1.x

Farm 1 (2, 3)

Segment 210.1.2.x

Farm 4 (5, 6)

MFAdmin,PAM, etc.

ICA MasterBrowser

ICA MasterBrowser

MFAdmin,PAM, etc.

MetaFrame 1.8/ICA Browser Attributes Server Farms cannot span segments Each segment has ONE ICA Master Browser ICA Master stores dynamic data for the segment and handles

Enumeration/Resolution for ICA clients Persistent data stored in registry (farm membership, licenses, pub apps, etc.) Persistent data read by ICA browser/PN Service at startup Cross server configuration tools read/write to registry on all servers Servers communicate via UDP broadcasts, remote REG calls, RPC’s, etc.

Server Farms with MF XP: IMA

MetaFrame XP/IMA Attributes Server Farms can span segments, can contain multiple Zones Each zone has ONE Data Collector Data Collectors store dynamic data and handle Enumeration/Resolution for ICA

clients Persistent farm data stored in shared, persistent Data Store Persistent data read from DS at startup, cached in Local Host Cache Management tool communicates via IMA to Data Store and member servers Servers communicate via IMA (TCP)

Zone 1

Zone 2

CMC

DS

LH

C

LH

C

LH

C

LH

C

LH

C

LH

C

DC

DC

Server Farm

Attributes of the MetaFrame XP Data Store (DS) The DS is a repository (database) which contains

persistent, farm wide data like member servers, licenses in farm, zone configs, printers/drivers, published apps, load evaluators, trust relationships, etc.

Each MetaFrame XP farm shares one Data Store. All information in the DS is stored in an encrypted binary

format (except indexes). A Farm can operate for 48 hours if DS is unavailable,

then licenses time out and no new users can connect. A DS can be an Access, MS SQL, or Oracle database. A DS can be configured for either ‘Direct’ or ‘Indirect’

access.

Data Store

Attributes of Direct Mode Uses Microsoft SQL 7/2000 or Oracle 7.3.4/8.0.6/8.1.6

database. Servers initialize directly from the DS via ODBC. Servers maintain an open connection to the database

for consistency checks.

Data Store in ‘Direct’ Mode

DS

LH

C

LH

C

LH

C

LH

C

LH

C

LH

C

Attributes of Indirect Mode Uses JET 4.x, Microsoft SQL 7/2000 or Oracle 7.3.4/8.0.6/8.1.6

database. Member servers communicate via through ‘IMA host’ server to

read/write to data store. If using JET database, MF20.MDB lives on the ‘IMA host’ server.

Data Store in ‘Indirect’ Mode

DS

LH

C

LH

C

LH

C

LH

C

LH

C

LH

C

IMA Host (indirect mode)

DC

Attributes of the Local Host Cache A subset of the Data Store, stored on each individual server

(IMALHC.MDB).• Contains basic info about servers in farm, pub. apps and properties, trust

relationships, server specific configs (product code, SNMP settings, load evaluators, etc.)

Used for Initialization if DS is down. Used for ICA client application Enumeration.

Local host Cache (LHC)

Zone 1

Zone 2

CMC

DS

LH

C

LH

C

LH

C

LH

C

LH

C

LH

C

DC

DC

Server Farm

Attributes of Data Collectors A DC stores dynamic information about a Farm, such as servers up/down,

logons/logoffs, disconnect/reconnect, license in use/released, server/application load, etc.

There is a DC for each Zone. DC’s handle all ICA client Resolution activity, should handle all Enumeration

activity. ANY DC can Resolve ANY app for ANY client (DC’s are peers in a multi-zone implementation).

DC’s distribute most persistent data changes to member servers for LHC update.

Data Collectors

Zone 1

Zone 2

CMC

DS

LH

C

LH

C

LH

C

LH

C

LH

C

LH

C

DC

DC

Server Farm

Attributes of Zones Logical, centrally configurable grouping of MetaFrame XP servers. Each Zone has one Data Collector (DC). Can span IP networks (LAN, WAN). Aren’t necessarily tied to an IP segment (only by default). Are useful for partitioning/controlling persistent data update traffic and for

distributing ICA client Enumeration/Resolution traffic. A Zone can contain up to 256 hosts without a registry modification. In most cases, fewer zones are better!

Zones

Zone 1

Zone 2

CMC

DS

LH

C

LH

C

LH

C

LH

C

LH

C

LH

C

DC

DC

Server Farm

Attributes of the CMC Central management tool where 98% of farm configuration/maintenance occurs. Extensible framework that allows different tools to ‘snap in’. Doesn’t need to run on a MetaFrame server. Works through the IMA service (dest. port 213) to access DS, DC, and member

servers. Should be run through a DC that has local access to the DS. Is the most read/write intensive usage of the DS.

Citrix Management Console (CMC)

Zone 1

Zone 2

CMC

DS

LH

C

LH

C

LH

C

LH

C

LH

C

LH

C

DC

DC

Server Farm

Demonstration: CMC in Action

Communication ‘Layers’ (5 of them) IMA (server to server) Communication

• Persistent Data Events (1)• Dynamic Data Events (2)• Printer Management Events/Processes (3)

ICA Session (client to server) Communication• Client Enumeration/Resolution (4)• ICA Client to Server (5)

Understanding XP Communication

IMA Persistent Data Events (1)

DS

LH

C

LH

C

LH

C

LH

C

LH

C

LH

C

Communication Events IMA Service Initialization

• Read heavy initialization/validation of the LHC Periodic Consistency Check (configurable timing)

• Key: HKLM\Software\Citrix\IMA\DCNChangePollingInterval• Default value: 600000 milliseconds REG_DWORD: 0x927C0

IMA Host (indirect mode)

DC

IMA Persistent Data Events (1)

Communication Events Farm modification through CMC

• Modifications happen through a 2 phase process:

1: CMC (through a MetaFrame server) commits the change to the DS.

2: CMC/IMA packages and distributes changes <10k to the DC’s, who then distribute it to member servers. If the change is >10k, it distributes a change notification and servers perform consistency check on LHC.

• If member servers are unavailable, they receive the change during the periodic LHC consistency check.

CMC

DS

LH

C

LH

C

LH

C

LH

C

LH

C

LH

C

DC

DC

IMA Dynamic Data Events (2)

Communication Events Any state change on server (logon/logoff, disconnect/reconnect,

load change) triggers a dynamic data update.• Member server notifies it’s DC of the change.• The member server’s DC notifies ALL other DC’s of the

change. Note: DC’s have a peer-to-peer relationship: every DC knows what every

other DC knows.

LH

C

LH

C

LH

C

LH

C

LH

C

LH

C

DC

DC

IMA Dynamic Data Events (2)

Communication Events Member server to zone DC heartbeat check.

• Key: HKLM\Software\Citrix\IMA\Runtime\KeepAliveInterval• Default value: 60000 milliseconds REG_DWORD: 0xEA60

DC to DC consistency check.• Key: HKLM\Software\Citrix\IMA\Runtime\Gateway\ValidationInterval• Default value: 300000 milliseconds REG_DWORD: 0x493E0

LH

C

LH

C

LH

C

LH

C

LH

C

LH

C

DC

DC

IMA Printer Management Events (3)

Communication Events Why is this slide blank? Printer Management has a relatively substantial impact upon IMA

traffic.

Client Enumeration/Resolution Client to XP: Client asking, XP answering ‘what apps can I

run?’ and ‘where do I go for this app?’• Enumeration (what apps…): Client to XP server, TCP80 (default

with TCP+HTTP server location), or UDP1604 (with TCP/IP server location), enumerated from LHC on MetaFrame server.

• Resolution (where do I go…): Client to XP DC, TCP80 (default with TCP+HTTP server location), or UDP1604 (with TCP/IP server location).

ICA Session Communication (4)

LH

C

LH

C

LH

CD

C

Client Enumeration/Resolution NFuse to XP: NFuse asking (on behalf of the client) and XP

answering the above questions• Client web browser talking HTTPS to NFuse server for both

processes.• Enumeration (what apps…): NFuse to XP server, TCP80 (default),

or SSL, enumerated from LHC on MetaFrame server, presented to web browser as hyperlinks.

• Resolution (where do I go…): NFuse to XP DC, TCP80 (default), or SSL, builds ICA file with resulting info.


LH

C

LH

C

LH

CD

C

NFuse

ICA Client to Server Actual ICA session stream from the ‘Connector’ (ICA client) to an

XP server, destination port TCP1494 (default).


LH

C

LH

C

LH

CD

C

(launched from

either UI)

MetaFrame XP Features Revealed

MetaFrame XP Management

Centralized AdministrationSingle Point Command and Control

All administration, configuration, monitoring and control of the Citrix Server Farm is managed centrally

Independent Management Architecture IMA compliant servers and management products share a common and

extensible management infrastructure

Unified Management Console The Citrix Management Console communicates across a single Management

Scope of the server farm using the IMA protocol

Central Data Store Configuration information for the Server Farm is stored centrally in the Citrix

Data Store.

Citrix Management Console

Centralized License Management

Description: Licenses are installed into the Central Data Store and managed centrally from the Citrix Management Console.

Benefit: Administrators can easily manage all of the licenses for the Citrix Server Farm from a single point.

License Pooling Across Subnets

Description: ICA Connection licenses for client connections can be pooled across the entire server farm regardless of whether the server farm crosses network subnets

Benefits: Enables pooling of ICA connection licenses across the extended enterprise network within the MetaFrame Server Farm

Data Center 1Data Center 1Subnet 10.1.X.XSubnet 10.1.X.X



Only 1 ICA LicenseOnly 1 ICA LicenseIs utilizedIs utilized

License Fail Over and Redundancy

Description: MetaFrame XP allows licenses to be available for fail over and redundancy. In the case of a server failure the Server and Connection license are still available

Benefit: Administrators have the ability to bring up “warm” backup servers in the event of a server failure without the need to re-install and re-activate their server licenses

MetaFrame XP License Management

Centralized License ManagementFlexible Licensing for emerging business models

Increased flexibility to support Citrix Licensing Programs (Shrink Wrap, CLP, ELP, and iLicense)

Single Point of License Installation and Activation License installation and activation can be done centrally via the Citrix

Management Console

Support for Multiple Server/Product Platforms The new licensing system supports all types of Citrix licenses: Server,

Connection, and Management

Connection License Sharing across Platforms Ability to share connection licenses across other IMA compliant server

platforms in the future: Solaris, HP-UX, AIX

MetaFrame XP Directory Integration

Active Directory IntegrationApplication Publishing

Enables application Publishing to users and Groups in Active Directory

Account Authority Access Utilizes Native Active Directory Interfaces to access the Active

Directory

User Principal Names Allows users to logon to the MetaFrame Server using User Principal

Names: i.e. [email protected]

NFuse and Program Neighborhood Enables users to utilize their Active Directory accounts to access

MetaFrame applications via NFuse and Program Neighborhood

Active Directory Integration

ADS

Citrix Management Console

Enumerate User and Group Accounts from Active Directory

Publish Application for ADS Users from the CMC

Description: Applications can be published on MetaFrame XP servers and assigned to users from Active Directory.

Benefit: MetaFrame XP integrates and fully supports Application Publishing in a Native Active Directory environment

MetaFrame XP Printer Management

Printer Management Print Driver Replication Printer Mapping Network Printer Auto-Creation Printer Compatibility Printer Bandwidth Control Terminal Printer Auto-Creation Client Printer Creation Logging

MetaFrame XP Printer Management

Printer Mapping Ability to create mappings for Windows 9X Client Printers on the

MetaFrame Server and automatically distribute to the Server Farm

Printer Bandwidth Control Allows the administrator to specify the amount of bandwidth that

can be used by printing over the client connection

Terminal Printer Auto-Creation Ability for the administrator to setup auto-creation of printers for

ICA DOS and WinCE Terminal Devices

Client Printer Creation Logging Logs all information about auto-creation of client printers,

allowing the administrator to proactively detect printer issues and resolve them with the required information

Print Driver Replication

CMC

Install New Printer Driver on 1 Server

Use CMC to Manage and Distribute New Printer Driver to entire Server Farm

Description: Through the Citrix Management Console, printer drivers can be managed across the entire server farms.

Benefit: Gives administrators the power and control to manage and distribute printer drivers to all of the MetaFrame servers in the server farm, providing a consistent printing environment for all users.

Printer Compatibility

Restricted•XYZ Printer•ABC Printer

ABC Printer

ICA Client

ICA ConnectionPrinter is on the restricted list

Printer Creation is Disabled

Description: Printer compatibility allows the administrator to specify client printers that can be used in the MetaFrame environment or specify printers that can never be used.

Benefit: Gives administrators the power to determine and control the types of client printers that can be utilized on the MetaFrame Servers enabling them to ensure a consistent and stable computing environment

Print drivers can only be replicated to the servers of the same OS as the source server.

Install drivers on the source server and select any available port on the server.

If installing for the sole purpose of replication there is no need to share the printers or set them as default.

Can be very CPU intensive on the source server so avoid replicating drivers while the source server has a heavy load.

Print Management Recommendations

#QueueEntries = [#Drivers] * [#Servers]• Every driver/server combination creates a queue item in

the printer replication queue.• Should not exceed 1500 entries in length• Eg. 30 drivers to 50 servers

QPRINTER Utility• Not installed by default.• \support\debug\i386• QPRINTER /REPLICA

Expected Performance• Handled by IMA Service at very low priority.• Depends on network traffic and server load.

Printer Queue Management

Shadowing Installation Option: • Ability to select whether ICA Shadowing is available • Lock down the shadowing configuration to avoid changes• Allows administrators flexibility with privacy and security

issues involving shadowing

Shadow Indicator: • Notifies users that shadowing is in progress• Provides users with a “cancel” button to end the shadow

Shadow Activity Logging: • logs all session and user information during a shadow• Enables the creation of a shadow “audit log”

New! XP Shadow Management

ICA Client Enhancements

Client EnhancementsPublished Application Parameter Support

Enables the MetaFrame server to accept published application parameters provided by a client, and the client to pass published application parameters to the server

ICA Client Object Interface A framework that exposes the functionality of the Citrix ICA Win32 Client to

other objects or Applications. Allows any application that supports embedding of objects, to interface with and pass instructions to the ICA Client

Per Connection Timezone Ability to run applications on the MetaFrame server in the context of the

users local time zone. The MetaFrame Server can support different users running applications at different time zones on the same server

Per Session Time Zone Support

Redmond

ICA Client

ICA Client

ICA Client

Ft. Lauderdale

London

MetaFrame XP ServerSalt Lake City

Published ApplicationsRun in context ofUser’s Local Time Zone

Time ZoneTime ZoneGMT -8GMT -8


Time ZoneTime ZoneGMTGMT


Introducing ‘Turnkey’ NFuse NFuse install option with XP install if IIS detected. Sets up default web and startup page. In short- you can now ACCIDENTLY deploy NFuse!

NFuse Integration

‘Project Columbia’

What is it? Free, unsupported, NFuse template site Drop in replacement for XP’s ‘turnkey’ NFuse Easy feature configuration (config.txt)

What does it do? Tons! For starters…

Multi-farm support Backup XML server support Integrated password validation with change function Detect/install ICA clients Automatic delivery of win32t.cab ICA client

‘Project Columbia’

But wait, there’s more! ;-) Throw in these functions too.

Display farm names with app sets Modify application display options and column count Automatically populate USERNAME/DOMAIN fields Disable ‘Right Click/Save As’ on ICA file Enable connectivity for Citrix Extranet clients Return ALTADDR for external network users Round robin load balancing of XML servers

Current limitations Win32/Microsoft server focus Un-supported

Demonstrations: ‘Turnkey’ NFuse and ‘Project Columbia’

‘Project Columbia’ in Action

Management Tools in MetaFrame XP

Citrix Load Management Provides:• Configuration of Application Balancing• Monitoring of Application and Server Load • Dynamic adjustment of Load Balancing Criteria• Citrix Load Management replaces ICA Load Balancing

Services in MetaFrame 1.8• Load Management utilizes IMA for communication• Provides the ability to create criteria for Servers and

Applications

Load Management in XPa and XPe

Major Components of Load Manager Rules

• Measure statistics for high or low loads on servers.• Lower a rule, reach a threshold more quickly• Elevate a rule, a threshold is hard to reach.

Load Evaluators• Used to configure server load measurements.• Use Default for Citrix provided load evaluators.• Use Advanced to create your own.• Can vary on each server.• Can use any combination of rule and load evaluators per

server across the farm.


Load Management Criteria

Application User Load Context SwitchesCPU Utilization Disk Data I/ODisk Operations License ThresholdMemory Usage Page FaultPage Swap Server User LoadIP Range NewNew Scheduling NewNew

Administrators can now control accessibility to published applications on the basis of an IP range rule to specify sets of addresses and a scheduling rule to grant access to a specific

application only during specified hours


New Criteria in Load Management

IP Range:

•Using the IP Range rule an administrator can specify a distinct address or set of addresses that can access the published application

Scheduling:

•The Scheduling criteria enables administrators to control the application load across server based on time sensitive criteria

•Using the Scheduling criteria and administrator can create a Load Evaluator that allows access to a specific application or server only during specified times

Default Load Evaluators:Default:

• Rule represents the number of users logged onto a MetaFrame XP server

• Contains one rule, Server User Load, that reports a full load when 100 users log on to the attached server

Advanced:• The rules in this load evaluator represent server performance

using Disk I/OCPU UtilizationDisk OperationMemory Usage


Demonstration:Load Management

Resource Manager• Ground up re-write!• Resource Management integrates with the Citrix

Management Console• Resource Management adds tabs to the CMC• Can control summary data in the CMC**• Configure Alert recipients in the CMC• Adds counters to each server for monitoring, can manage

several servers in the CMC• Monitors application usage by published applications• Watcher window requires the CMC to monitor servers

Resource Management in XPe

Installation Manager• Nearly a ground up re-write!• Installation Management integrates with the CMC• Configure Network account to be used by the installer service

to install packages• Can select to reboot servers post installation• Define how often to expire and remove installation

management jobs• Define server groups and application packages• Status can be checked in Job properties

Installation Management in XPe

Network Manager• Network Management in XPe is an SNMP agent that runs on

your citrix servers• It can be managed with any SNMP management service or

utility• SNMP agent automatically installed with MetaFrame XPe• Console plug-ins are available for:

Tivoli NetView (v. 5.1.2 and above)HP OpenView 6.0 only

• Plug-ins are located on a separate “Network Management for XPe” CD in the data pack

Network Management in XPe

Migrating to MetaFrame XP

Why Move to MetaFrame XP?

•Increased farm scalability and stability

•Simplified license management and activation

•Printer management

•Enhanced NFuse integration

•Active Directory User Principal Name support

•Client time zone support

•Less server to server network traffic

•1.8 and Feature Release 1 enhancements integrated and available to more clients

Mixed mode is designed to facilitate migration to MetaFrame Extended Platform 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…

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

Termsrv

Mixed Mode – Architecture Comparison

MF 1.8

LocalNT

Registry

ICA BrowserSvc

PN Svc

OtherPN Srvrs(named pipe)

NFuse

XML Svc

ICA Client

HTTP

HTTP &XML

PN VirtualChannel

PN NamedPipe

MFAdmin

AppCfg

QServer

NT Reg (remote regedt)

WinstationAPI(RPC)

UDP 1604

UDP 1604


MF XP (Native Mode)

IMASvc

OtherIMA Srvrs

(TCP)

NFuse

XML Svc

ICA Client

HTTP

HTTP &XML

CMC TCP

TCPPN Virtual Channel

Termsrv


MF XP (Interoperability Mode)

IMASvc

LocalNT

Registry

OtherIMA Srvrs

(TCP)

ICA BrowserSvc

PN Svc

OtherPN Srvrs(named pipe)

NFuse

XML Svc

ICA Client

HTTP

HTTP &XML

PN VirtualChannel

PN NamedPipe

MFAdmin

AppCfg

QServer

NT Reg (remote regedt)

WinstationAPI(RPC)

UDP 1604

UDP 1604

Mixed Mode

Until you get to native mode, you can’t take full advantage of:

Increased farm scalability and stability Advanced printer management UPN support Simplified license management and activation

1.8 license gateways are not supportedMetaFrame connection licenses are equally distributed among subnetsCMC/Farm/Properties/Interoperability can change licenses assigned to each subnet.

Mixed Mode (Cont.)

On first XP install, if 1.8 is detected on the segment, it will offer to run in mixed mode

If yes, legacy tools are automatically installed

Admins must use two sets of tools to manage a mixed farm appcfg 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

Migration Strategies

All servers are upgraded to Extended Platform 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. See specific documentation in Admin Guide.

Note: Repeated licenses will give an error upon migration to IMA Data Store.

Migration Strategies – Flash Upgrade

Migration Strategies – Parallel

XP servers built in native mode

1.8 and XP servers do not communicate w/ each other

Consider this for fast growing installs, new Win2K rollouts, or multi-site scenarios

Requires 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

Migration Strategies – Mixed Mode

Rolling upgrade of existing MetaFrame servers

Set during install 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 Starts PN and ICA browser services on XP servers. Existing apps are migrated to IMA data store (1 time)

Any appcfg. changes made to 1.8 apps after migration are not updated to the data store

Using NFuse to Bridge the Gap

NFuse as a Bridging Technology

NFuse allows administrators to hide complexity from the end user. For migration, it can be used to present applications from an arbitrary number of farms

MetaFrame 1.8 MetaFrame Extended Platform MetaFrame for UNIX Multiple sites

‘Project Columbia’ in Action

Migration Scenarios

Scenario 1: Single Site Single Farm Migration

High level steps (‘rolling’ upgrade):1. Create IMA DataStore 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

5. Enable/disable UDP browsing as needed

Single Farm Migration Tips: 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 1: Single Site Single Farm Migration

Scenario 2: Multi-Farm Consolidation

High level steps: Ensure IMA server to server communication

(default TCP 2512) Upgrade first farm (including switch to native

mode) or build new Enterprise 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.

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.

Useful Command Line Utilities

QUERY FARM (QFARM, replaces QSERVER)

• /APP Display app names and server load.• /DISC Display disconnected session data.• /LOAD Display server load.• /PROCESS Display active processes.• /ADDR Display address data on selected server.• /TCP, /IPX, /NETBIOS Display protocol data.


CLICENSE.EXE: Built in, useful for querying licensing information on the farm.

• Add_and_activiate• Enumerate• In_use• Servers_using


QUERYHR.EXE: From Support directory on XP CD, useful for querying zone/DC info on the farm.

• -z Show all the available zones• -h <zone name> Show all the hosts in a specified

zone• -l Show the Local Host Record• -n <host name> Show the specified Host Record

given a host name• -I <Host ID> Show the specified Host Record given a

host ID• -N Show the farm name• -d <Host ID> Delete an IMA Host Entry


QUERYDS.EXE: From Support directory on XP CD, useful in determining what servers are currently alive in a server farm.

Usage:• Queryds /table:<tablename>[/query:<querystring>]

Table names:• SubscriptionTable• ServiceTable• PN_Table• Conn_Sessions• Disc_Sessions


QUERYDC.EXE: From Support directory on XP CD, useful for querying DC info and forcing ‘elections’.

• -z <zone name> Show Data Collector name• -e Force Election• -a Show data collectors for all zones


QPRINTER.EXE: From Support directory on XP CD, useful for viewing printer replication queue and importing mapping files into the DS.

• /REPLICA Display info about printer replication queue

• /IMAPRMAPPING <file name> Import mapping file into DS.


Rick Dehlinger, [email protected]

metaframe xp

Documents

metaframe servers

metaframe xppresented

metaframe xptime

zipintro metaframe xpwhat

future metaframe products

metaframe xpsmetaframe

management tools communication

data collector