ZENworks 7 Desktop Management with Support Pack 1 Interim Release 4

November 18, 2009

Novell® ZENworks® 7 Desktop Management with Support Pack 1 Interim Release 4 (SP1 IR4) contains files that were updated for ZENworks 7 Desktop Management after the SP1 release. The Desktop Management product is shipped in two packages, one package for Windows and NetWare, and a second for ZENworks 7 Desktop Management Services on Linux.We recommend that you check the readme of the shipping version of ZENworks 7 Desktop Management with Support Pack 1 for issues that pertain to all of its interim releases.

This readme contains the following general information:

1.0 Readme Updates

This document was updated in the following sections on the dates indicated:

1.1 November 18, 2009

Added the following section:

2.0 Supported Platforms

Some of the platforms that ZENworks 7 Desktop Management originally supported might no longer be supported by their vendors. If you encounter issues in such platforms, we recommend you to move to one of the platforms that is supported by ZENworks 7 Desktop Management and the vendor.

For more information on the supported platforms, see ZENworks 7 Desktop Management Installation Guide.

3.0 Downloading and Extracting Interim Release 4 for Windows and NetWare

To download ZENworks 7 Desktop Management with SP1 Interim Release 4 (IR4), complete the following steps:

  1. Locate the Interim Release download at the Novell downloads Web site, then search for the ZENworks 7 product and this IR4 release.

  2. Follow the prompts to copy the download file, zdm7sp1_ir4.zip, to a suitable network path. This is the location where the self-extracting file will be decompressed.

    NOTE:We recommend that you extract this Interim Release to the root of a local drive of a Windows workstation or to the root of a network server volume because it contains directory paths that could exceed the DOS limits.

  3. From the download location, double-click zdm7sp1_ir4.zip, then extract the file contents to the current location.

    IMPORTANT:If you chose to download zdm7sp1_ir4.zip to a location that includes a space in the path, for example, c:\documents and settings\tsmith\my documents\my downloads, the .zip fails to extract. To work around this problem, run the .zip from a DOS command prompt.

    The .zip extracts a folder named zdm7sp1_ir4.

4.0 Installing the Interim Release on Windows and NetWare

We recommend that you back up your existing installation before applying the files from this interim release. The interim release installation updates a limited number of files.

NOTE:You must follow the proper installation order when you upgrade to IR4. For more information, see Interim Release 4 Installation Order.

4.1 Interim Release 4 Installation Order

Interim Release 4 is not a full overlay of ZENworks 7 Desktop Management with Support Pack 1. You must have the shipping version of ZENworks 7 Desktop Management with Support Pack 1 or ZENworks 7 Desktop Management with Support Pack 1 Interim Release 2 already installed on the server before you can install IR4. IR4 is a comprehensive maintenance release, which means that it includes all of the fixes made after Support Pack 1 shipped.

NOTE:Installing the Desktop Management Agent update included in this interim release does not require that the SP1 version of the agent be already installed.

Upgrading requires that you install IR4 to the Desktop Management Server first, then the Middle Tier Server, then the Desktop Management Agent.

4.2 Updating the Desktop Management Server

The following sections include information you will need as you install the Desktop Management Server updates for this interim release:

4.2.1 Updating a NetWare Server

Use the following steps when you install ZENworks 7 Desktop Management with SP1 IR4 on a Novell NetWare® server where you previously installed ZENworks 7 with SP1 Desktop Management Server software:

  1. Unload all copies of Novell ConsoleOne® running on the NetWare server.

  2. (Conditional for servers running Workstation Imaging) Unload imgserv.nlm or run zfdstop.ncf.

  3. (Conditional for servers running Workstation Inventory) Type the following command at the server console to unload Java:

    STOPSER *

  4. From the network location where you extracted the interim release files, open the zdm7sp1_ir4 folder, double-click winsetup.exe to start the interim release installation program, then click Installation.

  5. Click Desktop Management Services, then follow the prompts displayed by the Installation Wizard.

    The IR4 installation program updates only the ZENworks 7 Desktop Management components that you previously installed. If you want to install other components, they must be installed from the shipping version of ZENworks 7 Desktop Management with Support Pack 1 before they can be updated with this program.

  6. When the installation program is complete, reboot the server to restart the updated services.

