Citrix states in their article: CTX101703

CTX101703 - Installing and Uninstalling MetaFrame XP Post FR2 Hotfixes

This document was published at: http://support.citrix.com/kb/entry.jspa?externalID=CTX101703

Document ID: CTX101703, Created on: Mar 26, 2003, Updated: Jun 7, 2003

Products: Citrix MetaFrame XP 1.0 for Microsoft Windows 2000

Installing and Uninstalling MetaFrame XP
Post Feature Release 2 Hotfixes

.MSI Hotfix Package Installation and Uninstallation Notes

Version 1.4

Table of Contents

OVERVIEW 3

General Local Methods for Installation and Uninstallation 3

General Local Installation Methods 3

General Local Uninstallation Methods 3

Active Directory Methods for Installing and Uninstalling 3

Install the Hotfix Using Active Directory 3

Uninstalling the Hotfix Using Active Directory 4

Installing a Replacement Hotfix using Active Directory 5

Uninstalling a Replacement Hotfix Using Active Directory 5

MetaFrame XP Feature Release 2 Installation Manager Methods for Installation and Uninstallation 5

Installing the Hotfix Package Using Installation Manager 6

Uninstalling the Hotfix Package Using Installation Manager 6

Command Line Switch Methods for Installation and Uninstallation 6

Other Switches 6

ICA and RDP Methods for Installation and Uninstallation 7

Installing a Hotfix Using ICA and RDP 7

Uninstalling a Hotfix Using ICA and RDP 7

Replacing Hotfixes with Newer Hotfixes: Methods for Installation and Uninstallation 7

Installing a Replacement Hotfix Using General Methods 8

Uninstalling a Replacement Hotfix Using General Methods 8

Troubleshooting 8

Identifying the Method used for Installation 8

Using GUID 8

Creating an Error Log File 8

Reinstalling if hotfix /r Command Fails 10

The Hotfix does not Appear in Add/Remove Programs 10

Overview

Following the release of MetaFrame XP Feature Release 2, MetaFrame hotfixes are being released as a Windows Installer (.msi) application package. New methods for installation, uninstallation, and troubleshooting tips for the .msi package hotfixes are described in this article.

General Local Methods for Installation and Uninstallation

General Local Installation Methods

Citrix recommends the following methods for installing .msi hotfixes:

• Double-clicking the hotfix.msi file

• Right-clicking the hotfix.msi file and choosing install

• Using Add/Remove Programs from the Control Panel and choosing the hotfix.msi file

• Typing msiexec /I .msi at a command prompt

NOTE: A local installation is when the hotfix software is located on the local server prior to installation.

General Local Uninstallation Methods

If you used local installation to install the hotfix, you can uninstall the hotfix using the following recommended methods:

• Use Add/Remove Programs from the Control Panel.

• You can browse to the .msi file, right-click the hotfix.msi file, and choose uninstall.

• Type msiexec /x .msi at a command prompt in the same local directory where the .msi file is located.

Active Directory Methods for Installing and Uninstalling

Install the Hotfix Using Active Directory

1. Verify that the servers are part of the Active Directory domain.

2. Configure the Active Directory as follows:

• Launch the Microsoft Management Console to access the Active Directory.

• Add the Active Directory Users and Computers snap-in (if it is not there already).

• Create a new Organizational Unit under the Active Directory tree.

• From the Computers folder, move the MetaFrame XP Feature Release 2 servers that are in the farm and need the hotfix to the new Organizational Unit.

• Right click the new Organizational Unit. Choose Properties, and then click the Group Policy tab.

• To add a new Group Policy Object, choose New and type a name for the new policy.

• Highlight the new policy and click Edit.

• The Group Policy window opens.

• Under Computer Configuration, expand Software Settings and click Software Installation.

• Right click Software Installation. Select New > Package and browse to the location of the package.

• The Deploy Software dialog box opens and prompts you to choose Assigned or Advanced publish or assigned. Choose Assigned.

