MetaFrame XP

1. MetaFrame XP Presented by Rick Dehlinger Senior Systems Engineer Citrix Systems, Inc.

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

3. 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”

4. Intro MetaFrame XP

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

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

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

8. 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…

9. New Terms and Architectural Concepts

10. 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).

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

12. Independent Management Architecture Citrix Mgt. Console MetaFrame XP NT 4.0 TSE MetaFrame XP Win2K Independent Management Architecture (IMA) DB Load Management Services Installation Management Services Resource Management Services Security Services • Central Data Store • SQL, Oracle, Access

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

14. Server Farms with MF 1.8: ICA Browser MFAdmin, PAM, etc. 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. ICA Master Browser ICA Master Browser Segment 1 10.1.1.x Farm 1 (2, 3) Segment 2 10.1.2.x Farm 4 (5, 6)

15. Server Farms with MF XP: IMA CMC LHC LHC LHC LHC LHC LHC DS DC DC 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) Server Farm Zone 2 Zone 1

16. Data Store 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.

17. Data Store in ‘Direct’ Mode DS 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. LHC LHC LHC LHC LHC LHC

18. Data Store in ‘Indirect’ Mode LHC LHC LHC LHC LHC LHC DS DC 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. IMA Host (indirect mode)

19. Local host Cache (LHC) CMC LHC LHC LHC LHC LHC LHC DS DC 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. Server Farm Zone 2 Zone 1

20. Data Collectors CMC LHC LHC LHC LHC LHC LHC DS DC DC 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. Server Farm Zone 2 Zone 1

21. Zones CMC LHC LHC LHC LHC LHC LHC DS DC DC 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! Server Farm Zone 2 Zone 1

22. Citrix Management Console (CMC) CMC LHC LHC LHC LHC LHC LHC DS DC DC 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. Server Farm Zone 2 Zone 1

23. Demonstration: CMC in Action

24. Understanding XP Communication 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)

25. IMA Persistent Data Events (1) LHC LHC LHC LHC LHC LHC DS DC 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)

26. IMA Persistent Data Events (1) CMC LHC LHC LHC LHC LHC LHC DS DC DC 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.

27. IMA Dynamic Data Events (2) LHC LHC LHC LHC LHC LHC DC DC 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.

28. IMA Dynamic Data Events (2) LHC LHC LHC LHC LHC LHC DC DC 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

29. IMA Printer Management Events (3) Communication Events • Why is this slide blank? • Printer Management has a relatively substantial impact upon IMA traffic.

30. ICA Session Communication (4) LHC LHC LHC DC 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).

31. ICA Session Communication (4) NFuse LHC LHC LHC DC 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.

32. ICA Session Communication (5) LHC LHC LHC DC ICA Client to Server • Actual ICA session stream from the ‘Connector’ (ICA client) to an XP server, destination port TCP1494 (default). (launched from either UI)

33. MetaFrame XP Features Revealed

34. MetaFrame XP Management • Centralized Administration • Single 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.

35. Citrix Management Console

36. 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 singlepoint.

37. License Pooling Across Subnets Only 1 ICA License Is utilized • 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 1 Subnet 10.1.X.X Data Center 2 Subnet 10.2.X.X Data Center 3 Subnet 10.3.X.X

38. 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 X

39. MetaFrame XP License Management • Centralized License Management • Flexible 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

40. MetaFrame XP Directory Integration • Active Directory Integration • Application 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. user@domain.com NFuse and Program Neighborhood • Enables users to utilize their Active Directory accounts to access MetaFrame applications via NFuse and Program Neighborhood

41. Active Directory Integration 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 ADS Enumerate User and Group Accounts from Active Directory Citrix Management Console

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

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

44. Print Driver Replication CMC 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. Install New Printer Driver on 1 Server Use CMC to Manage and Distribute New Printer Driver to entire Server Farm

45. Printer Compatibility • Restricted • XYZ Printer • ABC Printer ABC Printer 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 ICA Client ICA Connection Printer is on the restricted list X Printer Creation is Disabled

46. Print Management Recommendations • 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.

47. Printer Queue Management • #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.

48. New! XP Shadow 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”

49. ICA Client Enhancements • Client Enhancements • Published 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

50. Per Session Time Zone Support Redmond Time Zone GMT -8 Time Zone GMT -7 ICA Client MetaFrame XP Server Salt Lake City Ft. Lauderdale Time Zone GMT -5 ICA Client Published Applications Run in context of User’s Local Time Zone London Time Zone GMT ICA Client