4.2.2 Updating a Microsoft Windows Server

Use the following steps when you install ZENworks 7 Desktop Management with SP1 IR4 on a Microsoft Windows server where you previously installed ZENworks for Desktops Server software:

  1. Unload all copies of ConsoleOne running on the Windows server.

  2. From the Windows server desktop, click Start > Settings > Control Panel > NDS Services > then stop the following services:

    • imgserv.dlm
    • zenimgds.dlm
  3. From the Windows Control Panel, click Administrative Tools > Services, then stop the following services if they are running:

    • Novell Inventory Service

    • Novell Database - Sybase

    • Novell Zen Web Server

    • Wake On LAN Service

    • ZENworks Workstation Import Services

    • ZENworks Workstation Removal Services

    • any other ZENworks services listed

  4. From the network location where you extracted the interim release files, open the zdm7sp1_ir4 folder, double-click winsetup.exe to start the interim release installation program, then click Installation.

  5. Click Desktop Management Services, then follow the prompts displayed by the Installation Wizard.

    The IR4 installation program updates only the ZENworks 7 Desktop Management with SP1 components that you previously installed. If you want to install other components, they must be installed from the shipping version of ZENworks 7 Desktop Management with SP1 before they can be updated with this program.

  6. When the installation program is complete, reboot the server to restart the updated services.

4.3 Installing the Middle Tier Server

The following instructions apply when you install the ZENworks 7 Desktop Management with SP1 IR4 on a server where you previously installed ZENworks Middle Tier Server software. The Middle Tier Server IR4 installation updates a limited number of files only; it is not a complete installation.

IMPORTANT:You must follow the proper installation order when you upgrade to IR4. For more information, see Interim Release 4 Installation OrderInterim Release 4 Installation Order.

The following steps apply only to the IR4 Middle Tier Server software update.

  1. From the network location where you extracted the interim release files, open the zdm7sp1_ir4 folder, double-click winsetup.exe to start the interim release installation program, then click Install.

  2. Click Middle Tier Server.

    IMPORTANT:As the installation program initiates on a Windows server, it attempts to unload the IIS Admin Service. You must also make sure that ncplw32 and wm.exe are also unloaded before the installation proceeds.

    To do this, open the Control Panel, then click Administrative Tools > click Services, then stop the Workstation Manager service. Unload the following services that use ncplw32.dll:

    • Novell iFolder
    • Novell Application Launcher
  3. Follow the prompts displayed by the Installation Wizard.

    You will need to enter your user name and password for the server where you upgrade the Middle Tier Server to IR4.

    The IR4 installation checks the Middle Tier Server for the presence of myapps.html, the Application Browser View of the Novell Application Launcher™. If it detects myapps.html, the installation assumes that you may have previously configured it and that those settings should not be overwritten. To accommodate users who want to take advantage of the changes in IR4, the installation copies myapps.html.template, an updated version of the Browser View, to the server. To use this update, copy your customized settings from myapps.html to myapps.html.template, then rename or remove myapps.html, and then save myapps.html.template as myapps.html.

    If the installation does not detect myapps.html on the server, the program detects some settings (that is, the Middle Tier IP address), writes them to the file, and copies the myapps.html file to the server.

  4. When the installation program is complete, reboot the server to restart the updated services.

  5. At each workstation that accesses myapps.html from the Middle Tier Server, restart the Web browser, go to the myapps.html page, then accept the download of the plug-in.

    NOTE:If a workstation uses Internet Explorer as its Web Browser, do not use the Novell Delivered Applications icon on the browser toolbar to download the new plug-ins; this icon currently refers to the local copy of myapps.html (that is, c:\program files\novell\zenworks\nls\english\myapps.html).

    You must type in the address or file location of myapps.html (located on the previously updated Middle Tier Server) and launch it at least once before you can click the Novell Delivered Applications icon on the toolbar.