NOTE: You can access the Properties of the software installation package if needed later to access the “Advanced publish or assigned” properties.

3. To install the hotfix, reboot the MetaFrame XP Feature Release 2 servers that need the hotfix. Upon reboot, Active Directory installs the hotfix and starts an automatic reboot of your server. When the server is finished rebooting, verify the hotfix.msi packages were installed (type hotfix /v at a command prompt or look in the Citrix Management Console).

Uninstalling the Hotfix Using Active Directory

To uninstall the hotfix using the Active Directory, go to the Active Directory Users and computers snap-in. Right click the Organizational Unit that contains the Group Policy Object.

If you want to uninstall the hotfix from all the servers in the group, remove the .msi package from the Group Policy Object and Active Directory will remove the hotfix the next time the servers reboot.

Additionally, even if you used Active Directory to install the hotfix, you can remove the hotfix on individual servers using the “General Local Uninstallation Methods” detailed above.
From Microsoft: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q314934#4

WARNING: Make sure you do not delete the Group Policy Object if you want to uninstall the hotfix from the servers.
From Microsoft: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q240976

Installing a Replacement Hotfix using Active Directory

When you add a hotfix software package in the Group Policy Object, the Deploy Software dialog box opens and prompts you to choose Assigned or Advanced publish or assigned. Normally, you choose Assigned.

NOTE: You can go into the properties of the software installation package if needed later to access the “Advanced publish or assigned” properties.

Continue to set-up the hotfix software package as instructed in the “Install Hotfix Using Active Directory” section above.

For replacement hotfix software packages, you can go into Properties
for further customization. On the Upgrade tab, you can specify packages that this package will upgrade and pick the hotfix that it replaces. Choose Package can upgrade over the existing package in the Add Upgrade Package window. If you specify this, when you verify installation using the hotfix /v command, you will see only the most recent hotfix.

If you added the hotfix without further customization, when you verify installation with the hotfix /v command, all hotfixes are listed, including those which are replaced.

Uninstalling a Replacement Hotfix Using Active Directory

If you customized your Active Directory Group Policy Object so that a newer hotfix replaces an older hotfix, when you uninstall the newer hotfix, the server hotfix level reverts to the older hotfix.

MetaFrame XP Feature Release 2 Installation Manager Methods for Installation and Uninstallation

NOTE: For additional information about how to use Installation Manager to deploy .msi packages, see the Citrix MetaFrame XP Feature Release 2 Administrator’s Guide. Using this method allows you to install the hotfix on a group of servers in a MetaFrame farm simultaneously.

Installing the Hotfix Package Using Installation Manager

1. For this scenario have 2-3 servers in the farm.

2. Configure Installation Manager properties; that is, a network share account, default file path, and so on.

3. Add an .msi hotfix package from the share you created.

4. Right-click the package and install it (select the available servers in the farm and schedule to deploy now as well as later, forcing a reboot).

5. After the servers reboot, verify that the hotfix package is installed on all servers (c:\hotfix /v).

Uninstalling the Hotfix Package Using Installation Manager

NOTE: You can type msiexec /x at a command prompt to uninstall hotfixes installed with Installation Manager. However, in the Citrix Management Console, Installation Manager still shows the package as installed, even though you uninstalled it locally. This is a known limitation of Installation Manager for any .msi package.

If you use Installation Manager to install the hotfix, you cannot use the first two methods of local uninstallation procedures to remove the hotfix. In this case, Citrix recommends that you remove the hotfix .msi package from Installation Manager and let Installation Manager remove the hotfix.

Command Line Switch Methods for Installation and Uninstallation

Type msiexec /i .msi at a command prompt to install the hotfix.

Type msiexec /x .msi at a command prompt to uninstall the hotfix.

Other Switches

At a command prompt, type hotfix /List or /L to display a list of all installed hotfixes. If you specify a hotfix name, a detailed listing of the specific hotfix is displayed.

ICA and RDP Methods for Installation and Uninstallation

