The information in this Readme pertains to Novell ZENworks 11, the product that provides a comprehensive management of Linux and Windows servers and workstations.
The following table contains information on the documentation content changes that were made in this Readme after the initial release of ZENworks 11.
Table 1 Readme Updates
|
Date |
Readme Item Added or Updated |
|---|---|
|
August 08, 2011 |
Added an update on localization for ZENworks 11 SP1 in Section 2.0, Localization Update for ZENworks 11 SP1. |
|
April 06, 2011 |
In Section 3.5, Installation Issues, added Section 3.5.7, Windows 7 SP1 or Windows Server 2008 R2 SP1 devices fail to register with the ZENworks 11 Primary Server. |
The ZENworks 11 SP1 product documentation has not been localized. For issues specific to ZENworks 11 SP1, see the ZENworks 11 SP1 Readme.
For all other ZENworks 11 SP1 documentation, see the Novell ZENworks 11 SP1 documentation Web site.
Before you start installing or upgrading to ZENworks 11, review the information in the following sections:
This product contains undocumented utilities that Novell Support might use to diagnose or correct problems.
For detailed information about the new features or enhancements in ZENworks 11, see the “What’s New” section in the Novell ZENworks 11 Upgrade Guide.
For detailed information on prerequisites and instructions for upgrading Primary Servers, Satellites, and managed devices to ZENworks 11, see the Novell ZENworks 11 Upgrade Guide.
This Readme lists the issues specific to ZENworks 11.
For all other ZENworks 11 documentation, see the Novell ZENworks 11 documentation Web site.
This section contains information about issues that might occur when you install ZENworks 11.
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 11 Configuration Management, the partition no longer works and the update fails.
Workaround: Before you install ZENworks 11 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.
During the command line installation of ZENworks 11 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.
The installer prompts for the first reboot after completing the installation of ZENworks Asset Management. The server prompts for a reboot again to remove any additional packages that might have been installed while installing ZENworks Asset Management.
Workaround: None
When installing the ZENworks Server or ZENworks Adaptive Agent on a virtual machine, the installation takes much more time than normal and can appear to hang. This can be caused by the VM operating system not matching the operating system specified during creation of the VM. For example, Windows Vista is selected as the Guest OS for the VM during creation but the actual guest operating system is Windows 7.
Workaround: Allow adequate time for the installation to complete (up to 4 hours).
Workaround: Upgrade your hypervisor software to a version that has a Guest OS that matches the VMs operating system. For example, Windows 7 and Windows Server 2008 R2 (x64) are not natively supported in VMware Workstation versions earlier than 7.0 or ESX/ESXi versions before ESXi 4.0.0 Build 208167.
When you try to add an additional Primary Server by using the administrator user created in the User Source, the installation log file displays the following message:
<Message><MessageID><![CDATA[0000]]></MessageID><MessageString><![CDATA[ConfigureAction failed!: com.novell.zenworks.datamodel.exceptions.InternalDataModelException:com.novell.zenworks.datamodel.exceptions.UntrustedCertificateException:com.novell.zenworks.datamodel.exceptions.UntrustedCertificateException:javax.naming.CommunicationException: simple bind failed:<server:port> [Root exception isjavax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException:No trusted certificate found]
Workaround: You must use the administrator users created in ZENworks 11. Users configured in a User Source where SSL is enabled might not be able to add additional Primary Servers to the zone.
For more information on creating a user, see the ZENworks 11 System Administration Reference.
If your Management Zone consists of Windows 7 SP1 or Windows Server 2008 R2 SP1 devices, the devices might fail to register with the ZENworks 11 Primary Server if the ZCM 11.0 Combined Patch has not been applied on all the Primary Servers in the Management Zone.
Workaround: Apply the ZCM 11.0 Combined Patch on all the Primary Servers in the Management Zone.
This section contains information about ZENworks 11 issues that might occur while working with ZENworks 11:
This section contains information about the general issues that might occur while working with ZENworks 11.
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.
The settings that you configure at the zone, device folders, or on individual devices by using ZENworks Control Center or the zman commands might be applied to the devices after approximately 10 minutes.
Workaround: If you want the settings to be applied to the devices immediately after you configure them, manually run the following command on each managed device for which you have configured the settings:
zac ref bypasscache
If ZENworks Control Center is opened in multiple browsers and you choose to perform an operation on an object in one browser when the same object is being modified or accessed in the other browser, an exception might occur.
For example, if you update an object in one session of ZENworks Control Center when the same object has been deleted in another session of ZENworks Control Center.
Workaround: None.
This section contains information about issues that might occur when you use Asset Management.
If the ZENworks Asset Management 7.5 zone is connected to an Oracle database, migration of ZENworks Asset Management 7.5 objects to ZENworks 11 Asset Management fails with an authentication error if the Oracle Client version is 10.2.0.x.
Workaround: Do one of the following before migrating the objects:
Upgrade the Oracle 10.2.0.x client to Oracle 11.2.0.
Downgrade the Oracle 10.2.0.x client to Oracle 10.1.0.2.
For more information, see TID 7006490.
This section contains information about issues that might occur with the Standard Edition of AdminStudio 9.5.
In the Bundle Creation page of the AdminStudio Distribution Wizard for ZENworks Configuration Management, if you select the 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 Novell Support Knowledgebase.
This issue occurs only with AdminStudio 9.5.
Workaround: None.
This section contains information about issues that might occur when you use bundles in ZENworks Configuration Management.
If you use ZENworks Control Center to disable or enable a bundle that has been recently opened, the changes are not immediately reflected on the bundle’s page.
Workaround: In ZENworks Control Center, refresh the bundle page to reflect the changes.
The Content Replication settings of a bundle is applied only to the published version of a bundle. However, the sandbox and older versions of the bundle gets the settings applied at the folder level or the zone level (in that order).
Workaround: To enable all the versions of a bundle to get the same Content Replication settings, do one of the following:
Override the settings at the folder or the zone level. However, this affects all the bundles within the folder or zone.
Move the bundle to a folder and override the settings at the folder level. However, this affects all the bundles within the folder.
This section contains information about issues that might occur when you use ZENworks Endpoint Security Management.
Section 4.5.2, The VM operating system crashes when shutting down
Section 4.5.3, Forcing an immediate update of Endpoint Security zone settings
Section 4.5.4, A hang occurs when copying a file to an RSD password-encrypted folder
Section 4.5.5, Access denied to RSD when a decryption password is not entered
Section 4.5.6, Intermittent crash when creating diagnostic package on Windows 7 64-bit devices
Section 4.5.7, Path-based exceptions for Windows Firewall are not working
The Endpoint Security Agent does not support user-assigned security policies on devices where Fast User switching is used (that is, switching between user accounts without quitting applications and logging out).
Workaround: In environments where Fast User switching is required, assign security policies to the device, not to the user.
When you run the Endpoint Security Agent on a VM client operating system such as Windows XP or Windows 7, the VM operating system might crash when manually shutting down.
Workaround: None.
By default, Management Zone settings are cached on the ZENworks Server and the cache is updated every 10 minutes. Because of this, if a change is made to a zone setting, devices don’t receive the changes until the next cache update, which might be as long as 10 minutes.
For ZENworks Endpoint Security Management, the following are stored as zone settings:
Location and network environment settings
Zone security policies
Effective policy report settings
Data encryption keys
If you change any of these settings and you want to apply them immediately to a device, you must use the zac command line utility on the device to bypass the ZENworks Server cache and retrieve the new settings. To do so, run the following command on the device:
zac ref general bypasscache
When you copy a file to a password-encrypted folder on a removable storage device (RSD), if you use the Copy dialog box to cancel the copy before you enter the encryption password in the Password Encryption dialog box, the copy process stops responding and the device appears to hang.
Workaround: Cancel the copy by using the button in the Password Encryption dialog box rather than in the Copy dialog box.
If the Data Encryption policy that is applied to a device is configured to require a decryption password, the decryption password applies to both Safe Harbor folders and removable storage devices. The password must be entered before either a Safe Harbor or removable storage device can be used.
The decryption password prompt is displayed at Windows startup. If a USB device is inserted before the device’s user enters the decryption password and the user attempts to access the device, access is denied. The device becomes accessible only after the user enters the decryption password.
A Windows crash sometimes occurs the first time a diagnostics package is created on a Windows 7 64-bit device. This crash is intermittent and does not occur on all machines.
Workaround: The crash only occurs the first time a diagnostics package is created. Reboot the machine and create the diagnostics package again.
After enforcement of a Data Encryption policy on a Windows XP/Vista/7 device, Windows XP and Windows Vista users are unable to add new path-based exceptions to the Windows Firewall through the Windows Firewall interface. For Windows XP/Vista/7, all path-based exceptions that existed on devices prior to enforcement of the Data Encryption policy no longer work.
Workaround: To add new path-based exceptions on Windows XP and Windows Vista:
In the Windows registry, locate the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Zesocc
Locate the ReparseExclusions value.
This is a REG_MULTI_SZ value that is prepopulated with the following string:
\PROGRAM FILES\NOVELL\ZENWORKS\BIN\NZRWINVNC.EXE
To add another application, double-click the ReparseExclusions value and specify the application path in the Value Data list.
Do not include the drive letter in the path. The path is relative to the root, as shown under Step 2.
Reboot the computer.
Add the applications through the Windows Firewall interface.
Workaround: To enable existing path-based exceptions to work on Windows XP/Vista/7:
In the Windows registry, locate the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Zesocc
Locate the ReparseExclusions value.
This is a REG_MULTI_SZ value that is prepopulated with the following string:
\PROGRAM FILES\NOVELL\ZENWORKS\BIN\NZRWINVNC.EXE
To add an application already defined as an exception in the Windows Firewall, double-click the Re parse Exclusions value and specify the application path in the Value Data list.
Do not include the drive letter in the path. The path is relative to the root, as shown under Step 2.
Reboot the computer.
This section contains information about issues that might occur when you use Intel AMT in ZENworks Configuration Management.
When you enter the credentials on an Intel AMT device during provisioning, the device is sometimes not discovered.
Workaround: To ensure that the device is discovered, use the following steps to reprovision the device:
Unprovision the device, then disable Remote Configuration.
Save the changes, then restart the device.
After the device has restarted, enter the BIOS screen, then enable Remote Configuration.
Enter the credentials, then provision the device.
Verify if the device is getting discovered. Repeat Step 1 through Step 5 to reprovision the device until the device is discovered.
If you restart the Novell ZENworks Loader Service while provisioning, unprovisioning, deleting, or searching an iAMT device through a search filter, the status of the device becomes suspended.
Workaround: Remove the Intel AMT device by unprovisioning it:
In ZENworks Control Center, click .
Click .
Click the link to view all the discovered Intel AMT devices.
Select an Intel AMT device that you want to provision, then click .
If you want to delete the Intel AMT device after unprovisioning fails, select the check box.
Click .
If you want to provision an Intel AMT device, you must configure it.
For more information on how to configure an AMT device, see the Novell ZENworks 11 Out-Of-Band Management Guide
This section contains information about issues that might occur when you use Linux Package Management in ZENworks Configuration Management.
If you use the zac dup command to upgrade an OES 2 SP1 managed device to OES 2 SP2, the upgrade fails with the Out-of-memory exception. This is because ZENworks Adaptive Agent uses the default JVM memory of 128 MB to upgrade, but the memory cannot handle large bundles and packages.
Workaround: Increase the JVM memory size of the OES 2 SP1 managed device before upgrading it to OES 2 SP2:
Open the /etc/init.d/novell-zenworks-xplatzmd file in a text editor.
Search for the PARAMS to JSVC section in the file, then locate the EXTRA_OPTS variable.
Prepend -Xms256m -Xmx256m to the EXTRA_OPTS variable as follows:
EXTRA_OPTS="-Xms256m -Xmx256m -Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory -Djavax.xml.stream.XMLOutputFactory=com.ctc.wstx.stax.WstxOutputFactory -Djavax.xml.stream.XMLEventFactory=com.ctc.wstx.stax.WstxEventFactory -Djava.rmi.server.hostname=127.0.0.1"
Save the /etc/init.d/novell-zenworks-xplatzmd file.
Restart the ZENworks Adaptive Agent by running the /etc/init.d/novell-zenworks-xplatzmd restart command.
Workaround: None.
After you delete a bundle that was created by replicating a ZLM Subscription with the option selected, if you choose to immediately replicate the ZLM Subscription again with the option selected, the replication might fail.
Workaround: Wait for at least 15 minutes before you start replicating the ZLM Subscription again.
This section contains information about issues that might occur when working with locations and network environments in ZENworks 11.
ZENworks database must be up and running before the ZENworks Server Service starts so that the ZENworks Location Web Service can acquire a reference to a valid service to the database.
This section contains information about issues that might occur when logging in to various locations in ZENworks 11.
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.
Workarounds:
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.
This section contains information about issues that might occur during migration to ZENworks Configuration Management.
If you run the ZENworks Configuration Management Migration utility on a device that has Firefox 3.0.x set as a default browser, the help file is not displayed when you click the help icon.
Workaround: Set Firefox 2.0 or Internet Explorer as the default browser on the device.
This section contains information about issues that might occur when you use ZENworks 11 Patch Management.
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.
Patch Management cannot deploy the following patches on SLES 11 SP1:
Workaround: Disabling and enabling custom patches is currently not supported. The custom patches are enabled by default. If you do not require a custom patch, delete it.
When you try to download signatures or patches, in /var/opt/novell/log/zenworks/loader-messages.log, multiple error messages of the following form are displayed:
Signature Download XXX .pls failed
A possible cause might be that /opt/novell/zenworks/zpm is owned by root instead of zenworks.
Workaround: Do the following:
Open a terminal and run the following command:
chown zenworks:zenworks /opt/novell/zenworks/zpm
Restart Novell ZENworks Loader service by running the following command:
/etc/init.d/novell-zenloader restart
(Optional) If you want to start the patch replication at the scheduled time, and if the replication is desired immediately, perform the following:
In ZENworks Control Center, click
Click > .
Click to start the replication.
For more details, see TID 7007532 available in the Novell Support Knowledgebase.
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: None
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 group should 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 the issues that might occur when you use ZENworks 11 Policy Management.
Some policies might not be applied when a user logs in to a Terminal Server session. The policy is usually automatically enforced during the next device refresh schedule. For example, the Browser Bookmarks policy, the iPrint policy, and Internet Explorer maintenance settings that are configured in the Group policy are not applied to the device.
The ZEN user daemon might not have started when the policies were enforced on the device.
Workaround: If you want to enforce a policy immediately on the device, you must manually refresh the ZENworks Adaptive Agent in one of the following ways:
Right-click the ZENworks icon, then select .
At the command prompt, run the zac ref command.
Creating roaming profiles on a Windows 2008 R2 shared location is not supported for Windows managed devices. If you try accessing the roaming profile, Windows automatically logs in to a local or temporary profile.
Workaround: None.
If you use ZENworks Control Center to disable or enable a policy that has been recently opened, the changes are not immediately reflected on the policy page.
Workaround: In ZENworks Control Center, refresh the policy page to reflect the changes.
The Content Replication settings of a policy are applied only to the published version of a policy. However, the sandbox and older versions of the policy have the settings applied at the folder level or the zone level (in that order).
Workaround: To enable all the versions of a policy to get the same Content Replication settings, do one of the following:
Override the settings at the folder or the zone level. However, this affects all the policies within the folder or zone.
Move the policy to a folder and override the settings at the folder level. However, this affects all the policies within the folder.
This section contains information about issues that might occur when you use the Remote Management feature in ZENworks Configuration Management.
If you remotely connect to a managed device through Remote Desktop Connection (RDP), then download and install the 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 Microsoft Support Web site and install it on the managed device.
Workaround: Install the Remote Management Viewer on a SUSE Linux Enterprise Server or SUSE Linux Enterprise Desktop device.
The ZENworks Reporting solution is based on BusinessObjects Enterprise XI 3.1 Service Pack 3 (SP3). 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 3.1 SP3, see the BusinessObjects XI documentation Web site.
Section 4.15.3, Unable to launch the ZENworks Reporting Server InfoView
Section 4.15.8, ZENworks Reporting Server does not support some BusinessObjects XI 3.1 SP3 features
Section 4.15.9, ZENworks Reporting Server installation on a Windows Server 2008 R2 device fails
Section 4.15.13, Uninstallation of ZENworks Reporting Server in GUI mode hangs on OES 2 SP2 x86_64
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 click on 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 when the Administrator tries to run the Web Intelligence Report (WEBi).
Workaround 1: Do the following:
Log out from the ZENworks Reporting Server InfoView.
Delete the cookies from your browser.
Close all browser instances.
Log in to ZENworks Control Center, then launch the ZENworks Reporting Server InfoView.
Workaround 2:In case, the error message is displayed even after deleting the browser cookies. Do the following:
On Windows: Restart the Server Intelligence Agent:
From the desktop menu, click > > > > to display the Central Configuration Manager window.
Click .
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:
/etc/init.d/BobjEnterprise120 stop
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:
/etc/init.d/BobjEnterprise120 start
Wait 2 to 3 minutes for all the services to start.
ZENworks Reporting might not contain a reference to users that were created by using the ZENworks 10 Configuration Management SP2 user source. Therefore, ZENworks Reporting fails when you log in to ZENworks Control Center by using an administrator account (such as Administrator@windowdomain.com) created in ZENworks Configuration Management 10 SP2.
Workaround: On the ZENworks Reporting Server, use the following command to create users for the administrator account that was created by using the ZENworks 10 Configuration Management SP2 user source:
zman rpau complete_user_name
where the complete_user_name is the administrator account, such as Administrator@windowdomain.com.
If you launch the ZENworks Reporting Server InfoView in Firefox 3.5, and you select as the target window in the Create Hyperlink dialog box while linking a ZENworks Report to a User Details Report, the User Details Report data is not displayed in the new browser window.
Workaround: While linking a ZENworks Report to a User Details Report in a Firefox 3.5 browser, select as the target window in the Create Hyperlink dialog box.
Workaround: See TID 7006288 at Novell Support.
The following features of BusinessObjects XI 3.1 SP3 are not supported in ZENworks Reporting Server:
Encyclopedia
Crystal Reports
My Dashboard
If the IP Helper service is running on a Windows Server 2008 R2 device, the ZENworks Reporting Server installation fails.
Workaround: Disable the IP Helper service:
Click > > > >
Right-click , then select .
In the drop-down list, select .
Click , then restart the device.
Install ZENworks Reporting Server.
For more information on installing the ZENworks Reporting Server, see the Reporting Server Installation Guide.
In the ZENworks Reporting Server InfoView, when you run a custom report for the Launch Status object under the Bundles and Policies folder created in ZENworks 10 Configuration Management SP3 in ZENworks 11, you might encounter the following error:
some objects are no longer available in the universe. See your Business Objects administrator. (Error WIS 00001)
Workaround: Click to close the error message dialog box, then do the following to add the Launch Status object:
Click.
In the Universe pane, navigate to > > > .
Drag the Launch Status object to the Results Object pane.
Click .
Save the report.
The Manageable Devices filter might not include the Linux, Windows 7, and Windows Server 2008 R2 devices while generating the custom report.
Workaround: Do the following:
In ZENworks Control Center, click .
Click .
Click > .
Delete the Manageable Devices object in the Query Filter pane.
Include the Linux, Windows 7 and Windows Server 2008 R2 devices:
In the Universe pane, navigate to >
Drag the Network Device Type object to the Query Filters pane.
In the Universe pane, navigate to > > > .
Drag the OS Category and OS Platform objects to the Query Filters pane.
Click the icon next to each filter.
Select from the pop-up menu.
Select the desired values, then add them to the List pane.
Click .
Workaround: Do the following:
In ZENworks Control Center, click .
Click to launch the ZENworks Reporting Server InfoView.
Right-click any Web Intelligence Report, then click .
In the Schedule pane, click .
Click .
In the Output Format panel, select the check box.
In the Output Format Details panel, select the check box.
Click .
In the Options and Settings panel, deselect the check box.
In the Directory option, specify the path to the directory on the destination device to save the report instance.
Fill in the appropriate fields, then click .
If you choose to uninstall the ZENworks Reporting Server from an OES 2 SP2 x86_64 by running the uninstallation program in the GUI mode, the program might take about 45 minutes to finish the uninstallation. During this time, the uninstallation program might appear to hang even though ZENworks Reporting Server is successfully uninstalled.
To verify that ZENworks Reporting Server has been uninstalled:
In ZENworks Control Center, click .
Check whether the ZENworks Reporting Server InfoView is disabled.
Check whether the Business Objects Enterprise service directory was removed:
/etc/init.d/BobjEnterprise120 service
Check whether the Business Objects Enterprise directory was removed:
/opt/novell/zenworks/share/boe folder
Check the ZENworks Reporting Server uninstallation log file:
The /var/opt/novell/log/zenworks/ZRSuninstall.log file must display the following message:
ZRS Uninstallation Completed Successfully!
The action will not work on existing custom reports when you use a Firefox 5 browser.
Workaround: None
The action will not work on existing custom reports when you use a Firefox 5 browser. This is because BusinessObjects Enterprise XI 3.1 SP3 does not support the Firefox 5 browser.
Workaround: None
This section contains information about issues that might occur with Satellite devices in ZENworks 11.
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 the tab > select the check box next to the Satellite device, click > then click .)
A Linux managed device might not be promoted as a Satellite with the Authentication role even though you have successfully configured the Authentication role for the device and have subsequently refreshed the device. The following exception is logged in the error log file:
Error Deploying WebApp : javax/servlet/Servlet ClassNotFoundException
Workaround: Manually refresh the Linux managed device. If the Authentication Satellite is still inactive or you are unable to log in, restart the agent service by using /etc/init.d/novell-zenworks-xplatzmd.
If you change the Imaging content replication schedule for an Imaging Satellite, the imaging content is replicated from the Primary Server to the Satellite according to the default schedule set while promoting the managed device to the Imaging Satellite, and not according to the revised schedule.
Workaround: To change the imaging content schedule after promoting a managed device to an Imaging Satellite:
Remove the Imaging role from the Satellite.
For detailed information on how to demote a Satellite to a managed device, see “Removing the Roles from a Satellite” in the ZENworks 11 System Administration Reference.
Add the Imaging role to the Satellite, then configure the desired imaging content replication schedule while configuring the role.
For detailed information on how to add the Imaging role to a Satellite, see “Adding and Configuring Satellites Devices” in the ZENworks 11 System Administration Reference.
This section contains information about issues that might occur with the ZENworks Adaptive Agent in ZENworks 11.
If you manually postpone the distribution activity during the distribution of a Linux bundle, the download of the file is immediately canceled; however, the following error message is displayed:
Inner Cache Error
Workaround: None. Ignore the error message. You can continue with the distribution activity at a later time.
If you have configured a bundle to display its shortcut in the managed device Menu and you assign this bundle to a Windows 7, Windows 2008, or Windows 2008 R2 device, the bundle shortcut icon is not correctly displayed in the menu.
Workaround: Download the patch from Microsoft Support site.
For more details, see TID 7005032 available in the Novell Support Knowledgebase.
This section contains information about issues that might occur with the ZENworks Adaptive Agent in ZENworks 11.
If you manually postpone the distribution activity during the distribution of a Linux bundle, the download of the file is immediately canceled; however, the following error message is displayed:
Inner Cache Error
Workaround: None. Ignore the error message. You can continue with the distribution activity at a later time.
If you have configured a bundle to display its shortcut in the managed device Menu and you assign this bundle to a Windows 7, Windows 2008, or Windows 2008 R2 device, the bundle shortcut icon is not correctly displayed in the menu.
Workaround: Download the patch from Microsoft Support site.
For more details, see TID 7005032 available in the Novell Support Knowledgebase.
This section contains information about the issues that might occur when using ZENworks Virtual Appliance.
When you try to install VMware tools on ZENworks 11 Virtual Appliance, the installation displays the following error:
Searching for a valid kernel header path... The path "" is not valid.
Workaround: Before installing VMware tools on ZENworks 11 Virtual Appliance:
Download kernel-default-devel-2.6.32.19-0.3.1.x86_64.rpm from the Novell Download Web site to a device other than the ZENworks 11 Virtual appliance.
Copy the RPM that you downloaded in Step 1 to a temporary location on the appliance by using scp.
Install the RPM by running the following command:
rpm -ivh kernel-default-devel-2.6.32.19-0.3.1.x86_64.rpm
Workaround: To enable firewall, do the following:
On ZENworks Appliance, open a terminal and run the following commands:
To start the firewall on the ZENworks Appliance immediately:
SuSEfirewall2 start
To configure the firewall service to start whenever the device boots:
yast2 firewall startup atboot
For more details, see TID 7007548 available in the Novell Support Knowledgebase.
This issue might occur after you try to upgrade ZENworks Linux Server to ZENworks 11 through media based or appliance upgrade.
Workaround: For detailed steps to address this issue, see TID 7007711 available in the Novell Support Knowledgebase.
You cannot stop the ZENworks Loader Service in ZENworks Appliance because the loader service hangs.
Workaround: To stop the loader service:
At the terminal, to retrieve the process ID of ZENworks Loader Service run the following command:
ps --no-heading ww -C java | gawk '/com\.novell\.zenworks\.loader\.ZENLoader/{print $1}'
Kill the process by running the following command:
kill -9 <Process ID>
Replace Process ID with the output from the command executed in Step 1.
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.
Workaround: None.
Workaround: Before executing the rpsv and rpgn commands, ensure that the specified destination path has the read-write-execute (rwx) permissions for all Linux users.
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 © 2011 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.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.