4.4 Installing the Desktop Management Agent

The IR4 version of the Desktop Management Agent, zfdagent.msi, is a complex application that installs many files and makes many configuration changes to the workstation using Windows Installer functionality. Interim Release 4 is a self-contained MSI package (zfdagent.msi) uninstalls any previously installed zfdagent.msi before installing itself. For in-depth information about Microsoft Windows Installer, see the MSI Web site.

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.

It is also possible to install zfdagent.msi to individual workstations using the ZENworks Desktop Management installation program (winsetup.exe). With either installation method, we recommend that you back up your existing installation before applying the files from this interim release.

IMPORTANT:You must follow the proper installation order when you upgrade to IR4. For more information, see Interim Release 4 Installation Order.

4.4.1 Manually Installing Desktop Management Agent Interim Release 4

This section includes information about manually installing the Desktop Management Agent Interim Release 4 (zfdagent.msi) to an individual workstation.

4.4.2 Installing Desktop Management Agent IR4 on Windows 98/2000/XP

  1. At the workstation, access the network location (or insert a burned CD image) of the winsetup.exe program.

  2. Click Desktop Management Agents to launch the installation program, zfdagent.msi.

  3. On the first installation page of the Installation Wizard, read the introductory text > click Next.

  4. Read the License Agreement. If you agree to the terms of the license, click Yes.

    or

    Click No if you do not agree to the licensing terms. This closes the installation program.

  5. On the Select Features page, select the features that you want to install to the workstation.

    • Application Management: This feature uses the Novell Application Launcher to provide users access to workstation applications that the administrator can install and then manage. Application Management is installed by default—even if it is not selected—to accommodate future updates to the Desktop Management Agent.

    • Workstation Manager: This feature lets administrators configure and manage workstations by using eDirectory.

    • Workstation Inventory: This feature helps administrators collect hardware and software inventory information from scanned workstations.

    • Remote Management: This feature lets an administrator manage remote workstations from a remote console.

    • Mirror Driver: This feature 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 and the default optimization driver will be installed.

    • Workstation Imaging: This feature lets an administrator take an image of a workstation’s hard drive and put it on other workstations over the network.

  6. On the General Settings page, enter the DNS name or IP address of the Middle Tier Server that the agent will be connecting to, enter the HTTP or HTTPS port number that the Apache Web Server (NetWare) or the IIS Web Server (Windows) will use to listen for the Agent login, then click Next.

    If you will not be using a Middle Tier Server, you can leave this field blank.

    IMPORTANT:When designating a secure (HTTPS) port, you must use port 443.

    The IP address or DNS name and the port number let the workstation access the Apache Web server on the Middle Tier Server, which will pass on the authentication credentials to the Desktop Management Server.

    If you are installing to a workstation that doesn’t have a Novell Client installed, you will see the Workstation Manager Settings dialog box after the General settings page. On this page, you can customize the settings for the Workstation Manager feature.

  7. On the Novell Application Launcher/Windows Startup Options page, choose to launch either the Application Explorer or Application Window (or neither) on startup, then click Next.

  8. On the Summary page, review the settings you have selected for the Desktop Management Agent installation. If they are correct, click Next. If you want to change the settings, click Back.

  9. On the Completion page, select the option to restart the workstation, then click Finish.

4.4.3 Adding Features in a Manual Installation

You can add features to individual workstations by selecting the Modify option when you run the installation program after the initial installation. This procedure requires that the installation program has access to the full zfdagent.msi (that is, from a network drive or from the local workstation).

4.5 Using the Novell Application Launcher to Distribute and Install the Desktop Management Agent

The following content is included in this section:

4.5.1 Browsing to the Extracted Management Agent MSI Packages

