The information in this Readme file pertains to Novell® ZENworks® for Desktops (ZfD) 4 Support Pack (SP) 1b.
This Support Pack contains updates for all components contained in the ZENworks for Desktops product only. If the Support Pack file was downloaded, it must be extracted at the root of the drive because it contains directory paths that could exceed the DOS limits.
The purpose of this Support Pack is to provide a bundle of fixes that have all been tested together. These files have undergone component testing, core OS testing, and integration testing with other Novell products.
Do not install individual files from the Support Pack.
Install the NetWare® Support Pack before installing other Novell product support packs like GroupWise® and ZENworks for Servers. These Support Packs are included with the Consolidated Support Pack, or they can be downloaded individually from the Consolidated Support Pack Web site.
For information on the latest Support Pack issues, see TID 10077724 at the Support Connection Web site .
To order the Support Pack CD, go to the Consolidated Support Pack Web site .
For information on the issues corrected in the Support Pack since the original version of ZfD 4 was released, see TID 10077083.
This document was updated in the following sections on the dates indicated.
The section entitled "DBExport Fails to Run on Windows NT/2000 Servers If Other JREs are Installed" was added to Workstation Inventory issues.
The section entitled 6.9 Windows 98 Computer Standby Feature Disabled was added to the Application Management issues.
The section entitled 9.3 DBExport Fails to Run in An Isolated Mode on a Windows NT/2000 Server was added to the Workstation Inventory issues.
The section entitled "DBExport Fails to Run on Windows NT/2000 Servers If Other JREs are Installed" was deleted from the Workstation Inventory issues.
The ZfD Remote Management component does not work properly when imported workstations have more than one network interface card. For more information, see TID 10019161 in the Novell Support Knowledgebase.
Beginning with ZfD 4, some previously supported Windows desktop policies were discontinued. In addition, in ZfD 4 SP1b, some Group Policy settings cannot be applied to Windows XP desktops. This section explains the details of these policy limitations.
The following policies are not a part of the ZENworks for Desktops 4 SP1b installation.
Customers who are upgrading from 3.x versions of ZfD will be able to retain the functionality of these policies. Retaining the functionality requires the continuing use of the previously-used directory tree. ZfD 3.x snap-ins will also be required to administer the legacy policies.
Although they can be configured locally, certain security settings cannot be extended to a Windows XP Group Policy on the network because Microsoft* doesn't publish any method to modify them. The following security settings cannot be modified and will not work in a Windows XP Group Policy pushed to the network:
This section explains the installation issues for the ZfD Server, the ZfD Middle Tier Server, and the ZfD Management Agent. It also discusses some installation issues for ZfD components such as Application Management and Workstation Imaging.
The ZfD 4 SP1b installation program requires free space on the designated system drive of the workstation from which you are installing. If the installation program fails, it might be because there is not sufficient free space to continue.
You must create sufficient space in order to continue with the installation. If your Windows drive is almost full, you can set the SystemDrive environment variable to use disk space on another drive.
The ZfD Server installation program reads its autoexec.ncf file to find and use the first listed BIND IP Address statement. If the file has two or more BIND IP Address statements and if the first address is incorrect or inactive, the installation will fail.
To correct the problem, make sure that the correct IP address is listed first in the autoexec.ncf file.
If you are trying to install ZfD Server software to a Windows 2000 server, you might not be able to add it as a targeted server in the Add Servers dialog box, particularly if Novell eDirectoryTM is installed on the Windows 2000 server and you are authenticated to eDirectory. You must also be authenticated through Windows in order for the file transfer to occur during the installation.
Use the following steps to authenticate to the target server:
From the Windows Explorer, click Tools > Map Network Drive to open the Map Network Drive Wizard.
Click the active link on the Connect Using a Different User Name string to open the Connect As dialog box.
Enter the computer name of the target server, followed by a backslash (\) and the administrator name. For example:
zenserver\administrator
Enter the password for the target server to return to the Map Network Drive Wizard.
In the Folder field, type or browse to the shared folder name followed by a backslash (\) and C$. For example:
\\zenserver\C$
In the Drive field, select the drive letter you want to map to this folder > click Finish.
If you use a Windows 2000 server with ConsoleOne® installed to install ConsoleOne to another server, Windows adds the new installation path to ConsoleOne to its registry, which also includes the default location of the previously installed ConsoleOne.
If you use this same Windows 2000 server to install ConsoleOne snap-ins to another server, the installation will fail because it uses the default path for installation.
If you cannot install the snap-ins from another server, we recommend that you delete the default value from the following registry entry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App_Paths\ConsoleOne.exe
This section contains information about the issues that might occur when you install the ZfD Middle Tier Server software.
If you install NetWare 6 SP1 on a server that already has ZfD Middle Tier Server installed, the ZfD Middle Tier Server will stop working. If this happens, you need to reinstall the ZfD Middle Tier Server software.
If you install the ZfD Middle Tier Server software on a Windows 2000 server, you must restart that server twice to load the newly installed software.
If you upgrade a shipping version of ZfD 4 Middle Tier Server running on NetWare 5.1 SP5 with ZfD 4 SP1b Middle Tier Server, the Middle Tier Server components will not work.
If you install the Novell Client on a Windows 2000 server, then install the ZfD Middle Tier Server on the same machine, then uninstall the Novell Client from this server, the ZfD Middle Tier Server will fail.
This section contains information about the issues that might occur when you install the ZfD Management Agent software.
IMPORTANT: The version of the ZfD Management Agent that shipped with ZfD 4 (setup.exe) is no longer supported. Current ZfD 4 users should replace the older version of the agent with the version of the agent shipping with ZfD 4 SP1b or ZfD 4.0.1 (zfdagent.msi). ZfD 4 SP1b is included as part of Consolidated Support Pack (CSP) 9, and can be downloaded individually from the CSP download Web site. The updated ZfD Agent MSI (ZfD 4 SP1b/4.0.1) can also be downloaded from the Novell Product Downloads Web site.
If you have downloaded and installed interim patches for the ZfD 4 Management Agent, refer to the ZfD 4 Upgrade guide at the ZfD 4 documentation Web site for information about upgrading from your current ZfD Management Agent to the ZfD 4 SP1b/4.0.1 Management Agent.
The Microsoft Windows Installer engine (msi.dll) must be present on the workstation in order for the ZfD Agent MSI package to be unpacked and executed. Some Windows 98 and Windows NT workstations might not have the MSI engine installed, so the ZfD Agent MSI package will not install.
You can obtain the latest version of the Windows Installer from the Microsoft downloads site or you can use the MSI 2.0 file that is available in the \windows installer folder of the ZENworks for Desktops Companion CD.
When the ZfD Management Agent MSI package is distributed and installed, it uninstalls the existing installation of the ZfD 4 Management Agent (that is, the last shipping version, setup.exe) on Windows workstations.
If you distribute the ZfD Management Agent MSI through Application Launcher to a Windows workstations, users should not have ConsoleOne open on those workstations.
If ConsoleOne is open during the distribution, the ZfD Agent Installation MSI will fail.
If you configure the ZfD Management Agent MSI object to allow a user-based uninstall, the workstation does not currently prompt for a reboot when the user executes an uninstall by right-clicking the Application object icon.
If you grant Administrator rights to the user, he or she can uninstall the ZfD Management Agent using Add/Remove Programs. In this case, the workstation does display a prompt for reboot.
Because the uninstall might have had an effect on the Windows registry, other applications reading the registry at startup might be adversely affected unless the workstation is rebooted. Users should always reboot their workstations manually after uninstalling the ZfD Management Agent by right-clicking the application icon.
If you previously installed some ZfD features with the ZfD Management Agent installation, and you subsequently try to manually uninstall those features by using the Modify Features dialog box, you will receive the following error message:
A feature must be selected in order to proceed with the install.
The uninstall of the feature will not be successful.
You must use an Application object with the Novell Application LauncherTM to uninstall previously installed features.
If you have installed ZfD 4 SP1 Remote Management with Mirror Driver option selected, do not install ZfD 4 SP1b Remote Management directly over it.
To install ZfD 4 SP1b Remote Management, do the following:
Uninstall the ZfD 4 SP1 Management Agent.
Reboot the workstation.
Install the ZfD 4 SP1b Management Agent.
If you install the ZfD 4 SP1b Remote Management component over the ZfD 4 SP1 Remote Management component, the Found New Hardware Wizard dialog box prompts you to install Novell ZENworks Remote Management Driver. If this happens, click Next. In the Hardware Installation or Digital Signature Not Found dialog box, click Continue Anyway.
If you have installed ZfD 4 SP1 Management Agent, do not install the ZfD 4 SP1b Management Agent directly over it.
To install the ZfD 4 SP1b Management Agent, do the following:
Uninstall the ZfD 4 SP1 Management Agent.
Reboot the workstation.
Install the ZfD 4 SP1b Management Agent.
If you install the ZfD 4 SP1b Management Agent over the ZfD 4 SP1 Management Agent, the following error messages are displayed on reboot:
Cannot load dynamic link library for path\wmnetp.dll
Cannot find ZENautil.dll
Click OK on the error messages, then log in and install the SP1b ZfD Management Agent using a manual installation. This will add the missing files.
This section contains information about the issues that might occur when you install the Application Management component of ZfD 4 SP1b.
If you want to use the Application Browser view of the Novell Application Launcher, some additional configuration is necessary if you have installed ZfD Middle Tier Server software to a NetWare 5.1 server where apache\htdocs is the default directory of the Apache files.
You need to manually copy two files, myapps.html and zfdwebsw.exe, from the apache\nwdocs directory to a public directory (the default is apache\htdocs) on this server.
This section contains information about the issues that might occur when you install the Workstation Imaging component of ZfD 4 SP1b.
If you reinstall or upgrade the Workstation Imaging component of the ZENworks Server installation, the following lines will be added to the zfdlog.txt log file:
Imaging\NTa Components NOT successfully installed on <server_name> at <installation_path>
Imaging\NTb Components NOT successfully installed on <server_name> at <installation_path>
The installation log file (zenworks_for_desktops_server_installlog.log) indicates that the zenimgdsr.dll file was not successfully copied. This condition exists because the original .dll file remains open on the server during the installation. Both the ZfD 4 and the ZfD 4 SP1b versions of the .dll are the same, so the failure to install is inconsequential.
If you want to avoid the error, you can rename zenimgdsr.dll on the server and then run the installation program.
This section explains the issues that might occur when users try to authenticate to the ZfD Server using either the Novell Client or the ZfD Management Agent for login.
If you try to authenticate through the ZfD Middle Tier Server to a ZfD Server installed on a Windows 2000 machine that already has Active Directory* (installed because the ZfD Server acts as the Primary Domain Controller) and eDirectory (installed to accommodate ZfD) both installed, the authentication will fail unless the user logs on with a full context.
The reason for this failure is a contention for the default LDAP port between the Active Directory and eDirectory LDAP listeners. To work around this port conflict, during the install of eDirectory either choose an LDAP port other than the default of 389 or modify the LDAP Group object found in the server's container in ConsoleOne, then use the nsadmin utility in the ZfD Middle Tier Server to configure the ZfD Middle Tier Server to communicate over that port.
To configure the port in NSADMIN:
In the Address box of Internet Explorer, type the URL for the NSADMIn utility. For example:
http://IP_address/oneNet/nsadmin
In the Value field of the LDAP Port configuration parameter, specify the LDAP port number you already set in eDirectory, which the ZfD Middle Tier Server should use to communicate with the ZfD Server > click Submit.
If you try to manually unload the Middle Tier Server Handlers (for example, xzen.nlm) running on NetWare 5.1 or NetWare 6, the server will abend.
On NetWare 6, you should use NVXADMDN to unload Apache and Middle Tier handlers. Use NVXADMUP to restart Apache and Middle Tier handlers.
On NetWare 5.1, enter the following command:
unload apache
Using ndscons.exe on Windows 2000 to verify the connection between the ZfD Middle Tier Server and the ZfD Server will not work unless you have Administrator rights for the local Windows 2000 user.
If users log in to a local workstation with a User ID that does not match the user ID in eDirectory, the distribution of MSI applications to the workstation (including the Agent MSI program) will fail.
For user a workstation to receive an MSI application distribution, the user's local User ID and eDirectory User ID must match.
If many (that is, hundreds of) users attempt to log in to the network at the same time through a ZfD Middle Tier Server on NetWare 6, NetWare 6 SP1b, or NetWare 6 SP2, the server might hang because of high utilization problems. To fix this problem, download and install the patch for Novell Storage ServicesTM (NSS) available from Novell Support at http://support.novell.com. Search for TID 10072765.
The issue is resolved with NetWare 6 SP3, which includes the fix mentioned above.
A workstation with the ZfD Management Agent installed and running in Passive mode without the Novell Client presents the following option in a drop-down box when you click Change Password from a Windows Security dialog box (Ctrl+Alt+Delete):
<Novell Netidentity Credentials Provider>
This option for changing the eDirectory password from Netidentity is currently non-functional. To change the password for the Agent running in Passive mode, open the Control Panel, click Network Identity, and change the password in the appropriate dialog box.
This section identifies some areas of the ZfD Workstation Management component that might not work properly or that might require further configuration in ZfD 4 SP1b.
If the Novell Client and the ZfD Management Agent are installed on a workstation (for example, a laptop workstation) and that workstation is taken outside of the corporate firewall, only the traditional Novell Client login will be displayed at login, and the user will only be able to log in locally by choosing Workstation Only.
In this scenario, ZfD Workstation Management will not work (that is, no ZfD policies will be applied and Workstation Manager will not work), but ZfD Application Management will work (that is, applications will be available from any view of the Novell Application Launcher). If users log in locally they will see only the installed applications that are marked "disconnectable" or applications that were force-cached when they were connected.
If the ZfD Management Agent and the Novell Client are both installed and the agent is configured with a Middle Tier Server address, users can log in to the Middle Tier through the Application Launcher after logging in only to the workstation with the Client. In this case, the Application Launcher works normally, except it accesses eDirectory and the file system through the Middle Tier Server instead of the Novell Client.
If you have only the ZfD Management Agent installed on a workstation outside the firewall, ZfD Policies and the Workstation Manager will work.
This section discusses some aspects of Windows Group policy administration that might not work properly or that might require further configuration in ZfD 4 SP1b.
Some Group Policy settings might not appear on Windows desktops because ZENworks, by default, signals Windows to refresh Group Policies asynchronously. The most noticeable effect of this behavior occurs when policies remove items from the desktop. If those items aren't processed early in the login process, the settings will not work.
ZENworks can be configured to refresh Group Policies synchronously to address this issue.
To enable synchronous processing of Group Policies at each Windows workstation, create a new DWORD value named "Apply Policies Synchronously" with a value of 1 in the registry in the following location:
HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Workstation Manager\Group Policies
This setting will cause ZENworks to wait for Windows to process the Group Policies before pushing them to the desktop.
If you apply a workstation group policy created for Windows XP that is configured with security settings and you also apply a user group policy created for Windows XP that is configured with security settings (for example, you want to define a user certificate), the security settings applied with the user group policy will overwrite the security settings applied by the workstation group policy.
If you disable the security settings in the user policies, the security settings configured in the workstation policy are set and activated.
If you launch the Microsoft Management Console (MMC) from ConsoleOne to edit a Windows Group Policy---specifically to rename a default user account (Administrator or Guest), you must not be logged in as the user whose default account name you are changing. If you log in using this default account and rename the account, the changes will not be saved to the network path you designate in ConsoleOne and might remain on the administration machine.
After ZfD 4 SP1b installation, iPrint printers are not distributed to users running Windows 2000/XP workstations, even after the ZfD 4 SP1b iPrint policy is configured in the User Policy package (which installs the iPrint Client and pushes printer drivers to the users) and their workstations are rebooted.
To work around this problem, modify the AllowUserPrinters value in the iprint.ini file in the \\server_name\sys\login\ippdocs directory from zero (0)---the default value---to one (1), which will allow the user to add the printer.
NOTE: The iprint.ini file is available only if you have installed Novell Distributed Print ServiceTM as part of a NetWare installation and if you have extracted the nipp.exe to that directory. If you do not have iprint.ini and nipp.exe, you can download them from Novell Support at http://support.novell.com. Search for TID 10080443.
If you use the ZfD 4 iPrint Policy to install the iPrint Client on a network workstation and then reboot, non-Administrator users are prompted with a dialog asking for Administrator credentials. The system asks for a reboot because a value is placed in the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce key in the Windows registry by InstallShield (the installation program used by the iPrint Client).
This value initializes the cleanup routine for the InstallShield installation and requires Administrative privileges to execute. Until either the prompt is satisfied with Administrative credentials or this value is removed from the RunOnce key, the non-Administrative user will continue to be prompted for Administrator credentials at login to the local workstation.
This section identifies some areas of the ZfD Application Management component that might not work properly or that might require further configuration in ZfD 4 SP1b.
Although nal.exe and nalexpld.exe are included the product and still launch executables, their purpose is to facilitate the continued functioning of existing login scripts.
The ZENworks for Desktops 4 release only supports switches that are supported by nalwin32.exe. To see a list of these switches, enter the following command:
nalwin32.exe /?
These switches are fully documented in the Application Management section of the ZfD Administration guide available at the ZENworks for Desktops documentation Web site.
Running nal.exe from the server returns the following error:
The ordinal 6625 could not be located in the dynamic link library MFC42.DLL
This error occurs because an older version of mfc42.dll is already installed on the server in sys:\public. To work around the problem, you need to copy a newer version of mfc42.dll to this location. You can find a newer version in the \supplemental folder of the ZENworks for Desktops Companion CD.
The new Terminal Server system requirement on an Application object applies only to remote Terminal Server sessions. Sessions running at the Terminal Server console are considered to be remote sessions by default. This behavior can be changed by creating the following registry key on the Terminal Server itself:
HKEY_LOCAL_MACHINE\Software\Netware\Nal\ConsoleIsNotTS
Creating this registry key will cause sessions running on the Terminal Server console to be treated as non-Terminal Server sessions.
If you enable personal folders when you configure the Novell Application Launcher snap-in for ConsoleOne, users with the Windows XP, Windows 2000, or Windows 98SE operating systems who rename folders in Application Explorer view will notice that the act of renaming a personal folder actually creates a new folder instead. The issue occurs only when the following steps are used:
Enable personal folders in ConsoleOne.
From a Windows 98SE/2000/XP workstation, open the Application Explorer view.
Right-click the personal folder > click Explore.
Create one or more new folders > rename a folder.
A new folder is created.
Users can work around this problem after it occurs by closing the Application Explorer view and then reopening it. The view will open without displaying a duplicate folder with the original name.
When a distributed application is configured to be uninstalled from a workstation, the workstation does not currently prompt for a reboot when the uninstall is complete.
Because the uninstall might have had an effect on the Windows registry, other applications reading the registry at startup may be adversely affected unless the workstation is rebooted. Users should always reboot manually after a distributed application is uninstalled.
Applications cannot be delivered through a network firewall if ZfD Server software and ZfD Middle Tier Server software are installed and running on a Windows 2000 server.
If the ZfD Server and the ZfD Middle Tier Server use Active Directory and Windows Domains, and if the ZfD Middle Tier Server is part of a domain, create a user and password in Active Directory to correspond exactly to the username and password in eDirectory. The Middle Tier Server and the ZfD Server must be members of the same Active Directory domain. Windows workgroups do not work.
A key component of Novell Licensing Services, nls32.dll, does not ship with the current Novell Client. As a result, an error will be generated when you try to use Software License Metering and Monitoring in ZfD.
You can find a newer version of nls32.dll in the \nal licensing folder of the ZENworks for Desktops Companion CD. Copy nls32.dll to the following location:
Windows NT/2000/XP Workstation: Copy to c:\winnt\system32
Windows 98 Workstation: Copy to c:\windows\system
If you associate an application to a Windows 98 workstation, configure it to Force Cache, distribute the application to the workstation, and then try to run the application when the workstation is disconnected from the network, the application icon will disappear from any launching point (that is, the desktop, system tray, or Start menu). The icon reappears when the workstation is reconnected to the network.
After you install the ZfD Management Agent to a Windows 98 workstation, the Computer Standby feature will no longer work. When you initiate standby, the Computer Standby dialog box appears. However, the dialog box never dismisses and Task Manager displays "Not Responding."
This section identifies some areas of the ZfD Workstation Imaging component that might not work properly or that might require further configuration in ZfD 4 SP1b.
Upgrading a Windows 2000 workstation hard disk from a Basic Disk System to a Dynamic Disk System changes the partition table so that it does not does not allow the workstation to boot to the production partition, only to the ZfD Linux* partition. No fixes for this issue are included in ZfD 4 SP1b.
If you choose to use dynamic disks on the workstation, you must create the image after the disks have been upgraded from basic to dynamic disks.
When booting multiple workstations from a Preboot Services environment to a server object configured for an imaging multicast session, some workstations might not recognize the multicast session unless the server contains a RW replica of eDirectory.
To correct the problem, add a RW replica to the server.
If you install the ZfD 4 SP1b Workstation Imaging component to a Windows 2000 server that has more than one network interface card (NIC), you do not have the option of binding the imaging proxy server to a specific IP address.
If you install ZfD 4 SP1b Workstation Imaging to a NetWare server, you can bind the imaging proxy server to a specific IP address (that is, the NIC of your choice) by using the following switch:
load imgserv -i:IP_Address
This section identifies some areas of the ZfD Remote Management component that might not work properly or that might require further configuration in ZfD 4 SP1b.
The display adapters listed below do not support the Screen Blanking feature of Remote Management. The managed workstation screen will not be blanked when these adapters are used.
IMPORTANT: Some of the following adapters may cause the managed workstation to hang or crash.
In addition, the Screen Blanking feature will not work on any display adapter that is not 100% VGA-compatible.
If the managed workstation has a full-screen DOS window open, you will not be able to remotely control it.
During a Remote Control or Remote View session, the active desktop wallpaper on the managed workstation might not be suppressed.
To improve the Remote Management performance, suppress the wallpaper before starting the Remote Control or Remote View session.
The animated and the colored cursors on the managed workstation are not supported for Remote Management.
Password-based authentication will fail if spaces are included in the password that is used to initiate a Remote Management session.
Only English characters are supported in the Remote Management password on non-English platforms. If extended characters are used while setting the password, Remote Management authentication will fail.
NOTE: The following information is applicable if you do not select the Mirror Driver, which is available as a Remote Management subfeature in the ZfD Management Agent installation program.
A Windows 2000/XP workstation with the NVIDIA graphics driver version 41.09 (or earlier) installed and with the Remote Management Agent also installed will crash with a General Protection Fault (blue screen) if a user changes the display settings or previews the screen saver or reboots the workstation after installing Remote Management.
Use the following steps to work around this problem.
From the NVIDIA Web site, download the NVIDIA graphics driver version 42 and install it on the affected Win 2000/XP workstation.
Reinstall the Remote Management Agent on the workstation.
For more information, see TID 10076769 in the Novell Support Knowledgebase.
This section identifies some areas of the ZfD Workstation Inventory component that might not work properly or that might require further configuration in ZfD 4 SP1b.
The ZfD 4 Inventory database cannot be mounted on a Sybase* Adaptive Server* Anywhere 8 database. Also, the Sybase engine shipping with ZfD 4 cannot coexist on a NetWare server where Sybase ASA 8 is running.
If the Novell Client is not installed on inventoried workstations, and if you use double-byte characters in the Inventory Service object's scan directory (scandir) path, the .str files will not be transferred to the Inventory server.
By default, the scandir path is the installation path where the Inventory server-side components and the database are installed (unless you manually changed it after the ZfD 4 installation by configuring the Inventory Service object).
When you install ZfD 4 SP1 Workstation Inventory on a Windows NT/2000 server, the installation program will automatically copy the JRE 1.3.1 to the server. DBExport might not work if you have installed other JREs separately.
If DBExport fails to run in an isolated mode on a Windows NT/2000 server, do the following:
Open Windows Registry and note the value of InvSrvPath from the HKEY_LOCAL_MACHINE\Software\Novell\ZENworks entry.
Open InvSrvPath\server\wminv\bin\dbexport.bat in a text editor.
Remove the -xbootclasspath flag and its value in the Java command line.
Append the following entry to <InvSrvPath>\server\wminv\bin\javadir.bat:
set path=%java_dir%\bin;%java_dir%\njclv2\bin;%path%
Run dbexport.bat.
At the server console prompt, type the following string:
DBEXPORT configuration_filename.EXP csv_filename.CSV
where configuration_filename.exp is an existing file that contains the data export settings and csv_filename.csv is the filename where the data exported from the database will be stored.
This section identifies some potential problems that might occur when you upgrade to ZfD 4 SP1b from earlier versions of ZENworks for Desktops.
In a typical upgrade situation, you will upgrade the ZfD Server to SP1b and begin using it before the ZfD 4 Agents on all of the workstations are upgraded.
Workstations that continue to use the older version of the ZfD 4 Management Agent might not be able to send Workstation Inventory scans to the server and cannot be remotely managed by ZfD 4 SP1b until they are rebooted.
This section identifies some things to look for when you use ZfD 4 SP1b in the same environment with other Novell products.
When installed to the same network location, ZENworks for Desktops 4 and ZENworks for Servers (ZfS) 3 give you the ability to manage and distribute software, files, and applications, to monitor the network's usage and health, and to enforce network policies, all from a central location.
For more detailed information on ZfD 4 and ZfS 3 SP1 Inventory interoperability, see Interoperability with ZENworks for Servers 3 in the Workstation Inventory section of the ZENworks for Desktops 4 Administration guide at http://www.novell.com/documentation/lg/zdpr/index.html.
Novell iChain® features such as SSO, Caching, Access Control, and Secure Exchange, are not currently supported with ZfD 4. ZfD 4 features will work through an iChain 2.0 tunnel.
The following sections provide the details of what will not work properly in ZfD 4 if ZfD 3.2 is also running.
If you have a network environment with a ZfD 4 Workstation Inventory Root Server and an Intermediate Server or Leaf Server that is ZfD 3.2, the inventory service on the Intermediate or Leaf Server will not start. In this scenario, the ZfD 3.2 inventory service displays the following error:
getID() out ->exception[Root exception is com.novell.service.jncp.NDSException: ccode = -669 (0xfffffd63)]com.novell.java.security.LoginException: Login failed.
If the ZfD 3.2 server is the Root Server and ZfD 4 is the Intermediate Server or Leaf Server, the inventory service on the Intermediate/Leaf Server will not start. The following error is displayed:
Error Type 15 Error 630
The problem can be resolved by applying a software patch to the ZfD 3.2 server. For more information, see the ZENworks for Desktops 4 Upgrade guide at http://www.novell.com/documentation/lg/zdpr/index.html.
If you load ConsoleOne from the ZfD 3.2 server, you cannot view the workstation inventory information if the workstation was inventoried into the ZfD 4 database. Users will get the error that the workstation inventory is not available in the database.
If you load ConsoleOne from the ZfD 4 Server, you will be able to see workstation inventory information of the workstation that is inventoried in either a ZfD 3.2 database or ZfD 4 database.
ZfD 4 Remote Control features will fail if the remote workstation has the ZfD 4 agents installed and if the Remote Management Console has ConsoleOne loaded with ZfD 3.2 ConsoleOne snap-ins.
ZfD 4 Remote Control features will work if the remote workstation has the ZfD 3.2 agents installed and if the Remote Management Console has ConsoleOne loaded with ZfD 4 ConsoleOne snap-ins.
ZfD 4 SP1b Workstation Inventory is interoperable with ZENworks for Servers 3 SP2.
This section identifies other issues that might cause problems or require work-arounds when you use ZfD 4 SP1b.
ZENworks for Desktops 4 SP1b does not support DNS-rooted trees or federated trees.
In the shipping version of ZENworks for Desktops 4, the property pages for User, Workstation, and Container objects in ConsoleOne included an Application Launcher and an Applications tab.
With ZfD 4 SP1b, these two pages are now consolidated under the ZENworks tab in the User, Workstation, and Container objects.
Workstation Import and Workstation Management (that is, policies pushed to workstations or users) do not work properly when users connect through a VPN.
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.
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside.
Copyright © 2003 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
US Patent Nos. 5,633,931; 5,692,129; 5,758,069; 5,761,499; 5,859,978; 5,893,118; 5,905,860; 6,023,586; 6,047,312; 6,061,743; 6,105,069; 6,115,549; 6,144,959; 6,173,289. Patents Pending.
ConsoleOne, Groupwise, DirXML, iChain, NDS, Novell, Novell Support Connection, NetWare, and ZENworks are registered trademarks of Novell, Inc. in the United States and other countries. eDirectory, NLM, Novell Application Launcher, Novell Client, Novell Distributed Print Service, and Novell Storage Services are trademarks of Novell, Inc.
All third-party products are the property of their respective owners.