This role enables the managed device to distribute content (bundles, policies, system updates, and patches) to other devices.
When you set up a device to function with a Content role, you must specify a Primary Server as its parent. The device with the Content role receives all content from its parent Primary Server. Any content you want hosted on a Satellite with the Content role must also be hosted on its parent Primary Server. If the content is not hosted on the new Primary Server, it is added.
Select the check box next to, click , then click .
Fill in the fields:
Content Type: Select a Content Type (for example,, , or Server).
NOTE:If you chooseas the and configure the settings to replicate the Imaging content, these settings are automatically reflected in the Configure Imaging Content Replication dialog box invoked while configuring the Imaging role to the device. Similarly, the Imaging content replication settings configured while configuring the Imaging role to a device are automatically reflected in the Configure Content Type Replication dialog box invoked while configuring the Content role with the Imaging content type to the device.
Throttle (in KB/sec): Select the throttle rate. This rate specifies the maximum rate at which content (in kilobytes per second) is replicated. The actual rate can be lower, depending on other factors, including the number of downloads.
NOTE:The specified throttle speed only controls the rate at which ZENworks delivers content, it does not control the rate at which the NIC sends data to other applications. Thus the total bandwidth used by the server's NIC may be greater than the throttle speed set.
To view the traffic from ZENworks alone, you need to filter on the ports configured for your server. For example 80 and 443.
Duration: Click the up-arrow or down-arrow to set the content update duration period in minutes. Depending on the Schedule Type and its options you select, you need to be aware of the following:
Thesetting in all three scheduling types ( , , and ) is not the true end time when the content update stops processing. The end time specifies the end of the time period during which an update can start. For Fixed Interval replication in a newly promoted Satellite Server, the replication starts with a minimum delay of 1 day.
If you selector and set a random start and end time, the update starts between these times and continues for the specified duration. For example, if the is set at the default of 60 minutes and the update starts 10 minutes before the specified end time, content is updated for the entire 60 minutes. The same concept applies for the schedule. If is set at the default of 60 minutes and the end time does not allow enough time for the specified duration, content is updated for the entire 60 minutes.
If the Primary Server contains too much content to update during the specified duration, the update continues at the next regularly scheduled time. Content that already exists on the Satellite device is not updated again. Content that was not updated during the previous update and any new content added to the Primary Server is updated.
After the completion of content replication, if there is no content to replicate when the satellite queries for the missing content on the primary server, you can add more time in between the content replication retries in a given content replication duration. This will reduce the load on the primary server and the database.
If there is no content to replicate, the satellite content query interval doubles each time. By default the first wait is 10 minutes. For instance, the first query interval would be at 10 minutes, the next at 20, then 40, 80, 160, and so on until the interval has reached the maximum wait time of 1440 minutes. At any point of time, if the content for replication is found, then the query interval is reset to 10 minutes.
You can configure the initial wait time with the following registry key:
HKLM\SOFTWARE\Novell\ZCM: CDPRestartInterval (Reg_SZ): Seconds to wait
/etc/opt/novell/zenworks/conf/xplatzmd.properties CDPRestartInterval=Seconds to wait
Schedule Type: Select a schedule for how often you want the Satellite’s content to be updated from the parent Primary Server:
No Schedule: If you select zac wake-cdp (cdp) command on the Satellite., content is never automatically updated from the parent Primary Server. To manually replicate the content run the
Recurring: Select Section B.4, Recurring., , or , then fill in the fields. For more information, see
You should also consider the following:
We recommend you to set the schedule to 12 hours.
When you change the default Zone level Content Replication Schedule, the new schedule is not applied to the existing Satellite Servers that have been promoted to the Content role. For the new Content Replication Schedule to be applied to the promoted Satellite Servers, you can either demote and then promote the Satellite Servers to the Content role or you can edit the default Content Replication Schedule for each promoted Satellite Server.
Be aware that the cleanup action for content occurs every night at midnight.
If you do not set a schedule for a particular type of content, theschedule applies to all content of that type.
Clicktwice to return to the Add Satellite Server or Configure Satellite Server dialog box.
Continue with Step 4.
(Optional) Specify the content to host on the Content Server. For more information, see Section 28.4, Including or Excluding Content.
If you want to specify the content that the Satellite hosts, you can include or exclude content from being replicated to it.
If you want to include content that its parent Primary Server does not have, you must first add the content to the parent Primary Server.