Installing a Hotfix Using ICA and RDP

You can use the “General Local Installation” methods from an ICA or an RDP session.

NOTE: To install a hotfix in an ICA or an RDP session to a mapped drive, you need to use the full UNC path. You cannot use a mapped drive letter as part of the installation command.

To install an .msi package in an RDP/ICA session, you cannot use a mapped network drive. For example, if the package XE102W001.MSI is at \\Server\Public\XE102W001.MSI, the following procedure will fail:

C:\>net use e: \\Server\Public

C:\>e:

E:\>msiexec /I XE102W001.MSI

However, the following procedure succeeds:

C:\>msiexec /I \\Server\Public\XE102W001.MSI

Uninstalling a Hotfix Using ICA and RDP

You can use the “General Local Uninstallation Methods” from an ICA or an RDP session. If you installed the hotfix to a mapped drive, uninstall the hotfix with the original UNC path you used for installation.

Replacing Hotfixes with Newer Hotfixes: Methods for Installation and Uninstallation

Some hotfixes replace older hotfixes. The hotfix readme file lists the hotfixes that the newer hotfix replaces. For example:

Filename: XE102W005.MSI

For: MetaFrame XP 1.0 for Windows 2000

Replaces: XE102W002

Date: May 29, 2002

Language supported: English (US)

Installing a Replacement Hotfix Using General Methods

Use the “General local Methods” of installation recommended previously. After installing a newer hotfix that replaces an older hotfix, type hotfix /v at a command prompt to verify the installation. This lists the hotfix that was replaced and the name of the hotfix that replaced it.

Uninstalling a Replacement Hotfix Using General Methods

You can remove a hotfix that replaces a previous hotfix using the “General Local Methods” mentioned above. After reboot, the MetaFrame XP Feature Release 2 server reverts to the previous hotfix level.

If you try to remove an older hotfix after it is replaced by a newer hotfix, you will get an error message. The .msi hotfix package continues to uninstall. When you type hotfix /v the hotfix might still be listed as installed. In this scenario, follow the instructions in the error message and type hotfix /r at a command prompt to completely remove the package.

NOTE: For information about Active Directory installation of a replacement hotfix, see the Active Directory section.

Troubleshooting

Identifying the Method used for Installation

Use the Citrix Management Console to view the user who installed the hotfix. This information is available from the Hotfix tab of the server Property. If you use the local installation method, the install user name is the current logon user context. If you use the Active Directory Group Policy Object method, the install user name is SYSTEM. This is because the Active Directory Group Policy Object installs the .msi package before the user logs on, so the installation runs under the SYSTEM context. If you use Installation Manager, the install user name is the network user account you specified for Installation Manager because Installation Manager impersonates that account before the installation.

Using GUID

If you do not have access to the hotfix .msi file and you want to remove the hotfix, type msiexec /x , where ProductCode is the globally unique identifier GUID. You can use the Orca Database Editing Tool to view the Product Code. It is listed as the value in the ProductCode row within the Property table of the .msi package that contains the hotfix. For instructions about downloading and using Orca, see Microsoft’s Web site at http://www.microsoft.com.

Creating an Error Log File

Use the following article related to command line switches to create an error log file for Msiexec.exe. You can create error log files for install or uninstall. An example command to create an error log for an install is:

msiexec /i
\hotfix.msi /l*v c:\temp\hotfix.log

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/ove...

Reinstalling if hotfix /r Command Fails

The command hotfix /r is generally not supported for .msi hotfixes (hotfix /r is a legacy command used to remove pre-MetaFrame XP Feature Release 2 hotfixes).

If you use the hotfix /r command to remove a hotfix and then
attempt to install the same hotfix using the msiexec /i command, an error message will appear because the hotfix /r command does not completely remove the .msi package. You need to remove the package by running the package, selecting Remove, and then proceeding with the uninstall. The Modify button also allows you to remove the package. Run msiexec /i again and install the package.