The interim release .zip extracts a folder named zdm7sp1_ir4. This folder contains a subfolder, named \agentinstall, which contains the following language subfolders and files:

  • chinsess\zdfagent.msi (Chinese Simplified MSI installation)

  • chinsest\zdfagent.msi (Chinese Traditional MSI installation)

  • deutsch\zfdagent.msi (German MSI installation)

  • english\zfdagent.msi (English MSI installation)

  • espanol\zfdagent.msi (Spanish MSI installation)

  • francais\zfdagent.msi (French MSI installation)

  • nihongo\zfdagent.msi (Japanese MSI installation)

  • portugue\zfdagent.msi (Portuguese MSI installation)

Use the path to the localized MSI package of your choice when you create the Application object that will be distributed to users.

4.5.2 Creating and Configuring the MSI Application Object

Use the following steps to create and configure zfdagent.msi as an Application object prior to distributing it to user workstations.

  1. In ConsoleOne, right-click the container where you want to create the Application object, click New, then click Object to display the New Object dialog box.

  2. In the New Application dialog box, select the Application that has an .MSI File option, then click Next.

  3. Specify the path to the .msi file.

    The file should be in the network location where you extracted zdm7sp1_ir4.zip, in the zdm7sp1_ir4\agentinstall\language folder.

  4. Click Next, then modify the fields as necessary to customize the Application object.

  5. Click Next, then define the system requirements that a workstation must meet before the Agent MSI will be distributed to it.

  6. Click Next, then associate the Agent MSI Application object with the users or workstations where you want to distribute it.

  7. Click Next, review the Application object settings, then click Finish to create the Application object.

For more information about creating an MSI Application object, see Creating the Application Object from a Windows Installer (.MSI) File in Configuring the Application in eDirectory in Distribution: Complex Applications in the Application Management section of the Novell ZENworks 7 Desktop Management Administration Guide.

4.5.3 Modifying MSI Features in the Application Object

By default, the zfdagent.msi in this Interim Release will install all of the features you have installed previously installed with the Desktop Management Agent, and no more. If you are installing this Interim Release (actually a new Desktop Management Agent MSI package) on a workstation for the first time, all of the following features are installed unless you deselect them:

  • Application Launcher

  • Workstation Manager

  • Workstation Inventory

  • Remote Management (with Mirror Driver)

  • Workstation Imaging

If you want to change what is installed by the new MSI, you can add MSI features as public properties of the zfdagent.msi. Use the following steps to modify the list of installed features:

  1. On the Properties page of the MSI tab of the Application Object, click Add to display the Select Property to Add dialog box.

  2. In the Value Name field, enter ADDLOCAL as the property name, then specify the property's value in the Value Data field. Use one or more of the following feature names as a property value:

    • ApplicationLauncher

    • WorkstationManager

    • RemoteManagement

      • MirrorDriver (this value can be used only with the RemoteManagement value)

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

    IMPORTANT:Command line parameters used for deploying MSI packages are case-sensitive.

  3. Click OK to add the property to the Properties list.

4.5.4 Running the MSI Application Object in Silent Mode

If you want to run the Agent MSI in silent mode, set the user interface to Silent on the Icon page of the Identification tab of the object properties.

4.5.5 Adding Properties to the MSI Application Object

You can add additional properties to zfdagent.msi. These properties and their values (including definitions for the values) are listed below. If one of these properties is listed without a value, it will use the default value.

IMPORTANT:Command line parameters used for deploying MSI packages are case-sensitive.

LOGIN_PASSIVE_MODE

The values for this property are effective only if the Novell Client is not installed on the workstation. If the Novell Client™ is already installed, the settings have no effect after zfdagent.msi installation.

If the Novell Client is removed after zfdagent.msi is installed, these settings take effect.

NOTE:If the Novell Client might be removed later and you want to use DLU, you need to assign a value of zero (0) to this property.

  • 0 Displays a Novell login at user login time.
  • 1 (Default) Does not display a Novell login, unless the Novell Client™ has been installed. If the Novell Client is installed, its login is displayed.

EDITABLE_MT_ADDRESS

  • 1 Allow the user to change the ZENworks Middle Tier IP address where authentication will take place. This is available only if the Novell Client is not installed.
  • 0 (Default) Do not allow the user to specify the Middle Tier address.

