11. Deploying Applications Using Installation Manager Terms you'll need to understand: -
Installation Manager (IM) packages -
MSI, MSP, and ADF packages -
Package management server -
Network share point server -
Package server -
Target server -
Installer and Packager services -
Server and package groups -
APPUTIL Concepts you'll need to master: -
Identifying the components of Installation Manager and understanding the role they serve -
Identifying the default package source location and Windows authentication account -
Choosing the default Installation Manager options that best meet the needs of a particular deployment scenario -
Creating server and package groups -
Monitoring the status of a package deployment -
Scheduling the uninstall of package -
Deploying packages using application publishing In Chapter 10, "Application Integration," we reviewed application deployment and Citrix's concept of application and content publishing. While content typically resides in a central location where it is easily accessed from any server in the farm, an application must be installed on a MetaFrame server before it can be published. To ease the task of deploying an application across multiple servers, Citrix provides Installation Manager as part of the Enterprise Edition of MPS. Installation Manager (IM) allows you to centrally manage the attended or unattended installation of applications and other software components (specific files, service packs , software patches, and so on) to the servers in your server farm. The applications and other software components being deployed are referred to as packages . As the number of servers in the farm increases , the usefulness of IM becomes more and more apparent. Installation Manager provides the following: -
It allows centralized, rapid deployment of application packages. Any MetaFrame server in the farm can be used to deploy packages, regardless of its location, connection speed, or hardware configuration. -
Applications can be installed, uninstalled , and repaired using Installation Manager. -
Application packages that have been created in IM can be published and automatically deployed to the target servers in the farm. You do this through the Application Publishing Wizard, which we discussed in Chapter 10. Installation Manager adds the Installation Manager Package option to the list of application types that can be published. When an IM package is published, it is automatically installed and then published for the specified users. -
Packages can be deployed immediately or scheduled for a time that is appropriate for the environment. Application installation, removal, publishing, and even repair can be scheduled to run automatically without administrator intervention. If necessary, a server restart can also be initiated immediately after the completion of the package deployment, ensuring that the application and the server environment are ready for use. -
Multiple packages can be managed as a single logical package through package groups. Within a package group, you can specify the installation sequence for all child packages, so when a single package group is deployed, all components are installed in the correct order. Package groups simplify the process of deploying multiple related packages to MetaFrame servers in the farm. -
IM supports the following three package formats: -
MSI These packages are based on the Microsoft Windows Installer Service. Many common software products such as Microsoft Office ship with MSI-based installation files, which can be used within IM to deploy the application. MSI files also support the use of transform files (usually with .mst extensions). Transform files modify the default behavior of the installation package and are most often used to tailor an MSI installation for a specific environment such as Terminal Services. IM supports the use of transform files with MSI packages. MSI files can also be created using software deployment tools such as InstallShield. MetaFrame does not include tools for creating MSI packages. -
MSP MSP files are also based on the Microsoft Windows Installer Service and are typically used to patch or update an existing application deployed using an MSI package. MSP packages are usually provided by software manufacturers to patch their products and can also be created using software deployment tools. MetaFrame does not provide tools for creating MSP packages. -
ADF Application Deployment File packages are created using the Packager application that is provided as part of Installation Manager. ADF packages are most often created when an application must be deployed and it does not already provide an MSI or MSP package. We review ADF package creation in the "Creating ADF Packages Using the Packager Utility" section later in this chapter. -
Installation Manager supports access delegation to MetaFrame administrators. Access to view and edit the Installation Manager configuration is supported, as well as the delegation of rights to install and uninstall packages on servers within a server group. These install/uninstall access management rights were not available in MetaFrame versions prior to 3.0. Alert Know that the install/uninstall access management rights are defined within a server group, and not within Installation Manager or a package group. View/edit rights apply to packages, whereas install/uninstall rights apply to servers.
-
Citrix provides support for managing published applications from a command prompt using the APPUTIL utility. In addition, APPUTIL also allows you to manage the installation and removal of IM packages and entire package groups from servers in the farm. You can find a full summary of APPUTIL'S features as they pertain to Installation Manager in the "Managing Packages from a Command Prompt" section later in this chapter. |
