Citrix Presentation Server

Overview

 What is Citrix Presentation server ? How will this help Corporate ? What is the Advantage ?

 Citrix Citrix Metaframe Citrix Presentation Server

 Citrix MetaFrame Presentation Server is a technology that can allow remote users to connect to applications that are actually installed on a remote computer.

 Remote application looks like as if it is installed locally

 For example, if an application needs to be made available to users who are outside the network , the application can be installed on a Citrix server and access will be given to the users who need to use it.

 Those users can then go to a certain web address, log in with credentials and click on an icon on that page for that application.

 It will then appear as though the remote application will start and run on their remote computer, when the application is being executed on the Citrix server and screenshots and mouse/keyboard inputs are being sent back

 The application running on the server is available on their computer so the application need not be installed on the local machine.

 The remote application can be minimized / maximized / resized just like any other local application.

 Using drive mapping, files can be also be opened on and saved to the local computer that the user connected from.

 How this works ?

ICA Protocol
This Protocol Connects the client to the server The Communication happens using the ICA Protocol This is optimized for WAN Connections

 Means ICA will not transfer the entire data from server to client instead it pushes the screen updates and mouse keyboard changes.

RDP vs. ICA

Both are very similar to each other RDP is from Microsoft ICA is from Citrix

ICA with SMB

For file sharing

SMB

Client

SMB

File Server

 In this the client is trying to connect to File server The user is trying to open some file from the server Assume the file size is 10MB File is transferred through SMB File transfer is slow as SMB will transfer entire file to the client system

ICA

Client

ICA

Citrix Server

 In this Client is trying to connect to the File Server using Citrix Server ICA is used here for communication ICA will send only screen updates and mouse keyboard changes to the client instead of entire 10 MB file Transfer rate is faster Even the bandwidth is low it will not affect much

 In WAN ICA is ideal for file sharing

Features of Citrix Presentation Server 4.0

User Experience
Smooth roaming for smart card users Multi-monitor improvements Quick Launch Bar for Program Neighborhood Pass-through of Windows key combinations Dynamic multi-language user interface support for Web Interface Simplified customization of Web Interface Support for operating system file locking rules

Application Compatibility
Application isolation environments Virtual IP addresses

Connectivity and Device Support

Universal print driver Print provider and port monitor improvements Session printers policy USB synchronization for PocketPC USB support for TWAIN devices

Scalability and Performance

CPU utilization management Virtual memory optimization Improved remote file access and directory browsing

Security
Improved smart card support Smart card PIN handling Safe scripting enhancements of ActiveX Support for HP Protect Tools Add SecurID and Safeword to JSP site

Licensing
The License Management Console can now be run with either Apache HTTP Server or Internet Information Services (IIS) as its Web server.

Citrix Presentation Server 4.5

Reasons for upgrading to Citrix Presentation Server 4.5

Application streaming
No need to install applications on each target device.

Alternate Profile Configuration

Can manage a single application package across multiple application hubs

Offline application availability

Can configure users and groups that can use applications while disconnected Applications are streamed to the users device and persist in a local cache. Users then access applications in the same manner as if they were installed

Application lease period

Can set offline availability for an application
Users must reconnect to the network prior to the end of the lease period or the application cannot be used.

Like this we can control license within the environment.

Application Isolation Environment

Allowing applications that are incompatible with each other Applications delivered locally to the users device. can control the level of communication allowed between installed and isolated applications using isolation rules.

TWAIN device support

This allows transparent use of client-attached imaging devices from applications

Application Hub
Application packages are stored in a centralized file share for delivery to servers or user devices.

Application Profile
A single application can have multiple variations for different Windows operating systems.

Non-Administrator Client Installation

No need to give users Administrator privileges in order to install the Citrix Receiver

Browser-only SSL VPN access

Allows users to access network file shares, Web email and internal Web sites from devices that are locked down and do not permit the downloading of any software.

Secure application access

SSL VPN gives users access to any application or network resource by supporting all TCP and UDP protocols.

Integrated endpoint scanning and extensible endpoint analysis

Clients are scanned for up-to-date security software and operating system versions. Endpoint analysis capabilities can be extended using industry-standard development tools.