The values for this property are effective only if the Novell Client is not installed on the workstation. If the Novell Client is already installed, the settings have no effect after the zfdagent.msi installation.

If the Novell Client is removed after zfdagent.msi is installed, these settings take effect.

STARTUP_APPEXPLORER

  • 1 Launch Application Explorer on Windows startup.
  • 0 (Default) Do not launch Application Explorer on Windows startup.

STARTUP_APPWINDOW

  • 1 Launch the Application Window on Windows startup.
  • 0 (Default) Do not launch the Application Window on Windows startup.

MT_SERVER_ADDRESS

This property specifies the ZENworks Middle Tier Server IP address or DNS name. It is not necessary to specify this property if you are not using a Middle Tier Server.

HTTP_PORT

  • 0-65536 Specifies the HTTP port that will be used by the ZENworks Management Agent when communicating with the Middle Tier Server. This property must be added and its value defined if you are using a Middle Tier Server.
  • 80 Default HTTP port.

Use the following steps if you want to add any of these properties to the zfdagent.msi.

  1. On the Properties page of the MSI tab of the Application object, click Add to display the Select Property to Add dialog box.

  2. In the Value Name field, enter a the property name, then specify the property's value in the Value Data field. Use one of the properties listed above and the value you want.

  3. Click OK to add the property to the Properties list.

4.6 Distributing the Desktop Management Agent

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.

5.0 Downloading and Installing the Interim Release on Linux Servers

Interim Release 4 is not a full overlay of ZENworks 7 Desktop Management Services on Linux with Support Pack 1. You must have the shipping version of ZENworks 7 Desktop Management Services on Linux with Support Pack 1 already installed before you can install IR4. IR4 is a comprehensive maintenance release, which means that it includes all of the fixes made after Support Pack 1 shipped.

IR4 updates only the ZENworks components that were previously installed on your Linux Desktop Management server.

This section contains the following information:

NOTE:These instructions are focused only on the installation of ZENworks Desktop Management Services on Linux Desktop Management Servers. ZENworks 7 does not support Linux services on the Middle Tier Server, nor does it manage Linux desktops. Use the update instructions for Windows and NetWare platforms to update your agent and Middle Tier Server.

5.1 Downloading the Interim Release RPMs

To download ZENworks 7 Desktop Management Services on Linux with SP1, Interim Release 4 (IR4), complete the following steps:

  1. Locate the Interim Release download at the Novell downloads Web site, then search for the ZENworks 7 product and this IR4 release.

  2. Download the interim release tarball, zdmlsp1ir4.tar.gz, and extract the RPMs in a new directory.

5.2 Upgrading to ZDML 7 SP1 IR4 from ZDML 7 SP1 IR1 HP2a, ZDML 7 SP1 IR2, or Later

  1. Download the Interim Release and extract the contents of the zip file to a new directory.

  2. Run the following command to shut all services down:

    /opt/novell/zenworks/bin/ZDMstop

  3. From the directory where you extracted the contents of the zip file, run the following command to uninstall the previous version of dhost rpm:

    ./dhost_uninstall.sh

  4. Run the following commands to upgrade all of the ZENworks components that were previously installed:

    rpm -ivh novell-zenworks-zmgservices-dhost-*.rpm

    rpm -Fvh *.rpm

  5. Run the following command to start all ZENworks Desktop Management services:

    /opt/novell/zenworks/bin/ZDMstart

  6. Start /etc/init.d/novell-zdm-inv if it is in any state other than running.

    Start /etc/init.d/novell-zdm-wol if it is in any state other than running.

