Resolving Circular Dependency On The Master Primary Server - Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - PREBOOT SERVICES AND IMAGING REFERENCE 10.3 16-04-2010 User Manual

Preboot services and imaging
Hide thumbs Also See for ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - PREBOOT SERVICES AND IMAGING REFERENCE 10.3 16-04-2010:
Table of Contents

Advertisement

Monthly
This schedule lets you specify one or more days during the month to run the event.
Select Monthly, then fill in the following fields:.
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,
29 (for leap years), 30, or 31).
First Sunday: Specifies a specific day of a week. For example, the first Monday or the third
Tuesday. Click
Start Time: Specifies the time you want to run the event.
Process Immediately if Device Unable to Execute on Schedule: The event is run
immediately if, for some reason, the schedule you configured results in the event not being able
to run.
Use Coordinated Universal Time: The Start Time is converted to Universal Coordinated
Time (UTC). 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.
C.5 Resolving Circular Dependency on the
Master Primary Server
Circular dependency occurs when there are at least two servers, and the servers are master Primary
Server of each other.
For example, assume that there are two servers, Server A and Server B, in the Management Zone. In
ZENworks Control Center, you configure Server A to be the master Primary Server for Server B at
the Management Zone level. Later on, if you try to configure Server B to be the master Primary
Server for Server A at the device or folder level, you encounter the following circular dependency
error message:
Unable to apply the TFTP Replication settings. Remove the circular dependency
for the Master Primary Server. For more information, see the Help.
To successfully configure the TFTP replication settings, ensure that there is no circular dependency
on the master Primary Server that you select during the configuration of the TFTP replication
settings.
164 ZENworks 10 Configuration Management Preboot Services and Imaging Reference
to add multiple days.

Advertisement

Table of Contents
loading

This manual is also suitable for:

Zenworks 10 configuration management sp3

Table of Contents