Content Replication

The Content Replication panel lets you determine how often content (bundle, policy, and patch files) is synchronized between the ZENworks Servers, at what rate is the content synchronized, and specify whether the ZENworks Agents on managed devices and Satellite devices compares content checksums.

When a bundle or policy that contains content is added to the Management Zone, the ZENworks database is updated to reflect the addition of the content. ZENworks servers are responsible for periodically reading the ZENworks database to discover new content. Each ZENworks server that does not have the content then retrieves the content from a server where it resides.

If content has been removed from the Management Zone, each ZENworks Server also removes the obsolete content during the periodic update.

Primary Server Recurring Content Replication Schedule

The content replication schedule determines how often a ZENworks Server checks for new or removed content from other ZENworks Servers in the zone. The default schedule is 1 hour.

Primary Server Output Throttling in KB/Sec

This throttling rate determines the maximum amount of content (in kilobytes per second) that a ZENworks Server transfers when replicating content to other content servers or when distributing content to managed devices. Select None if you do not want to limit the maximum amount. Otherwise, select a maximum amount.

Agent Content Checksum

The Agent Content Checksum setting lets you specify whether the ZENworks Agent on managed 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.

Satellite Content Checksum

The Satellite Content Checksum setting lets you 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.

Default Satellite Server Output Throttling in KB/Sec

This throttling rate determines the maximum amount of content (in kilobytes per second) that a ZENworks Satellite Server transfers when replicating content. Select None if you do not want to limit the maximum amount. Otherwise, select a maximum amount.

Default Satellite Server Content Replication Schedule

The Default Satellite Server Content Replication Schedule lets you specify how often you want the Satellite’s content to be updated from the parent Primary Server:

No Schedule: If you select No Schedule, content is never automatically updated from the parent Primary Server. To manually replicate the content run the zac wake-cdp (cdp) command on the Satellite.
Recurring: The Recurring scheduling option lets you repeat the event at a specified interval. You can select Days of the Week, Monthly, or Fixed Interval.

When a Device Is Refreshed: This schedule causes the event to occur each time the ZENworks Agent performs a refresh on the device. The Delay execution after refresh option lets you delay the event so that it does not happen immediately upon refresh. You can specify the number of days, hours, or minutes by which you want to delay the event.

Days of the Week: This schedule lets you specify the days during the week that you want the event to run. The event is run on these same days, every week.
- Sun... Sat: Specifies the days of the week you want to run the event.
- Start Time: Specifies the time you want to run the event.
- Process Immediately if Device Unable to Execute on Schedule: For some reason, if the event does not run on the schedule you configured, to trigger the event immediately, you can select this option.
- Use Coordinated Universal Time: The Start Time is converted to Universal Coordinated Time (UTC). Recommended, if the management zone is across geographical locations. Select this option to indicate that the Start Time you entered is already in Coordinated Universal Time and should not be converted. For example, suppose you are in the Eastern time zone. If you enter 10:00 a.m. and select this option, the Start Time is scheduled for 10:00 UTC. If you don’t select this option, the Start Time is scheduled for 14:00 UTC because Eastern time is UTC - 4 hours.
- Start at a Random Time between Start Time and End Time: Starts the event at a randomly selected time between the time you specify in the Start Time and End Time fields. You can use this option to avoid possible network overload from concurrently scheduled events.
- Restrict Schedule Execution to the Following Date Range: Limits running the event to the time period specified by the starting and ending dates.
Monthly: This schedule lets you specify one or more days during the month to run the event.
- Day of the Month: Specifies the day of the month to run the event. Valid entries are 1 through 31. If you specify 29, 30, or 31 and a month does not have those days, the event is not run that month.
- Last Day of the Month: Runs the event on the last day of the month, regardless of its date (28, 30, or 31).
- First Sunday: Specifies a specific day of a week. For example, the first Monday or the third Tuesday. Click to add multiple days.
- Start Time: Specifies the time you want to run the event.
- Process Immediately if Device Unable to Execute on Schedule: For some reason, if the event does not run on the schedule you configured, to trigger the event immediately, select Process immediately if device unable to execute on schedule.
- Use Coordinated Universal Time: The Start Time is converted to Universal Coordinated Time (UTC). Recommended, if the management zone is across geographical locations. Select this option to indicate that the Start Time you entered is already in Coordinated Universal Time and should not be converted. For example, suppose you are in the Eastern time zone. If you enter 10:00 a.m. and select this option, the Start Time is scheduled for 10:00 UTC. If you don’t select this option, the Start Time is scheduled for 14:00 UTC because Eastern time is UTC - 4 hours.
- Start at a Random Time between Start Time and End Time: Starts the event at a randomly selected time between the time you specify in the Start Time and End Time boxes. You can use this option to avoid possible network overload from concurrently scheduled events.
- Restrict Schedule Execution to the Following Date Range: Limits running of the event to the time period specified by the starting and ending dates.
Fixed Interval: This schedule lets you specify an interval between days to run the event. For example, you can run the event every 14 days.
- Months, Weeks, Days, Hours, Minutes: Specifies the interval between times when the event is run. You can use any combination of months, weeks, days, hours, and minutes. For example, both 7 days, 8 hours and 1 week, 8 hours provide the same schedule.
- Start Date: Specifies the initial start date for the interval.
- Start Time: Specifies the initial start time for the interval.
- Process Immediately if Device Unable to Execute on Schedule: For some reason, if the event does not run on the schedule you configured, to trigger the event immediately, select this option.
- Use Coordinated Universal Time: The Start Time is converted to Universal Coordinated Time (UTC). Recommended, if the management zone is across geographical locations. Select this option to indicate that the Start Time you entered is already in Coordinated Universal Time and should not be converted. For example, suppose you are in the Eastern time zone. If you enter 10:00 a.m. and select this option, the Start Time is scheduled for 10:00 UTC. If you don’t select this option, the Start Time is scheduled for 14:00 UTC because Eastern time is UTC - 4 hours.
- Restrict Schedule Execution to the Following Date Range: Limits running of the event to the time period specified by the start date, end date, and end time.