5.3 Upgrading to ZDML 7 SP1 IR4 from other releases

  1. Download the Interim Release and extract the contents of the zip file to a new directory.

  2. Run the following command to shut all services down:

    /opt/novell/zenworks/bin/ZDMstop

  3. From the directory where you extracted the contents of the zip file, run the following command to uninstall the previous version of dhost rpm:

    ./dhost_uninstall.sh

  4. Run the following commands to upgrade all of the ZENworks components that were previously installed:

    rpm -ivh novell-zenworks-zmgservices-dhost-7.0.1-8.version.rpm

    rpm -Fvh *.rpm

  5. (Conditional) On OES 2 platform, do the following:

    1. Change directory to /opt/novell/zenworks/bin/

    2. Run ./novell-zenworks-inv-restore.sh

    3. Change directory to /opt/novell/bin/

    4. Run ./zeninvshares and provide administrative credentials of the tree in which the server resides.

  6. Run the following command to start all ZENworks Desktop Management services:

    /opt/novell/zenworks/bin/ZDMstart

  7. Start /etc/init.d/novell-zdm-inv if it is in any state other than running.

    Start /etc/init.d/novell-zdm-wol if it is in any state other than running.

  8. Run the /opt/novell/zenworks/bin/novell-zdm-version command. Ensure that the output of the command is displayed as follows:

    ZENworks Auto Workstation Import/Removal -- 7.0.1-10
    
    ZENworks Desktop Management Agent --  7.0.1-13
    
    ZENworks Application Management --  7.0.1-4
    
    ZENworks Imaging Service --  7.0.1-8
    
    ZENworks Inventory Database -- 7.0.1-1
    
    ZENworks Inventory Proxy -- 7.0.1-2
    
    ZENworks Inventory Service -- 7.0.1-5
    
    ZENworks Middle Tier Server -- 3.1.4-20070828_154207.sles9
    
    ZENworks Application Management Database -- 7.0.1-1
    
    ZENworks PXE Services -- 7.0.1-1
    
    ZENworks Remote Management -- 7.0.1-1
    

    These version numbers indicates that the patch has been successfully applied. Version numbers are not be displayed for the components that are not installed.

6.0 Fixed Issues

For a list of the issues fixed in ZENworks 7 Desktop Management with Support Pack 1/Interim Release 4, see Novell Support site.

7.0 Known Issues

This section includes the following information:

7.1 Workstation Inventory Issues

This section contains information about the Workstation Inventory issues:

7.1.1 Unable to send scan data to a Inventory Server installed on SLES 10 SP1

The Workstation Inventory agent is unable to send scan data to a Inventory Server installed on SLES 10 SP1.

Workaround: Do the following:

  1. Install ZENworks 7 Desktop Management with Support Pack 1 Inventory Server on the SLES 10 SP1 machine.

  2. Make sure that the /etc/samba/smb.conf file has the following Samba share entries for scandir and dictdir:

    [ScanDir]
    comment = zenworks inventory share
    path = /opt/novell/zenworks/inv/ScanDir
    guest only = yes
    guest ok = yes
    writeable = yes
    security = share
    force user = inventory
    
    [DictDir]
    comment = zenworks inventory share
    path = /opt/novell/zenworks/inv/server/DictDir
    guest only = yes
    guest ok = yes
    writeable = yes
    security = share
    force user = inventory
    

    If the entries are missing, then add them to the file.

  3. Execute the following commands to make sure that the Samba service is running:

    /etc/init.d/smb status

    /etc/init.d/nmb status

    If the Samba service is not running, start the service by executing the following commands:

    /etc/init.d/smb start

    /etc/init.d/nmb start

  4. Execute the following command to make sure that the Inventory service is running:

    /etc/init.d/novell-zdm-inv status

    If the service is not running, start the service by executing the following command:

    /etc/init.d/novell-zdm-inv start

  5. Make sure that the scan data has been successfully transferred from the agent and stored on the server.

  6. Upgrade the Inventory Server to ZENworks 7 Desktop Management with Support Pack 1 Interim Release 4.

  7. Repeat Step 3.

7.1.2 Updating the software dictionary

You must manually download the dictionary from the Novell Support site and save it in the zenworks_installation_directory\zenworks\inv\server\dictdir directory on the Inventory server. For more information, see the Novell ZENworks 7 Desktop Management documentation Web site.

7.1.3 NSS Shares for inventory are not getting created on OES 2