Hot Desktop
Enables users to securely share workstations. Users can logon/logoff in seconds

Always-on SSL VPN access

Automatically maintains an SSL VPN connection as users roam between networks or when users are connected via unreliable links.

Multi-Lingual User Interface Support for Virtualized Applications

Provides one client package for all languages and allows user to specify language preference.

EasyCall voice services

Enables users to select any phone number in any application and initiate a phone call directly from their PC via the corporate VoIP telephony service

Click-to-conference
Enables users to click any phone number in any application and initiate a conference call directly from their PC via the corporate VoIP telephony service

Address book lookup

Gives users access to the corporate address and phone book from their desktop.

Active Directory Federation Services support

Makes it easier to extend application access to trusted partners.

AES support
Provides high performance, standards-based encryption using Advanced Encryption Standards (AES

Trusted Server Configuration

Similar to Internet Explorers trusted web sites feature, Trusted Server Configuration prevents users from accessing unauthorized servers.

Offline user groups

Enable only a subset of users to take applications offline, for the data and files to be transmitted to their local device.

Single Sign-On
Secures application logons security of all password-protected Windows applications

Password policies
Can define policies to control application password strength for any application. Password expiration can also be controlled for any application that lacks this capability.

Self-service Password Reset

Allows users to reset their domain password or unlock their Windows account through Web Interface or from the control + alt + delete logon screen.

SmartAuditor
Provides powerful application session recording for improved regulatory compliance, risk mitigation, and accelerated problem resolution.

Application Performance Monitoring

Helps to find and troubleshoot server, network and application performance issues that impact the user experience.

SmartAuditor
Provides policy-based recording of user sessions with hosted applications

Load throttling
Prevents new servers from being overloaded when they first logon to the farm by automatically biasing server load.

Creates a consistent, reliable user access.

Health Assistant
Performs continuous server health checks and automatically initiates recovery procedures.

Client Backup
URL Specifies a secondary Web Interface URL and automatically redirects traffic in the event of a primary URL disruption.

Editions of CPS 4.5

Standard Edition
For Single server

Advanced Edition
More than one server with Load balancing Includes Load Manager

Enterprise Edition
For large Environments Includes Load manager Installation Manager Resource Manager Network Manager WMI provider

Citrix Clients
Program Neighborhood Program Neighborhood Agent Web Client Java Client

Program Neighborhood
If a client needs to create his own connection to the Citrix PS then we need to install this in his system

Program Neighborhood Agent

This will help us to create shortcuts in the startup menu or Desktops

Web Client
Small client Users will not have any rights to create their own connections Only administrators can control This uses Web Interface

Java Client

Dont have to install Non Windows clients can use this Will run like java applet JRE is required

 Components of CPS 4.5 and System Requirements

Citrix License Server

MetaFrame Presentation Server requires the presence of a MetaFrame Access Suite license server. The License Management Console must be installed on the same machine as the license server that it manages.

You can install MetaFrame Access Suite licensing on either on a stand-alone machine

Citrix License Server

Operating systems: Windows 2000 Server Family: Windows 2000 Server, Windows 2000 Advanced Server, and Windows 2000 Datacenter Server, Service Pack 3. Windows Server 2003 Family: Windows Server 2003, Standard Edition, Enterprise Edition, Enterprise x64 Edition, and Datacenter Edition. Disk space requirements: 30MB

License Management Console

Minimum browser requirement: Netscape 7.1 or Internet Explorer 5.0 Microsoft Internet Information Services (IIS) Version 5.0 or 6.0 or Apache HTTP Server 2.0.52
Sun Java Runtime Environment (JRE) 1.5.0_09.

Windows MUI Support

Citrix Presentation Server 4.5 supports Microsofts Windows Multilingual User Interface Pack (MUI) provided You must have all language settings set to English when you perform the installation You must install the English version of Citrix Presentation Server 4.5

Data Store
Microsoft Access SQL Server 2005 Express Edition, SP1 Microsoft SQL Server Oracle IBM DB2

Citrix Presentation Server

Operating systems: Windows Server 2003 Disk space requirements: 400MB for Citrix Presentation Server, Enterprise Edition 50MB for the Presentation Server Console 25MB for the Access Management Console 35MB for the Document Center Terminal Services running in application mode Java Runtime Environment Version 1.5.0_09 .NET Framework Version 2.0

Citrix Access Management Console

Operating systems: Windows Server 2003 Windows XP Professional Windows 2000 Server Professional Microsoft .NET Framework 2.0 Disk space requirements: 25MB Microsoft Windows Installer (MSI) 3.1.

Citrix Presentation Server Console

The Presentation Server Console is required to administer policies and printers. Operating systems:
Windows Server 2003 Windows 2000 Professional, Windows 2000 Server Windows XP Professional Java Runtime Environment Version 1.5.0_09. Disk space requirements: 50MB

Web Interface
Prerequisites Microsoft Internet Information Services (IIS) Version 5.0 or 6.0 (Windows components) and ASP.NET. Microsoft Visual J# 2.0. Microsoft .NET Framework 2.0 Disk space requirements:
Each Web Interface site (regardless of type) that you create: 3.5MB

Installation Manager
Can deploy applications and software to servers
Can install applications, files, service packs, and software patches to any or all servers The applications and software components that we deploy are bundled as packages.

Load Manager
Load Manager assigns the least-loaded server to run each published application. This process keeps loads lower for greater server and published application speed and efficiency. It identifies servers with high loads and provides increased server and network performance by spreading out loads more evenly.

The Load Manager Monitor tool makes it easier for you to view trouble spots on servers in the server farm so you can change load thresholds easily if bottlenecks occur.

 For Example If one server is running with 90 published application and other server is running with 95 published applications the next load will be taken by the first server as it has only 90 running applications

Network Manager
Provides systems management capabilities through third-party SNMP management consoles. Allows you to remotely monitor the status of servers and Terminate processes on servers Disconnect, log off, and send a message to an active session on a server Query operating system, process, and session information Log server traps in the event database

Resource Manager
Monitor the Resources for performance

Farm
Number of servers get collected into a Farm Farm is a boundary of management We can mange Each Servers or entire Farm based on the Administration need

Data Collector
Manage the data in the PS and Configuration of data It will have info on logon or Application usage It collects info dynamically This will change every time It collects the data for a particular zone

Data Store
Static data Will have info on published Applications Farm collection info Will not change every time When we make some changes to at farm or server level then this will be updated

LHC
Local host caching If the Server is disconnected from SQL Server then all these info will be cached locally and when the server is up it will be pushed to the server

Zone
Collection of Presentation Servers geographically In one zone at least one server will be a data collector

Published Application
If a client or a user wants to access some kind of application which is installed in the server

Published Desktop
If user wants to access entire desktop

Published content
A short cut to the installed applications We dont need to have this installed in the client side

How the client accesses the Citrix Server

The Client need not to be in the same Domain but user who accesses the Citrix Server should be the Domain user

The Client uses the Web interface to access the Citrix Server

Installation Of CPS 4.5

Prepare Windows Server Installing Terminal Server with License Installing Prerequisites Installing Citrix Licensing Server and Console Installing Citrix Presentation server

Installation of Windows Server

Install the Windows Server 2000/2003 with latest service packs and Security patches Join this to the Domain

Installing Terminal Server

Using Add/Remove Programs Windows Components Put this in install Mode You can provide License or you can give in 120 days

Installing Prerequisite
Depending upon the component what ever the prerequisite as mentioned earlier we need to install

Licensing Server
It monitors the Citrix Licenses Concurrent user License Not tied with specific user Named user License till the lease period expires user can have multiple logon to the session

http://www.mycitrix.com

C:\Program Files\Citrix\Licensing\MyFiles

You need to have these

Your My Citrix user ID and password The license code that was provided to you The host name of your license server.

 You dont have to install the License Server every time you install new Presentation Server but you need to point the License server

 Installing Presentation Server

Access Management Console

This allows us to manage the Citrix Suite Component from a single location locally or remotely

Web Interface
It makes application available for both Program neighborhood agent and Web Page

Citrix Presentation Server Console

Can mange Citrix Farms

Installing Pass-through Client

Creating Server Farms

You need to specify new or existing Need to Mention the data Store

Assigning Farm Administrator

IMA Encryption
Will have higher security If you enable this you need to enable in all the servers which join the Farm

Configuring the Session Shadowing

You can monitor and interact with user sessions

Configuring XML Service Port

By default it shares the port at 80 with IIS but we can change it. Supplies servers running the Web Interface and TCP/IP+HTTP- connected clients with the names of published applications that are available in a server farm. All the servers in the farm should use same port

Adding users to RDP group

By default this is disabled, we can add users

Installed Services

ADF Application Development Framework Installer Service

For IM to install packages or hotfixes

CPU management \ resource management service

CPU utilization / user session manager service

Licensing WMI Service

For License management

Print manager service

Printing Architecture like Driver loading It will manage universal drivers Client driver mapping It handles print sub system Work with print spooler

SMA Service
Suite Monitoring and Alerting For monitoring

Virtual memory optimization

For Virtual Memory

WMI Service
Will get in Enterprise Edition It will give some WMI Classes which we can use for scripting purpose

XTE Service
For SSL Relay Session Reliability

Licensing service
Distribution of license

Client network
Manage client device like Drive mapping

Diagnosis facility COM Server

It is a tracing facility service used by Technical Support

Encryption service
ICA Session encryption

IMA Service
Independent Management Architecture Handles connection between Presentation Server and Management Console

License Management console for Citrix licensing server

For web console of licensing

MF Com Server Service

For monitoring individual Server

RM Mail service
Sending the mail on Resource management

Secure gateway

For secure gateway

Presentation Server Clients for Windows

 Program Neighborhood Agent Program Neighborhood Web Client

Program Neighborhood Agent

Supports the full Citrix Presentation Server feature set. You can integrate published resources with users desktops.

 It is centrally administered and configured in the Access Management Console using a Program Neighborhood Agent site created in association with a site for the server running the Web Interface.

 The Program Neighborhood Agent is the client that operates with the Citrix Streaming Client to provide application streaming to the user desktop.

Access method

The Program Neighborhood Agent allows your users to access all of their published resources from a Windows desktop.

 Users work with your published resources the same way they work with local applications and files.

 Published resources are represented throughout the client desktop, including the Start menu and the Windows notification area, by icons that behave just like local icons.

 Users can double-click, move, and copy icons; and create shortcuts in their locations of choice.

 The Program Neighborhood Agent works in the background. Except for a shortcut menu available from the notification area, it does not have a user interface.

Client management and administration

You configure Program Neighborhood Agent at a site created in the Access Management Console and associated with the site for the server running the Web Interface.

 By using the Access Management Console in this way, you can dynamically manage and control your client population throughout your network from a single location and in real time.

Web Client
The Web Client is a smaller client that can be installed from a .cab file or from the main .msi file.

 The Web Client setup files are smaller than the other clients. The small size allows users to quickly download and install the client software.

Access method
If you want users to access published resources from a browser, use the Web Client.

 Users access published resources by clicking links on a Web page you publish on your corporate intranet or the Internet.

 The published resource launches either in the same window or in a new, separate browser window.

 The Web Client does not require user configuration and does not have a user interface.

Client management and administration

You can use the Web Client to access resources available from the Web Interface Publish links to your resources with the Web Interface

Program Neighborhood
Program Neighborhood supports the full Citrix Presentation Server feature set

 It requires user configuration and maintenance.

 Use Program Neighborhood if you are not using the Web Interface to deliver resources.

 Program Neighborhood cannot be configured from a centralized site, such as the Program Neighborhood Agent site

 It does not require the Web Interface.

Access method
If you want users to access your published resources from within a distinctive user interface, use Program Neighborhood.

 Using Program Neighborhoods own user interface, the Program Neighborhood window, users can browse for groups of published resources Can create custom connections to individual published resources or to computers running Citrix Presentation Server.

 Icons representing application sets and custom ICA connections appear in the Program Neighborhood window.

Client management and administration

You can set up scripted updates for Program Neighborhood Users can also configure options for Program Neighborhood using its interface.

New Features in client for Windows

Client Version is 10.x Supports Windows NT 4.0, Windows 2000, Windows 2003, Windows XP and Legacy PCs operating systems.

 Has backward compatibility

 Added advantage Supports

Windows XP (x64 edition) Windows XP Embedded

 Application streaming

 Non-administrator client installation.

 Trusted server configuration.

 Multilingual User Interface (MUI).

 32-bit color icon support.

 Program Neighborhood Agent backup URL support.

 SpeedScreen Multimedia Acceleration.

 Enhanced proxy detection support.

Discontinued Features
Client Auto update

 IPX, SPX, NetBIOS Protocols are not Supported

 ICA Dial-In Connections

Installing PNAgent
Since the release of Citrix Presentation Server 4.5, there no longer are separate Web and PNAgent.exe clients. Instead, there are new, non-admin Microsoft Installer (MSI) client and icaweb.cab files that can be deployed with previous versions of Web Interface.

 To deploy the icaweb.cab file: 1. Download the icaweb.cab client from www.citrix.com
Or copy it from the Presentation Server 4.5 component CD-ROM and place it in the following directory on the Web Interface 4.0 or 4.2 Web server:
\Program Files\Citrix\Web Interface\4.x\ICAWEB\en\ica32

 2. In the Manage Client Deployment section of the MetaFrame Presentation Server Admin tool, make the following changes to the Web Client Settings section:

 The Version and Class ID varies depending on the version of client you are deploying. You can find this information in the icaweb.inf file

 3. Enable Automatic client updates.

This setting can also be found in the Manage Client Deployment section.

 To test this, have a user (with a 9.x client for example) log on to Web Interface. The 10.x client is automatically deployed.

To deploy the ica32web.msi file:

1. Download the ica32web.msi client from www.citrix.com and place it in the following directory on the Web Interface 4.0 or 4.2 Web server:
\Program Files\Citrix\Web Interface\4.x\ICAWEB\en\ica32

 2. In the Manage Client Deployment section of the MetaFrame Presentation Server Admin tool, make sure the Display installation caption setting is set to Yes.

 3.

Open the WebInterface.conf file (from \inetpub\wwwroot\Citrix\MetaFrame\conf folder) with Notepad and change the following line: Win32Client=Default

To:
Win32Client=Download the ICA Client for Windows&/Citrix/MetaFrame/ICAWEB_common/en/I ca32/ica32web.msi

 4. Save the WebInterface.conf file

 To test this, open the Web Interface site in a browser. The Message Center should now display the link to the Microsoft Installer (MSI) package instead of ica32t.exe.

Deploy the ICA Web Client Through Web Interface 4.5

By default, Web Interface 4.5 automatically deploys the Microsoft Installer (MSI) packager. The file is located in the Web Interface Server

\Program Files\Citrix\Web Interface\4.5\Clients\ica32\

Creating the Packager for Web Interface 4.5

1. Copy the client packager (Ica32pkg.msi) from the components CD-ROM to a local directory on the Web server. 2. Give this at a command prompt:

msiexec.exe /a <path>/ica32pkg.msi

Where the path is your file location

 2. Select the location to store the file for deployment to Web Interface users. The default location is
\Program Files\Citrix\Web Interface\4.5\Clients\ica32\ica32pkg.msi

4. Accept the license agreement. 5. Select the client you want the users to install.

6. Choose whether you want the user to install the single sign-on option 7. Choose whether you would like the user to upgrade or downgrade an existing client version.

8. Select the option you want users to see during the client installation. 9. Follow the wizard to the end and click Finish. 10. Configure Web Interface to deploy the ica32pkg.msi file automatically.

 11. In the Access Suite Console, highlight the Web Interface 4.5 site and go to Manage application types and client deployment > Manage client deployment > Client updates and select the Automatically update the Clients for Windows at logon check box.

Creating Client packager for Web Interface 4.5.1

Web Interface 4.5.1 can deploy the ica32web.msi file. Unlike the ica32pkg.msi file, the ica32web.msi file does not install Program Neighborhood or the Program Neighborhood Agent. It only the installs the Web Client used by Web Interface to launch applications on the users workstations.

Web Interface 4.5.1 automatically deploys the ica32web.msi file from the WIONLY directory. \Program Files\Citrix\Web Interface\4.5\Clients\WIONLY. You can manually create this directory or copy over the entire Clients directory from the components CD-ROM.

 If the WIONLY directory is not present, Web Interface 4.5.1 defaults to deploying the ica32pkg.msi file from the Clients\ica32 directory. When the installation caption is set to Always, Web Interface 4.5.1 also calls the ica32web.msi file.

Creating MSI Package and keep in Network Folder

1. Copy the Client Packager (Ica32pkg.msi) from the Components CD to a local directory. 2. Create a share point on a file server that is accessible to your users. The Client Packager Setup wizard appears.

 3. Type the following at a command prompt: msiexec.exe /a path/ica32pkg.msi The Client Packager Setup wizard appears.

 4. Enter the UNC path to the network share point where you want to store the customized package.

 5. Select your compression option and click Next. 6. Select one or more clients to be included in the install package. If you select Program Neighborhood or Program Neighborhood Agent, the Setup wizard for each client appears.

 7. On the Upgrade Settings page, choose whether or not the install package can upgrade or downgrade existing clients. 8. On the Select User Dialog Boxes page, specify the dialog boxes displayed to users when they run the install package. 9. Verify your selections on the summary page and click Finish. The install package you specified above is created in the specified UNC path.

Installing clients using AD

Create a package
msiexec.exe /a path/ica32pkg.msi
Copy this in network share Open Group Policy Create a package Publish the package Assign the Package

 When the user logs on or the system starts the client is deployed

Installing Clients Manually

Enabling Download of ica32t.exe Client Install on Web Interface 4.5

By default, Web Interface 4.5 pushes the Ica32Pkg.msi file instead of ica32t.exe. This may cause problems for customers who do not wish to push an MSI file. The link in the Message Center to download the file will link to the ica32.exe file.

 We need to Change this

1. Copy the ica32t.exe file to the \Programfiles\citrix\WebInterface\4.5\Clients\ica32 folder on the Web Interface Server

 2. Open the WebInterface.conf file located in \inetpub\wwwroot\citrix\AccessPlatform\conf.

 3. Locate the line that reads: Win32Client=Default 4. Change it to read: Win32Client=Citrix ICA Client for Windows&/Citrix/AccessPlatform/Clients_comm on/ica32/ica32t.exe

 5. Save the file. The link in the Message Center to download the file should now link to the ica32t.exe file.

Configuring Web Client

Using the Client for Web

Configuring Program Neighborhood Agent

Using the Program Neighborhood Agent

Configuring Program Neighborhood

Using the Program Neighborhood

Securing Client access

Configuring Authentication for Workspace Control

Configuring Kerberos Logon

Using Smart Cards

Using the IMA Encryption Utility

Configuring Authentication for User

Using ICA Encryption

Installing Certificates

Configuring and Running Discovery in Web interface

Creating Sites
Use the Create site task in the Access Management Console to create one of the following sites: Access PlatformFor users accessing applications using the Web Interface. Program Neighborhood Agent ServicesFor users accessing applications using the Program Neighborhood Agent. Conferencing Manager Guest AttendeeFor users logging on to Guest Attendee conferences.

Automatically Deploying the Client for Java

You can configure the Web Interface to automatically deploy the Client for Java if a client is not installed on the users local machine.

 To enable automatic fallback to the Client for Java 1. Click the Manage client deployment task. 2. Select Remote clients. 3. Select the Native client and/or Embedded native client check boxes.

 4. Select the Client for Java check box. 5. In the Fallback to Client for Java area, select the Automatic fallback to the Client for Java check box. 6. Click Finish to accept the changes.

Publishing Resources

Application
Applications installed on servers running Citrix Presentation Server. When users access them, the published applications appear to be running locally on client devices.

Content
Data files such as Web pages, documents, media files, spreadsheets, and URLs. In Citrix Presentation Server, the combined total of data types you can publish is referred to as content.

Desktop
The servers desktop, so users can access all of the resources available on the server.

Application publishing Wizard

In the Access Management Console and can be accessed in the following ways: In the scope pane, select either a farm or an application. Then select Action > New > Published application. In the scope pane, select a server. Then select Action > All Tasks > Publish application on server.

 When you publish an application, configuration information for the application is stored in the data store for the server farm.

 The configuration information includes which types of files are associated with the application; users who can connect to the application; and client-side session properties that include window size, number of colors, level of encryption, and audio setting.

Configuring User access to published application

Anonymous Explicit

Redirecting Content from Client to Server

Redirecting Content from Server to Client

Using Virtual IP Addresses with Published Applications

Creating an Isolation Environment

Implementing Resource Limits and Client Options

Configuring Resource Appearance

Modifying Published resources

Managing Published Resources

Installation Manager

 1. Identify and configure the servers you require 2. Determine the package and format you want to deploy 3. Copy packages to the network share point server 4. Use Installation Manager to deploy packages on the target servers

Example
In the following example, the administrator wants to install and publish Microsoft Word 2000 on 20 servers in a farm. This application is available as an MSI package. The administrator decides to schedule the installation for the evening, when network usage is low.

To deploy the application on 20 servers

1. The administrators will identify the target servers they want to install the Microsoft Word on and a package management Server, and then configures these servers appropriately. They also identify a suitable network share point server and configure the appropriate permissions.

2. The administrator obtains the MSI file for the Microsoft Word 2000 application and copies this file to the network share point.

3. Using the Console on the package management server, the administrator creates a server group containing the 20 target servers. They then add the package to the Installation Manager database and schedule the installation and publishing of the application for that evening.

To install Installation Manager on a server

1. Log all users off the server. 2. Close all applications on the server, including the Console. 3. Insert the Citrix Presentation Server CD-ROM in your CD-ROM drive:

To uninstall Installation Manager

1. Launch Add/Remove Programs from the Control Panel. 2. Select Citrix Presentation Server for Windows. 3. Click Change. The Citrix Presentation Server for Windows Setup dialog box appears. 4. Select Modify and click Next. 5. In the Component Selection screen, remove Installation Manager and Follow the instructions on screen.

Introduction to the Packager

The Packager is a utility that packages software components into Application Deployment File (ADF) packages, ready for deployment on servers using Installation Manager.

 You need to use the Packager only if the software you want to deploy with Installation Manager is not available in MSI or MSP format.

 You use the Packager to monitor and record the changes made when you install an application or software component.

ADF Files
When the Packager records the changes made when software is installed, it creates an Application Deployment File (ADF). This is a script file in human-readable format that contains information about the environment, resources, and files required to install and run the software on a server.

ADF Packages
An ADF package is built by the Packager. The ADF package contains the ADF file and folders containing the software installation files. The ADF package stores all the information that Installation Manager needs to recreate the software installation on target servers.

Launching the Packager

From the Start menu, click All Programs > Citrix > Citrix Presentation Server > Installation Manager Packager. The Packager window and the Project dialog box appear.

Creating an ADF Package

Creating an ADF Package Manually

Packaging an Unattended Application Manually

Rolling Back the Packager

After completing the packaging process, you can restore your packager server to its original state prior to packaging the application.

Copying a Package to a Network Share Point

Before you can add and schedule a package for deployment on target servers, the package must be on a network share point.

Copying ADF Packages

1. Manually 2. Use packager

Adding a Package to Installation Manager

You must add packages to the Installation Manager database before you can install them on target servers.

Creating a Server Group

Creating a server group saves time when installing packages to multiple target servers

Creating a Package Group

Creating a package group saves time when installing packages on multiple target servers by grouping related packages together.

Scheduling the Installation of a Package

Publishing a Packaged Application

You can publish applications on servers in your farm from the packages you create. When you publish an application, the application becomes available to your users. Users can connect to the published application and run it within a client session.

Creating an Isolation Environment

Creating isolation environments on farms enables safe installation and execution of applications.

Configuring an Isolation Environment

Using an Isolation Environment

Associating an Application with an Isolation Environment

When you associate a published application with an isolation environment, the isolation environment manages all the interactions of the published application with system resources.

Installing an Application into an Isolation Environment

You install an application into an isolation environment to keep all operations of an application completely separate from other applications on the server.

Uninstalling Applications Installed into an Isolation Environment

Publishing Applications to Isolation Environments

Deleting Isolation Environments