If you are using Novell® ZENworks® 10 Asset Management in the standalone mode (without ZENworks 10 Configuration Management), see the Asset Management Readme at the ZENworks 10 Asset Management documentation Web site.
The issues included in this document were identified for Novell ZENworks 10 Configuration Management SP2.
For information about the new features or enhancements, see the Novell ZENworks 10 Configuration Management Upgrade Guide. The guide is available in the ZENworks 10 Configuration Management with SP2 (10.2) Guides.zip
For system requirements and installation instructions, see the Novell ZENworks 10 Configuration Management Installation Guide.
For administrative tasks, see the Novell ZENworks 10 Configuration Management SP2 documentation Web site.
This product contains undocumented utilities that Novell Support might use to diagnose or correct problems.
The following table contains information on the documentation content changes that were made in this Readme after the initial release of ZENworks 10 Configuration Management SP2 (10.2):
Table 1 Readme Updates
Readme Item Added or Updated
February 01, 2010
Newly added Section 3.5, AdminStudio.
December 15, 2009
The issues fixed in Update for ZENworks 10 Configuration Management SP2 (10.2.2) are identified with the phrase (Fixed in v10.2.2).
September 24, 2009
August 19, 2009
The issues fixed in Update for ZENworks 10 Configuration Management SP2 (10.2.1) are identified with the phrase (Fixed in v10.2.1).
July 7, 2009
June 26, 2009
In The Report Engine Server fails to initialize after installing ZENworks Reporting Server, added the workaround for Linux.
For a list of the resolved issues in ZENworks 10 Configuration Management SP2, see TID 7003225 in the Novell Support Knowledgebase.
This section contains information about ZENworks Configuration Management issues that might occur.
This section contains information about issues that might occur when you install ZENworks Configuration Management.
If your environment is running the Novell ZENworks Linux Management - Dell Edition and you created ZENworks partitions on your clients, when the partition is booted to update your clients to ZENworks 10 Configuration Management, the partition no longer works and the update fails.
Workaround: Before you install ZENworks 10 Configuration Management to your environment, create a scripted imaging task and force all ZENworks partitions to run it in preparation to update to Configuration Management.
Create the following script to fix the /etc/ZUpudate.sig file contained in the initrd resource file:
export PATH=/sbin:/usr/sbin:/bin:/usr/bin:/lbin mount $ZENDEVICE /mnt/harddisk cp /mnt/harddisk/boot/loader/initrd /initrd.gz #make a backup of initrd cp /mnt/harddisk/boot/loader/initrd /mnt/harddisk/boot/loader/initrd.sav gunzip /initrd.gz mount -o loop /initrd /mnt/cdrom cp /mnt/cdrom/etc/ZUpdate.sig / dos2unix /ZUpdate.sig cp /ZUpdate.sig /mnt/cdrom/etc umount /mnt/cdrom gzip -v9c /initrd > /mnt/harddisk/boot/loader/initrd umount /mnt/harddisk
If time is not synchronized on the network before you install the ZENworks services, you might see invalid certificate errors because the certificates have dates that are in the future, and therefore are considered invalid.
Workaround: Make sure that your network has its time synchronized before you install the ZENworks services. Make sure to include ZENworks back-end servers in the synchronization.
If you remotely connect to a managed device by using Remote Desktop Connection (RDP), then download and install ZENworks Adaptive Agent, the installation does not complete and the Remote Desktop Connection program stops working.
Workaround: To fix the issue, download the patch from the Microsoft* Support Web site and install it on the managed device.
ZENworks 10 Configuration Management SP2 is not supported on Windows* 7 Release Candidate. However, if your testing environment includes Windows 7 Release Candidate 32-bit or 64-bit, you can begin testing ZENworks 10 Configuration Management SP2 on those platforms.
During the command line installation of ZENworks 10 Configuration Management SP 2 on a Linux* server, if you choose to create a MS SQL Server* or an Oracle* database, and subsequently specify an existing database username, the installation fails at the end.
Workaround: Specify a new database username while creating the database.
This section contains information about accessibility issues when using ZENworks Configuration Management.
By default, Windows does not provide keyboard support for the toolbar.
Workaround: Enable the accessibility options in Windows and use the Accessibility Wizard to enable mouse key settings. Then, mouse functions are controlled by using the numeric keypad.
This section contains information about issues that might occur with Asset Inventory.
If an administrator configures an event-based or On Refresh schedule for an inventory scan and collection data form, the inventory agent fails to invoke the inventory scan and collection data form.
Workaround: Configure only a Recurring schedule for the inventory scan and collection data form.
Workaround: To troubleshoot the issue, see TID 7003350 in the Novell Support Knowledgebase.
If a device is reregistered from one Management Zone to another, the inventory data is not displayed for the device in ZENworks Control Center.
Workaround: Initiate an inventory scan twice on the device.
For more information on how to initiate an inventory scan, see
Scanning the Device in the Novell ZENworks 10 Configuration Management Adaptive Agent Guide.
This section contains information about issues that might occur with Asset Management.
You can migrate Oracle to Oracle databases. For migration purposes, these databases can be Oracle 9.2, Oracle 10.1, or Oracle 10.2.
If you are using an Oracle database, please observe the following:
The Oracle client must be installed on the machine that runs the migration utility. For versions 10.1 and 10.2, this must be Administrator, not InstantClient.
For the Oracle 10.2 client, you must apply patch 5473334 (Doc ID 387818.1). Of the several data access components included in the patch, Oracle Provider for OLEDB version 10.2.0.2.20 is required.
If you create and run a new report, the report does not display in the report list.
Workaround: Navigate out and then back to the page.
This section contains information about issues that might occur with the ZENworks Edition of AdminStudio* 9.5.
In the Bundle Creation page of the AdminStudio Distribution Wizard for ZENworks Configuration Management, if you select the Novell Support Knowledgebase.option, the existing bundles on the ZENworks server are not listed in the Bundles tree. Consequently, you cannot proceed with the Wizard. For more information, see TID 7005162 in the n the
This section contains information about issues that might occur when you use bundles in ZENworks Configuration Management.
Because Linux devices cannot have the ZENworks Adaptive Agent, you cannot assign bundles to be sent to them. However, in ZENworks Control Center, Directive bundles assigned to a Linux device might show as effective, which is incorrect.
If you set up an action to both back up the registry and edit the HKEY_CURRENT_USER registry entry on Windows Vista*, the action fails because all user-initiated processes in Vista run as the lowest privileged user.
Workaround: Use two different registry actions, one to back up the registry in the system context, and another to edit HKEY_CURRENT_USER in the user context.
When you create an Install Directory File bundle, the directory is installed even if its name contains spaces; however, it cannot currently be uninstalled by using the Undo Install Actions action.
Workaround: Avoid spaces in directory names if you want to enable the uninstallation of that directory.
If you launch a Launch Windows Thin Client Application action configured with the RDP Session on a 64-bit managed device, the action might fail.
Workaround: Apply the KB925876 patch.
If you use the 64-bit Internet Explorer* to launch ZENworks Control Center, then click the browse icon to browse to and select an icon from the icon resources such as an .exe, .dll, or .ico file, one of the icons from the resource file is selected by default. You cannot select any other icon.
Workaround: Use the 32-bit Internet Explorer to launch ZENworks Control Center.
This section contains information about issues that might occur with CASA in ZENworks Configuration Management.
CASA does not completely authenticate via the HTTP proxy during initial authentication, but instead contacts the Primary Server directly. After authentication, all CASA traffic goes through the HTTP proxy when using the ZENworks Adaptive Agent Logout/Login feature.
Workaround: The forward proxy server's firewall rules must allow access to ports 80, 443, and 2645. Additionally, HTTP forward proxy settings must be configured in two locations:
Device Management in ZENworks Configuration Management uses the WinInet HTTP protocol. Therefore, forward proxy settings must be configured in Internet Explorer: Click > > > > .
Device Management in ZENworks Configuration Management uses CASA authentication, which uses WinHTTP Services. WinHTTP requires proxycfg.exe. For example:
proxycfg -p forward_proxy_IP_address:8080
For more information on proxycfg.exe, see ProxyCfg.exe, a Proxy Configuration Tool.
This section contains information about issues that might occur when you use the Closest Server rules in ZENworks Configuration Management.
When you use this option, be sure to include at least one server in the Configuration section of the rule. Otherwise, after a managed device has been refreshed with this configuration, it cannot subsequently obtain new zone configuration data of any kind because it no longer knows of any servers to contact for this information.
After you create an L4 switch definition in the Default Closest Server Rules page, then add it to one or more custom Closest Server rules, any modifications that you make to the L4 switch definition (including definition deletions) are not propagated to any of the custom Closest Server rules.
This section contains information about issues that might occur when you use the Discovery and Deployment functions in ZENworks Configuration Management.
During the ZENworks Adaptive Agent installation, some ZENworks related files might be reported as malicious software by anti-virus software. Consequently, the installation abruptly stops. This is because the deployment packages (PreAgentPkg_Agent.exe and PreAgentPkg_AgentComplete.exe) contain another EXE file (ZENPreAgent.exe). If an EXE file is embedded in another EXE file, it is considered as malicious software because this is the behavior of a trojan.
Workaround: Do the following on the managed device where you want to install the ZENworks Adaptive Agent:
Manually add System_drive:\windows\novell\zenworks to the Exclusion list of the anti-virus software installed on the managed device.
Install the ZENworks Adaptive Agent.
The ZENworks Adaptive Agent runs on Microsoft .NET Framework. For better performance and stability, you should upgrade to the latest support packs and patches of .NET 2.0 through Windows Automatic Updates or Patch Management.
.NET 2.0 SP1 is the latest version supported by Microsoft on Windows 2000, and .NET 2.0 SP2 is the latest version of .NET 2.0 supported by Microsoft on Windows XP, Windows Server* 2003, Windows Server 2008, and Windows Vista.
On Windows XP and Windows Server 2003, you can directly download and install .NET 2.0 SP2 or upgrade to .NET 3.5 SP1, which includes .NET 2.0 SP2. On Windows Vista and Windows Server 2008, you must upgrade to .NET 3.5 SP1 to get the .NET 2.0 SP2 update installed.
This section contains information about issues that might occur when using Imaging in ZENworks Configuration Management.
Workaround: To assign the Imaging Satellite role or to promote a managed device to a Satellite with the Imaging server role, use the zman ssaimg command.
For more information on the zman commands, see the ZENworks 10 Configuration Management Command Line Utilities Reference.
Workaround: Disable the firewall on Windows 2000 and execute the zman ssaimg command.
You cannot take an image of the Linux device (Satellite or managed device) in the ZENworks Automated mode because the Linux device does not have the image-safe data.
Workaround: Take an image of the Linux device in the ZENworks Imaging Maintenance mode.
This section contains information about issues that might occur when logging in to various locations in ZENworks Configuration Management.
A Microsoft security fix (see Microsoft Knowledge Base article 312461) disallows certain characters in DNS names by not returning cookies when those characters are used in the server’s name. Without cookies being returned, state information cannot be preserved across HTML requests, so the user cannot log in to ZENworks Control Center.
The only characters allowed for DNS names in Windows are the alphabetical characters (a‑z), numbers, and the hyphen. For example, you cannot use an underscore character. Use a hyphen instead.
This is not an issue with the Mozilla* Firefox* browser, even when it is run on Windows.
Reference the IP address instead of its DNS name.
Reference a valid DNS name for the IP address the server is using. For example, your server name might be A_Server.mycompany.com, but the DNS registration for the IP address might be Aserver.mycompany.com, which will work.
If you only use Internet Explorer to run ZENworks Control Center, do not use underscores in your server names.
After an image containing the ZENworks Adaptive Agent has been restored on a Windows Vista device, nothing is displayed to indicate what is happening. After awhile, the device suddenly reboots.
This section contains information about issues that might occur during migration to ZENworks Configuration Management.
Add-on images that are created by exporting applications in traditional ZENworks are not valid in ZENworks Configuration Management. If these add-on images are migrated in combination with a base image or otherwise, they should be deleted.
Workaround: Manually delete the add-on image from ZENworks Configuration Management.
Migration of AOT or AXT applications to MSI applications is comparatively slower on a Windows Vista device.
This section contains information about issues that might occur when you use NAT with ZENworks Configuration Management.
In both a public and private network where static NAT is configured between the networks, policies and bundles might not be pushed down to the devices you are managing.
Workaround: On the DNS server to which the ZENworks server is registered, map the DNS name of the ZENworks server to the public IP address.
This section contains information about issues that might occur when you use Patch Management in ZENworks Configuration Management.
(Fixed in v10.2.2) When updating to ZENworks 10.2, your current patch configuration settings are reset to default values. This is because Patch Management has been enhanced with new capabilities, including the ability to use Satellites.
After updating to version 10.2, log in to ZENworks Control Center and access> to reconfigure Patch Management. You may want to change the server you are currently using for patch downloads and instead use a Satellite in order to take advantage of the new Satellite capabilities within the 10.2 version of the product.
Remember to re-enter any proxy settings or additional language selections that you might have been using in the 10.1 version of the product.
Workaround: None. Working as designed.
(Fixed in v10.2.2) In earlier releases of ZENworks Patch Management, a patch showed its status as Patched or Not Patched, regardless of whether the patch was new or outdated. This often caused many more patches to show as Not Patched than were actually necessary for deployment to a given target device.
This issue has been addressed in many of the new advanced content patches provided with the ZENworks 10 Configuration Management SP2:
When a patch is superseded, it is automatically disabled and marked Disabled (Superseded).
If the patch is re-enabled and detected, in most cases the patch shows as Not Applicable because it has been replaced by a more recent patch
Although this is inconsistent with the behavior of earlier versions of ZENworks Patch Management, this change is for the better because only the patches that currently need to be installed are reported or analyzed on each device.
Workaround: None necessary.
(Fixed in v10.2.1) The first time Patch Management is configured and the patch subscription is downloaded within a new Management Zone, Discover Applicable Updates (DAU) bundles might not be distributed to all satellites even if the option to cache patches on Satellites is selected. The Satellite is listed, but the column reflects that it is not included.
Workaround: If you experience this issue, clickto download the subscription a second time and include DAU bundles on Satellites.
You must allow sufficient time for the patch subscription process to complete for new DAU bundles to be created, and for content replication to occur to your Satellites. This might take a few minutes or longer, depending on your network topology.
(Fixed in v10.2.2) Deployment of certain .NET patches might require that the latest Windows Installer be installed. Otherwise, you can receive errors when deploying those patches.
Workaround: Prior to deploying .NET patches, verify whether a Windows Installer version is a prerequisite. If necessary, create a bundle to deploy the latest Windows Installer (version 3.1 or later) to your systems. Windows Installers are available from Microsoft.
(Fixed in v10.2.1) After you send a patch to a managed device, if you disable or delete the Patch Management Assignment bundle that was created to deploy the patch, the patch is automatically uninstalled when the managed device is refreshed.
It is expected that the patch should remain installed on the managed device until the requirement is met for unassigned bundles to uninstall after x number of days.
Workaround: Until this issue has been fixed in a future update of the product, you can do the following:
In ZENworks Control Center, click> > > > .
This keeps unassigned bundles from being automatically uninstalled.
(Fixed in v10.2.1) When the ZENworks Configuration Management client is version 10.0.3 and the Primary Servers are version 10.2, unwanted CAB files may be written to C:\ and not removed in subsequent patch operations.
Workaround: If you have 10.0.3 agents installed in your network, you must upgrade them to at least 10.1.3 before migrating the ZENworks Management Zone to version 10.2.
(Fixed in v10.2.2) After you have configured Patch Management, a message that reminds to you configure the product still displays every time that you click the tab.
This condition might exist if you enabled the subscription service via the Patch Management role administrator. This is an issue with the Zone Settings right not being available when trying to configure Patch Management.
Workaround: Always configure Patch Management settings by using the default ZENworks administrator login.
(Fixed in v10.2.1) If new patches fail to appear within Patch Management, click > > > > and determine how long the last daily subscription download took to complete. If this value is over 12 hours, the subscription download thread might not be running.
Workaround: Reboot the ZENworks Primary Server where the patch subscription is being downloaded.
This section contains information about issues that might occur when you use policies in ZENworks Configuration Management.
On 64-bit versions of Windows Server 2003, only the Browser Bookmarks policy, SNMP policy, Printer policy, Local File Rights policy, and the Windows Group policy device-related settings are applied if they are associated to the device.
The Browser Bookmarks policy settings are not removed from the user’s Favorites when the ZENworks Adaptive Agent is uninstalled.
If both user-associated and device-associated policies are effective for a device, only the policy that takes precedence according to the Policy Conflict Resolution settings is applied. However, the Effective status for both policies is displayed as Success in the ZENworks Adaptive Agent icon.
Subsequent to the first login, the DLU user is prompted to provide the credentials when he or she tries to log into the device again during the cache period specified in the policy if theand settings are configured in the Dynamic Local User policy.
Workaround: To enable the user to log into the device without being prompted on subsequent logins, ensure that theoption is enabled in the policy. This ensures that the ZENworks Agent manages the password on behalf of the user.
In the Local File Rights policy, if theaccess right is denied for the Administrators or Authenticated Users group and the option is selected, the policy fails. However, if the access right is denied for the Administrators or Authenticated Users group, the policy is successful only during the first enforcement.
The unenforcement of the Local File Rights policy from a device fails if the Full Control access right is denied for the Administrators or Authenticated Users group in the policy.
Because of the security settings in Microsoft Vista, administrators must manually add the appropriate security rights to the user registry hive to enable roaming profiles. For more information, see the Microsoft TechNet Web site.
Uninstall does not roll back the previously enforced Printer policies.
Workaround: Disassociate the Printer policy from the users or devices to unenforce the policy. After unenforcing the policy, uninstall ZENworks.
The iPrint nipp.exe client installer does not support a silent installation.
Workaround: Use iPrint nipp-s.exe or nipp.zip for a silent installation.
The printer policy does not support using a .exe file to install printer drivers.
Workaround: Use the .zip format of the installation file to install the printer drivers.
The iPrint client is not supported on 64-bit versions of Windows Server 2003.
Support for network printer prompting for user credentials is not provided
The Windows Group policy containing the local group policy settings is not applied if the operating system of the device where the policy is applied is different from the device where the policy is created.
Workaround: Remove the System Requirement from the Windows Group policy and apply the policy. However, the security settings are applied only if the operating system version of the device where the policy is applied is later than the operating system version of the device where the policy is created.
Software restrictions in security settings are not enforced if theoption is selected.
Workaround: In thetab, select to enforce the software restrictions.
Environment variables for the user are not supported in the Group policy login scripts.
The Group policy login scripts do not support the environment variables for users on Vista, Win2k3, and Win2k8 devices.
User settings fail to unenforce on Windows Server 2008 device.
On a Windows Server 2008 device, the Group policy user settings associated to a user are not unenforced when the user logs out.
This section contains information about issues that might occur when you use Personality Migration in ZENworks Configuration Management.
While saving the settings and data to a .pnp file, if you choose to use the to span the content to multiple files, you must specify a password in the option.
Workaround: Before migrating the printer settings from the source device to the destination device, do the following:
Create a directory named PrinterDrivers in any of the logical drives such as C:, D:, or E:.
Download and copy the unzipped driver to the PrinterDrivers directory.
When you create bundles by using the Store Personality or Apply Personality actions, the bundles always run as a dynamic administrator. The dynamic administrator does not have the Read or Write access to the authenticated network shares, and therefore cannot store or apply a PNP file from authenticated network shares.
Workaround: To store and apply personalities, the user groupshould have Write and Read access to the shared location when you create bundles by using the Store Personality and Apply Personality actions.
This section contains information about issues that might occur with registration in ZENworks Configuration Management.
If you enter zac unr /?, the help shows an example using the -f switch, but doesn’t explain its purpose.
The -f switch forces a device to unregister if the zac unregister command alone does not unregister the device.
This section contains information about issues that might occur when you use the Remote Management feature in ZENworks Configuration Management.
On Windows Vista managed devices, mouse and keyboard locks do not function if the Aero theme is enabled.
Workaround: Do not use the Aero theme.
The Remote Management viewer installation might fail. This error is inherent to the MSI framework.
Workaround: Perform either of the following steps:
Uninstall the Remote Management viewer by using Add/Remove Programs, then reinstall it.
Use the Microsoft Windows Installer Cleanup Utility to clean up the application, then reinstall it. This utility can be downloaded from Microsoft Support.
On Windows Vista devices, the Remote Management viewer fails even though the security prompt is successfully completed.
Workaround: Add the server running ZENworks Control Center to the list of trusted sites and retry.
Workaround: Click theicon in the Remote Management viewer, then press the Esc key to exit the Secure Attention Sequence (SAS) window. Then, click the icon again in the Remote Management viewer.
If the device is powered off by using a hard shutdown, you cannot use Wake-on-LAN to wake up the device.
If you remotely control or remotely view a device on which an RDP session was performed, you might see a black screen rather than the desktop of the device.
Workaround: To view the desktop of the device:
Manually unlock the desktop.
Reinitiate an RDP session on the console session of the device by running the following command:
The ZENworks Reporting solution is based on BusinessObjects Enterprise* XI. This section contains issues that might occur when you use ZENworks Reporting. To troubleshoot other error messages that you might encounter while working with BusinessObjects* Enterprise XI, see the BusinessObjects XI 3.1 documentation Web site.
The ZENworks Reporting solution has the following limitation:
The reporting universes in this release are enhanced to improve the user experience in Custom Reporting. The custom reports created in the previous releases of ZENworks Configuration Management are not transferable to this release of Reporting Server. The reports must be re-created in this release of the Reporting Server.
The following error might be displayed while running the reports:
A database error occurred. The database error text is: [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user "NT AUTHORITY\ANONYMOUS LOGON"..(WIS 10901)
Workaround: Do the following:
Edit the properties of ZENworks Reporting Server Services on the ZENworks Server:
From the desktopmenu, click > > > .
The Central Configuration Manager window is displayed.
Right-click, then click .
Right-click, then click .
The Server Intelligence Agent (ZENReporting) Properties window is displayed.
In the Log On As panel, deselect, then specify the username and password of the domain account of the Windows server that hosts the ZENworks Reporting Server database. For a non-domain user, the username and password must be the same on the MS SQL server database and ZENworks Reporting Server.
Right-click, then click
Workaround: On the Windows server where ZENworks Control Center is launched, add the appropriate DNS entry in the %Windows_root%\systems32\drivers\etc\hosts file.
Workaround: On the Windows device where ZENworks Control Center is launched, add the appropriate DNS entry in the %Windows_root%\systems32\drivers\etc\hosts file.
The following message is logged into the %ZENWORKS_HOME%\logs\zrsuninstall.log file:
Workaround: Do the following:
Open the Windows Task Manager and stop all instances of msiexec.exe and setup.exe.
Uninstall ZENworks Reporting Server.
Modifying the report layouts of the predefined reports is not recommended.
(Fixed in v10.2.1) ZENworks Reporting fails when you log in to the ZENworks Control Center by using an administrator account (such as Administrator@windowdomain.com) that was created by using the user source.
Workaround: To log in to the ZENworks Control Center with the administrator account that was created by using the user source, use only the username, such as Administrator.
You might encounter the following error message when the ZENworks Reporting Server InfoView session expires:
Unable to reconnect to the CMS <server-name>:6400. The session has been logged off or has expired. (FWM 01002)
Workaround: Do the following:
Delete the cookies from your browser.
Close all browser instances.
Log in to ZENworks Control Center, then launch the ZENworks Reporting Server InfoView.
Workaround: Click( > ) two times to relaunch the ZENworks Reporting Server InfoView page.
All the cookies that were created in the prior session are deleted on the first click, and the ZENworks Reporting Server InfoView page is displayed on the subsequent click.
To end the ZENworks Reporting Server InfoView session, ensure that you clickon the ZENworks Reporting Server InfoView page.
This problem might occur if the Central Management Server failed to start. The following error message is displayed in the %zenworks_home%\logs\zcc.log file:
cause:com.crystaldecisions.enterprise.ocaframework.OCAFrameworkException$NotFoundInDirectory: Server <Server_name>:6400 not found or server may be down (FWM 01003) cause:java.net.ConnectException: Connection refused: connect detail:Server <Server_name>:6400 not found or server may be down (FWM 01003) Connection refused: connect detail:Server <Server_name>:6400 not found or server may be down (FWM 01003) Connection refused: connect
Workaround 1: See the Business Objects Board forum.
Workaround 2: Contact Novell Support.
The following error message is displayed when the Report Engine Server fails to initialize:
Cannot initialize Report Engine server. (Error: RWI 00226) (Error: INF)
This problem might occur if the Report Engine Server is not running, and you are trying to create or access the reports.
Workaround: Manually initialize the Report Engine Server before launching the ZENworks Reporting Server InfoView:
On Windows: Restart the Server Intelligence Agent:
From the desktopmenu, click > > > > to display the Central Configuration Manager window.
Wait 2 to 3 minutes for the services to restart.
On Linux: Restart the BusinessObjects Enterprise services:
Stop the BusinessObjects Enterprise services by running the following command as a root user:
Wait 2 to 3 minutes for all the services to stop.
Start the BusinessObjects Enterprise services by running the following command as a root user:
Wait 2 to 3 minutes for all the services to start.
This section contains information about issues that might occur with Satellite devices in ZENworks Configuration Management.
(Fixed in v10.2.1)A software bundle larger than 2147483647 bytes cannot be served from a Linux Satellite to a managed device because of the file size limitations of Jetty, which is used by Linux Satellites to serve bundles. This size limitation does not apply to Windows Satellites or to imaging bundles.
If system update content has been synced to a Satellite device, the content is not automatically removed with the rest of the content if the Content role is removed from the device.
Workaround: Manually delete the system-update directory on the device.
If you remove the Content role from a Satellite device, the device is not automatically removed from the Closest Server Default Rule and the Closest Server Rules.
Workaround: Remove the Satellite device from the Server Hierarchy list (in ZENworks Control Center, click thetab > select the check box next to the Satellite device, click > then click .)
Workaround: After unretiring the Linux Satellite from the Management Zone, restart the novell-zenworks-xplatzmd service.
(Fixed in v10.2.1)When you remove the Imaging role from a Linux Satellite, the content replication functionality is disabled only during the next device refresh schedule. Consequently, all imaging content (such as tftp content) scheduled for replication before the next device refresh schedule is replicated on the Linux Satellite.
Workaround: If you want to disable the content replication functionality immediately after removing the imaging role, you must manually refresh the Linux Satellite in one of the following ways:
In thetab of ZENworks Control Center, click , select the check box next to the Linux device you want to refresh, then click > .
On the Linux unmanaged device, open a terminal, change your current working directory to /opt/novell/zenworks/bin/, and execute ./zac ref.
This section contains information about issues that might occur with the ZENworks Adaptive Agent in ZENworks Configuration Management.
The ZENworks Adaptive Agent is installed on Linux Primary Servers to enable software updates. Although Linux servers appear as managed devices in ZENworks Control Center, any actions performed on them, such as assignments, QuickTasks, and so on, will fail.
ZENworks resources are loaded according to the locale of the process that retrieves them. When using regional settings, the ZENworks Windows service might be configured to use a different language than the user is configured to use. The result is that the strings from both languages are displayed.
Workaround: Do one of the following:
Install the native language operating system
Change the default user language to match the language displayed by the user
(Fixed in v10.2.2)Workaround: On the Windows Vista managed device, use the login GINA to log in as a ZENworks user.
If you deselect theAgent Feature in ZENworks Control Center (Agent Features panel on the ZENworks Agent page), the User Management feature is not uninstalled on a Windows 2000 device.
For more information on customizing the agent features, see Customizing the Agent Features.
If the User Management Agent Feature is disabled or uninstalled in ZENworks Control Center (Agent Features panel on the ZENworks Agent page), the status for the DLU policy on the ZENworks Adaptive Agent Policies page is displayed aseven though the policy is not effective on the device.
(Fixed in v10.2.1)If you choose to install only the Asset Management feature of ZENworks Adaptive Agent ( > > > > ) on a device that already has traditional ZENworks Agent installed, the Adaptive Agent installation uninstalls the traditional ZENworks Agent.
If you upgrade from ZENworks 10 Configuration Management 10.1 or ZENworks 10 Configuration Management 10.1.x to ZENworks 10 Configuration Management SP2 (10.2), the ZENworks icon might not be visible in the notification area of the device.
Workaround: Do one of the following:
Log out and log in to the device.
Reboot the device.
Terminate and restart the explorer.exe process through the Windows Task Manager.
This section contains information about issues that might occur when using ZENworks Control Center.
During installation, the setup checks to see if the default HTTP port (80) and HTTPS port (443) are in use. If the ports are in use by another application (such as IIS), you are prompted to use alternative ports. In this case, you must access ZENworks Control Center via the port it is using and not access IIS.
Workaround: Although http://Primary_Server_IP_address works if ZENworks Control Center is using port 80, http://Primary_Server_IP_address:### (where ### is the port Tomcat is using) always works.
When Microsoft SQL Server 2005 is installed on non-English (U.S.), there are differing sort orders and collations offered. This means that the ordering of lists in ZENworks Control Center is affected, including devices and so on.
Workaround: When you install an SQL Server, it selects a default based on the locale of the server. Review the Microsoft documentation to determine which collation option to use when installing your MS SQL Server.
This section contains information about issues that might occur when you use the zman command line utility.
Using the man zman command for Simplified Chinese and Traditional Chinese doesn’t display any help. It only displays the tilde (~) character.
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 (®, ™, 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.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2009 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.
Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed on the Novell Legal Patents Web page and one or more additional patents or pending patent applications in the U.S. and in other countries.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.