Before you upgrade workstations to ZENworks 7, you must either upgrade the Novell Client or install the ZENworks 7 Desktop Management Agent. One of these will be used to authenticate to eDirectory. For more information about upgrading the Novell Client, see the Novell Client for Windows Installation and Administration Guide.
When you have upgraded the Novell Client and the ZENworks Server (called the “Desktop Management Server in ZENworks 7), you need to install the Desktop Management Agent on the user workstations. This installation updates the Novell Application Launcher, Workstation Manager, and Remote Management software on the user workstation. It also installs the Workstation Inventory agent and the Image Safe Data service.
You can uninstall the Novell Client from user workstations after you deploy the Desktop Management Agent as the exclusive means for users to authenticate to eDirectory. In this sense, ZENworks 7 Desktop Management can be “clientless;” that is, ZENworks 7 Desktop Management does not require the Novell Client if users log in with the Desktop Management Agent. For more information, see Using the Novell Client in a ZENworks 7 Environment
in the Novell ZENworks 7 Desktop Management Administration Guide.
The workstation functionality afforded by ZENworks 7 Desktop Management components is available only if you install the Desktop Management Agent. This is true even if you currently have the Novell Client installed on that workstation. The Desktop Management Agent installation removes the Desktop Management features that were previously installed by the Novell Client and replaces them with selected ZENworks 7 Desktop Management workstation features.
The following tasks must be performed if you want to install the Desktop Management Agent on workstations that are currently using ZENworks for Desktops 3.2 SP3:
Some issues might occur if you do not upgrade to the ZENworks 7 Desktop Management Agent in an upgrade from ZENworks for Desktops 3.2. They are detailed in the following section:
The Desktop Management Agent installation program, zfdagent.msi, requires a minimum of Microsoft Windows Installer (MSI) 1.1 during the installation process. You can upgrade Windows 98 workstations by manually installing version MSI 1.11 (or later) on every workstation prior to the installation.
The following table lists the versions of the MSI that should already be installed on Windows workstations.
Table 29-1 MSI Versions Pre-installed on Windows Workstations
NOTE:You should consider whether to upgrade all of the user workstations to use the same version of the MSI engine.
For your convenience, MSI 2.0 for Windows 2000/XP or Windows 98 is available in the \windows installer folder of the Novell ZENworks 7 Companion 2 CD or in the \microsoft windows installer folder of the Novell ZENworks 7 with Support Pack 1 Companion 2 CD.
For detailed information about Microsoft Windows Installer, see the MSI Web site.
If the MSI engine needs to be installed, you can use the Novell Application Launcher in ZENworks for Desktops 3.2 to install it with a Simple Application distribution.
Copy the appropriate MSI engine installer utility to your ZENworks Server.
(Conditional) From the Novell ZENworks 7 Companion 2 CD, copy the appropriate MSI engine installer utility to your ZENworks Server.
\windows installer\98\instmsia.exe installs the MSI 2.0 engine on Windows 98 machines.
\windows installer\nt\instmsiw.exe installs the MSI 2.0 engine on Windows 2000/XP machines.
(Conditional) From the Novell ZENworks 7 with Support Pack 1 Companion 2 CD, copy the appropriate MSI engine installer utility to your ZENworks Server.
\microsoft windows installer\98\instmsia.exe installs the MSI 2.0 engine on Windows 98 machines.
Using the newly installed ZENworks 7 Desktop Management (or SP1) snap-ins in ConsoleOne, create a Simple Application object for the version of the MSI engine you want to install.
If you want to install both versions, you must create a Simple Application object for each version.
After you name the simple application, enter the path to the location from which the application’s executable file will run. Include the executable file in the path. Because the Application Launcher will copy the file to a target directory on the workstation, specify the path as it will exist after the file is copied to the target directory.
Example: c:\temp\instmsiw.exe
Define the system requirements that a workstation must meet before the MSI engine application will be distributed to it.
For more information, see Configuring the Application in eDirectory
in the Novell ZENworks 7 Desktop Management Administration Guide.
Associate the application object to users or imported workstations, then select the characteristics you want to apply to the association.
We recommend that you select the characteristic for the association so that the Application object runs as soon as the Application Launcher or Workstation Helper starts and the Application object is available.
For more information, see Configuring the Application in eDirectory
in the Novell ZENworks 7 Desktop Management Administration Guide.
Configure the Simple Application object.
In the Application object Properties page, click the tab > .
You need to add the file to the Application Files list so that the Application Launcher copies it to the workstation. For more information, see the online help in ConsoleOne.
Click , click , then fill in the following fields:
Source File: Select the MSI engine installer utility you want copied to the workstation (for example, q:\public\zenworks\instmsiw.exe).
Target File: Enter the full path, including the file name, where you want the file copied (for example, c:\temp\instmsiw.exe).
Click to add the file to the list, then click to save the Application Object information.
If you are installing to Windows 2000 or Windows XP, in the Application object Properties page, click the tab > > select the option, set the to , then click to save the Application object information.
If you selected on the tab, the MSI Engine is installed as soon as the Application Launcher starts and the Application object is available.
The MSI engine installs an executable that is used later for installing the Desktop Management Agent MSI. The MSI engine installer utility installs this file, called msiexec.exe, in the windows_drive:windows_directory\system directory of the workstation.
The zfdagent.msi package is a complex application that installs many files and makes many configuration changes to the workstation. The most efficient method for installing the Desktop Management Agent is to distribute it to workstations as an MSI application using the Novell Application Launcher. The Novell Application Launcher not only distributes the Agent MSI package, it also calls the Windows Installer to perform the installation on the workstation.
This section provides the steps for configuring the MSI package for distribution with the Application Launcher, including:
In ConsoleOne, right-click the container where you want to create the Application object, click > click to display the New Object dialog box.
In the New Object dialog box, click to display the New Application dialog box.
In the New Application dialog box, select the option, then click .
Specify the path to the network location where you copied the .msi file.
Click , then modify the fields as necessary to customize the Application object.
Click, then define the distribution rules that a workstation must meet before the Agent MSI will be distributed to it.
Click , then associate the Agent MSI Application object with the users or workstations to where you want to distribute it.
Click , review the Application object settings, then click to create the Application object.
IMPORTANT:Before you distribute the Agent MSI (or any MSI package) using the Novell Application Launcher, you should make sure the Agent MSI application object is set to e and that the user credentials on the local workstation, in eDirectory, and in Active Directory (if used) are synchronized.
For more information about creating an MSI Application object, see Creating the Application Object from a Windows Installer (.MSI) File
in the Novell ZENworks 7 Desktop Management Administration Guide.
By default, all of the following features are installed by the ZENworks 7 Desktop Management Agent MSI package:
Application Management: Uses the Novell Application Launcher to provide users access to workstation applications that the administrator can install and then manage.
Workstation Manager: Lets administrators configure and manage workstations by using eDirectory.
Workstation Inventory: Helps administrators collect hardware and software inventory information from scanned workstations. Workstation Manager is selected by default when you select this feature.
Remote Management: Lets an administrator manage remote workstations from a management console.
Mirror Driver: Provides video adapter independence and co-existence with other Remote Control Solutions. If this feature is selected, the MSI installation overrides video driver checks and suppresses any Windows messages. If you do not want this driver, you can deselect it (optimization will be disabled).
The Mirror Driver is not yet signed by Microsoft.
Workstation Imaging: Lets an administrator take an image of a workstation's hard drive and put it on other workstations over the network.
If you want to modify this default install, you can add MSI features as public properties of the zfdagent.msi Application object. Use the following steps to modify the list of installed features:
On the Properties page of the tab of the Application Object, click to display the Select Property to Add dialog box.
In the field, enter ADDLOCAL (this is case sensitive) as the property name, then specify the property’s value in the field. Use one or more of the following feature names as a property value:
ApplicationLauncher
WorkstationManager
RemoteManagement
MirrorDriver (this property does not work unless you add the RemoteManagement property)
Imaging
Inventory
You can add more than one of these values to the list by separating them with a comma (no spaces). For example, if you wanted to add Application Launcher and Workstation Manager as features, you would type ADDLOCAL as the property and ApplicationLauncher,WorkstationManager as the values for that property.
Click to add the property to the list.
Other properties you can modify and their values (including definitions for the values) are listed in the table below. If one of these properties is listed without a value, the MSI package uses the default value.
Table 29-2 Properties and Values Available for the Desktop Management Agent MSI Application Object
If Symantec PCAnywhere* 10.x (or an earlier version) is installed on the managed device, and if you are upgrading the Remote Management Agent, you need to know the following information:
Selecting the option during the Desktop Management Agent installation might cause the managed device to shift into low resolution or VGA mode. This occurs because PCAnywhere does not support coexistence with Remote Control solutions that are based on hook driver technology. The Remote Management hook driver that shipped with ZENworks 6.5 (and later) has been deprecated and is not installed on the managed device during upgrade.
NOTE:You need to execute these steps only once. Because subsequent upgrades do not require these steps, we recommend that you select the option during installation.
To resolve this issue:
Reinstall the system video driver on the managed device.
Reinstall PCAnywhere on the managed device.
Install the ZENworks Management Agent with the option selected.
If you choose not to select the option, you do not encounter the low resolution or VGA screen problem. However, the remote sessions are not optimized for performance without Mirror Driver selected. For this reason, you need to launch rmsetdrv.exe to enable the hook driver, which was deprecated beginning with ZENworks 6.5.
Install the ZENworks Management Agent without selecting the option.
Run rmsetdrv.exe /hook.
NOTE:Because you must launch rmsetdrv.exe every time you upgrade the agent without selecting the option, and because the hook driver was deprecated beginning with ZENworks 6.5, we recommend that you select the option during the agent upgrade.
For more information on rmsetdrv.exe, see TID 10089810 in the Novell Support Knowledgebase.
If you want to install to a single workstation at a time, you can install zfdagent.msi manually. For more information, see Section 12.2, Manually Installing the Desktop Management Agent.
When completed with both manual command line parameters and MSI installation properties, the parameter field might look like this:
/i zfdagent.msi /qb STARTUP_APPEXPLORER=1
Because the field of the Application object has a line length limitation, you might not be able to add a large number of MSI Installation properties. To work around this limitation, you can do one of two things:
Use the AdminStudio ZENworks Edition to create an .mst file.
For more information about using AdminStudio, see the AdminStudio ENworks Edition Installation Guide.
Use the Microsoft MSI editor, orca.exe, to edit the property table of the zfdagent.msi file and add all of the Desktop Management Agent MSI installation properties you want. You can then install the edited MSI with all of the newly-added properties included.
For information about how to install and use orca.exe, see the Microsoft Knowledgebase Article 255905 at the Microsoft Support Web site.
The following issues might occur if you do not install the ZENworks 7 Desktop Management Agent on workstations when upgrading from ZENworks for Desktops 3.2:
If you upgrade a ZENworks Desktop Management Server from ZENworks for Desktops (ZfD) 3.2 SP3 to ZENworks 7 and then you subsequently reimage the workstations in the environment with a ZfD 3.2 image, or if you remove the Novell Client from the existing ZfD 3.2 workstations and then reinstall it, workstation associate applications might not display on these workstations.
If you need to reimage a ZfD 3.2 workstation or remove the ZfD 3.2 client from a workstation prior to it being upgraded to ZENworks 7.x Desktop Management, you should subsequently install the ZENworks 7 Desktop Management Agent on that workstation. Doing so causes the workstation associated applications to reappear.
If you upgrade a ZENworks Desktop Management Server from ZENworks for Desktops (ZfD) 3.2 SP3 to ZENworks 7.x and then you subsequently reimage a Windows 98 workstation in this environment with a ZfD 3.2 image, or if you remove the Novell Client from the Windows 98 workstations in this environment (where ZfD 3.2 is installed) and then reinstall the client, the Novell Application Launcher fails to run on the workstation.
The issue occurs because the application file storage location that used in ZfD 3.2 Application Management (on the server) differs from the file storage location used in ZENworks 7 Application Management (on the workstation).
If you need to reimage a ZfD 3.2 Windows 98 workstation or remove the ZfD 3.2 client from a Windows 98 workstation prior to it being upgraded to ZENworks 7.x Desktop Management, you should subsequently install the ZENworks 7.x Desktop Management Agent on that workstation. The newer version of the Desktop Management Agent recognizes the current location of the application files that have been distributed to the workstation.