In ZENworks Control Center, click the Configuration tab.
In the Management Zone Settings panel, click Bundle, Policy, Content > Pre-Caching Content.
Fill in the fields:
Content Type:
In this field, you can select the type of content that should be pre-cached. Here, you can pre-cache Bundles, Policies, and System Update Content.
After migrating to Advanced Patch Management, Linux Patches, Windows Patches, and Mac Patches options will be displayed.
By default, the system update content will bepre-cached to all the Primary Servers in the zone. The System Update check-box allows you to configure if the system update content should be pre-cached to all content Satellite Servers or none.
This setting will not be effective for existing System Update or existing Satellites. If you change the setting to precache, the existing satellites or existing System Update will not be affected. When a new System Update is imported or when you promote a device to content satellite, this setting will be honored.
Hence, to precache the system update content to Satellite Servers, ensure that you select the System Update check box before importing the System Update or before promoting a device to content satellite. To precache the system update content after the system update content is imported, run the run zman ccpe command.
Content Servers:
After you have selected the type of content to pre-cache, you use the Content Servers settings to select which Primary Servers and Satellites will pre-cache content.
You can select content servers in which the content should be pre-cached. You can either select a Primary Server or Satellite Servers.
To add a content server, click Add and then select the required Primary or Satellite servers.
To remove a content server, select the Primary or Satellite server and then click Remove.
To view only Primary Servers or Satellite Servers, click the All Servers drop-down, and then select Primary Servers or Satellite Servers. To view all servers, click the same drop-down and then select All Servers.
After configuring all the required options, click Apply or OK.
NOTE:You should be aware of the following when configuring pre-caching for Content Servers:
If content is not pre-cached to a Content Server, the server will request the content ondemand (in otherwords, when it is needed by a managed device) from an upstream Content Server, cache the content for future use, and serve it to the device. This is the default ondemand content behavior. When disabling pre-caching for a Content Server, you should check the Ondemand Content settings for the server to ensure that ondemand distribution is still enabled.
If pre-caching is enabled for a Content Server after it has already cached some content ondemand, the ondemand content will be deleted during the next pre-caching cycle and replaced by the pre-cached content. This ensures that only one copy of the content is cached on the Content Server.
The remediation bundle or Patch Agent bundles contain executables and metadata files that are deployed on the managed devices and they are required for running the patch scan or for performing remediation. These files do not constitute the actual patches, the actual patches are streamed on-demand to the managed devices. The remediation bundle, DAU, or Patch Agent bundles can be pre-cached but are only the executables or metadata files that get pre-cached and not the actual patches.
Satellite Content Checksum: Specify whether the ZENworks Agent on Satellite devices computes the checksum of downloaded content and compares that checksum to the stored checksum for that content on the ZENworks Primary Server.
Comparing checksums helps to ensure that no errors were introduced during content replication and that the content was not altered.
Under normal conditions, you should use the default of On. If your ZENworks System has serious performance issues, you can set this setting to Off to increase performance.
Click Apply or OK to save the changes.
You can adjust the Web Service Timeout value to suit your needs. For example, if a Satellite device is across a slow WAN link and there is missing content, the default 240-second timeout value might not be long enough to make the Web service call.
To modify the Web Service Timeout on a Satellite device:
For Windows, create the following string value in the registry on the Satellite device:
HKEY-LOCAL-MACHINE\SOFTWARE\Novell\ZCM\CDPWebCallWaitTimeout and set the value to the desired number of milliseconds.
For Linux, in the /etc/opt/novell/zenworks/conf/xplatzmd.properties file on the Satellite device, add the following line:
CDPWebCallWaitTimeout=xxx
where xxx is the desired timeout value in milliseconds.