Workaround: Perform the following steps to recreate the ZENINV Shares while upgrading the novell-zenworks-invserver-*.rpm using the interim or hot patch releases.

  1. Change directory to /opt/novell/zenworks/bin/

  2. Run ./novell-zenworks-inv-restore.sh

  3. Change directory to /opt/novell/bin/

  4. Run ./zeninvshares and provide administrative credentials of the tree in which the server resides

7.2 Remote Management Issues

This section contains information about the Remote Management issues:

7.2.1 Wake-on-LAN server is not able to wake up the device

If you create a Wake-on-LAN policy to wake up a device, the Wake-on-LAN server might not be able to read the Wake-on-LAN policy.

Workaround: Create a similar Wake-on-LAN policy to wake up the device.

7.3 Workstation Imaging Issues

This section contains information about the Workstation Imaging issues:

7.3.1 Unable to perform imaging operations on the managed device

After the installation of the agent on the device, the Workstation Object and Workstation Object ID are not listed in the ZENworks Imaging Windows Agent (ziswin).

Workaround: Manually reboot the managed device.

7.3.2 A bundle is applied to a device every time the device boots up

If a hardware rule is associated with a bundle that has only an add-on image, the bundle is applied to the device every time the device is booted to the imaging mode.

Workaround: Do one of the following:

  • Ensure that the bundle has a base image in addition to the add-on image.

  • Do not associate a hardware rule with a bundle that has only an add-on image.

7.4 Application Management Issues

If a NAL application objects distributes either a registry or INI setting and a Windows shortcut that uses one of the special Windows macros such as %*APPDATA%, %*DESKTOP%, and %*STARTMENU%, the macros might resolve to the Local Service account rather than the currently logged in Windows account.

For example, the macros that should resolve to c:\Documents and Settings\Username\Application Data actually resolve to c:\Documents and Settings\LocalService\Application Data.

Workaround: Do one of the following:

  • Replace the special Windows macros with Windows macros such as %USERPROFILE%\Application Data, %USERPROFILE%\Desktop, and %USERPROFILE%\Start Menu

  • Distribute the Windows shortcuts in a chained application that does not contain registry or INI modifications.

7.5 Workstation Management Issues

This section contains information about the Workstation Management issues:

7.5.1 The roaming profiles of a user logging out of a Windows XP managed device might not be stored in the user’s home directory on an OES 2 Linux SP1 device

If the user’s home directory is on an OES 2 Linux SP1 device and Store User Profile in User’s Home Directory is selected to enable the storage of the roaming profiles, the roaming profiles of the user are not stored in the user’s home directory when the user logs out of the Windows XP managed device.

Workaround: Apply the latest OES 2 Linux SP1 patch on the device that has the user’s home directory.

7.5.2 The roaming profiles of a user logging out of a Windows 2000 managed device might not be stored in the user’s home directory on an OES 2 Linux SP1 device

If the user’s home directory is on an OES 2 Linux SP1 device and Store User Profile in User’s Home Directory is selected to enable the storage of the roaming profiles, the roaming profiles of the user might not be stored in the user’s home directory when the user logs out of the Windows 2000 managed device for the first time.

Workaround: The user must log in to the managed device again and then log out of the device.

7.6 General Issues

This section contains information about the general issues:

7.6.1 An eDirectory user is prompted to enter the user credentials twice to log in to the managed device

An eDirectory user whose password has expired is prompted to enter his credentials twice to log in to the managed device that has both Novell Secure Login and the ZDM agent installed if the user chooses to change the password when prompted by ZENworks.

Workaround: Do one of the following:

  • Do not change the password when prompted to change by ZENworks.

  • Perform the following steps to prevent ZENworks from prompting you to change the password:

    1. Open the Registry Editor.

    2. Go to HKLM\Software\Novell\LgnXTier.

    3. Create a DWORD called DisablePasswordChangeDlg, and set the value to a non-zero integer.

8.0 Documentation Conventions

In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.

A trademark symbol (® , TM, etc.) denotes a Novell trademark; an asterisk (*) denotes a third-party trademark