You can configure server policies for containers, servers, and service locations. The policies allow you to automate use of NetWare functionality. See your NetWare documentation for specific information.
To configure server policies, review the instructions in the following sections:
For information on scheduling server policies, see Scheduling Policies.
The SNMP Community Strings and SNMP Trap Targets policies utilize SNMP.
To receive SNMP traps on your SNMP management console, you must copy the ZENTRAP.MIB file from the ZENworks for Servers Program CD or the ZENworks 6 Server Management Program CD to the location that your management console uses to manage MIBs, then compile it. Your SNMP management console will then be able to receive and interpret SNMP traps from ZfS.
ZENTRAP.MIB is located on the Program CD under ZfS\TEDPOL\SFILES\MIBS or ZENWORKSFORSERVERS\ZfS\TEDPOL\SFILES\MIBS.
The Search policy is used by the Distributor for information on how to read the eDirectory tree when the Distributor has been refreshed.
IMPORTANT: If you do not use the Search policy, ZfS will search up to [Root] and reread the objects every hour. Be sure to configure and enable the Search policy to limit unnecessary search traffic.
To configure the Search policy:
In ConsoleOne, right-click the Container Package > click Properties > click the Policies tab.
Click Search Policy > Properties > Search Level.
If the box under the Enabled column is not checked for the Search policy, click it before clicking Properties. A policy must be enabled to activate the Properties button.
To determine the upper limits of the search policy, select one of the following:
If you chose Selected Container, browse to select the container.
To determine searching limits in either direction of the item selected, enter a number. For example:
To determine the search order, click Search Order.
| Type | Description |
|---|---|
Object |
Server |
Group |
Server Group |
Container |
Container of Servers |
Use the arrow keys to change the order. You can also click Add or Remove to change which object types are used.
For ZfS 2 servers, to set the frequency for refreshing policies from eDirectory, click the Refresh Interval tab > click Policy Manager Will Refresh Policies From eDirectory > select the time increments.
For ZfS 3.0.2 servers, policies are refreshed when they are received at the Subscriber.
You can specify a refresh frequency. The default is once every hour.
If you leave both time increments at zero (days and hours), policies will not be refreshed from eDirectory, even if you have Policy Manager Will Refresh Policies From eDirectory checked.
Changes made to enabled policies are not enforced until they are refreshed at the given refresh interval. However, you can manually refresh all policies using the POLICY REFRESH command at the server console. The refresh rate is listed in seconds at the server console (1 hour = 3600 seconds).
Click OK to close the policy.
If you click Cancel, none of the Search policy changes made on any of the tabs will be saved.
To associate the policy package so that the Search policy will be enforced on the Distributor, click the Associations tab > click Add.
Browse to select the container where the Distributor object resides (or any container above it) > click OK.
If you click Cancel, the association you made will not be saved.
For ZfS 3.0.2 Policy and Distribution Services, the policies similar to those contained in the Server Package must be distributed for enforcement. Because the policies contained in the Server Package must be associated for enforcement, you must use the policies in the Distributed Server Package for ZfS 3.0.2 Policy and Distribution Services servers. For more information, see Configuring Distributed Server Package Policies.
For instructions on the policies contained in the Server Package that are applicable to ZfS 2 servers, see the ZfS 2 documentation on the Novell Documentation Web site.
For ZfS 3.0.2, only Server Inventory uses the ZENworks Database policy contained in the Server Package. For more information, see Configuring the Database Location Policy.
Because the Distributor does not receive Distributions, policies for a Distributor must be associated with the container where its object resides. The Service Location Package contains policies used by the Distributor.
The ZENworks for Servers License policy only applies to ZfS 2 servers. For more information, see the ZfS 2 documentation on the Novell Documentation Web site.
To configure Service Location Package policies, review the following sections:
Sets the TCP/IP address of the SMTP relay host that processes outbound Internet e-mail. This policy must be enabled if you select the E-Mail option for notifying or logging messages for the Distributor.
To configure the SMTP Host policy:
In ConsoleOne, right-click the Service Location Package > click Properties.
Click the SMTP Host policy > click Properties.
If the box under the Enabled column is not checked for the SMTP Host policy, click it before clicking Properties. A policy must be enabled to activate the Properties button.
Enter the TCP/IP address or DNS name of the relay host server > click OK.
To associate the policy package so that the SMTP Host policy will be enforced on the Distributor, click the Associations tab > click Add.
Browse to select the container where the Distributor object resides (or any container above it) > click OK.
If you click Cancel, the association you made will not be saved.
Use this property page to establish the targets (or locations) where you want SNMP traps sent from the Distributor. Each target must be a valid TCP/IP address or DNS name.
In ZfS 2, both this policy and the SNMP Trap Target Refresh policy are used to manage SNMP. In ZfS 3.0.2, this policy must be scheduled, because a new Schedule tab on the policy replaces the ZfS 2 SNMP Trap Target Refresh policy.
To configure the SNMP Trap Targets policy:
In ConsoleOne, right-click the Service Location Package > click Properties.
Click the SNMP Trap Targets policy > click Properties.
If the box under the Enabled column is not checked for the SNMP Trap Targets policy, click it before clicking Properties. A policy must be enabled to activate the Properties button.
To add items to the SNMP Trap Targets list on the SNMP Trap Policy tab, click Add.
On the SNMP Target dialog box, enter valid a TCP/IP address or DNS name > click OK.
To schedule the policy, click the Schedule tab > select a type in the Schedule Type field > configure the schedule:
Click OK when finished.
To associate the policy package so that the SNMP Trap Targets policy will be enforced on the Distributor, click the Associations tab > click Add.
Browse to select the container where the Distributor object resides (or any container above it) > click OK.
If you click Cancel, the association you made will not be saved.
This policy allows you to set default values for the attributes of Distributors and Subscribers. The default values become effective when you associate the Service Location Package to a container above where the Distributor or Subscriber object resides.
If you made changes to any default values for Distributors or Subscribers during installation of ZfS, the Use Policy check box will not be checked when the policy package is associated with the Distributors' or Subscribers' containers.
If you did not make changes to any default values during installation, the Use Policy check box will be checked when the policy package is associated with the Distributors' or Subscribers' containers, and the values in the Tiered Electronic Distribution policy will be used for the Distributor and Subscriber attributes.
IMPORTANT: The Tiered Electronic Distribution policy replaces, not supplements, the similar fields in a Distributor's or Subscriber's properties. Therefore, if you create a Tiered Electronic Distribution policy, make sure you fill in all of the fields on every tab in the policy that you will want to be applied to the affected Distributors or Subscribers. For example, if your Subscriber has a working directory entered in its object's properties, you don't enter a working directory in the Tiered Electronic Distribution policy, then later apply the policy by clicking the Use Policy check box on the Subscriber's properties, the Subscriber will no longer have a working directory available to it.
To configure the Tiered Electronic Distribution policy:
In ConsoleOne, right-click the Service Location Package > click Properties.
Click the Tiered Electronic Distribution policy > click Properties.
If the box under the Enabled column is not checked for the Tiered Electronic Distribution policy, click it before clicking Properties. A policy must be enabled to activate the Properties button.
On the General Settings tab, fill in the fields:
Input Rate: Sets the default input rate to minimize network traffic for TED objects. This determines the receive rate for Subscribers and Distributors. The default value is the maximum that the connection can handle. You can use this rate to control the use of narrow bandwidth links.
Output Rate: Sets the default output rate to minimize network traffic for TED objects. This determines the send rate for Distributors and Subscribers. The default value is the maximum that the connection can handle. There are three output priorities where you can specify a rate:
High Priority: These Distributions will be sent before any Medium or Low priority Distributions.
Medium Priority: These Distributions will be sent after all High priority and before any Low priority Distributions.
Low Priority: These Distributions will be sent after all High and Medium priority Distributions.
For more information, see Prioritizing Distributions.
Maximum Concurrent Connections: Specifies a default maximum number of Distribution threads that can be running concurrently for Distributors and parent Subscribers. The default value is unlimited (blank field).
This number can help in load-balancing on a Distributor's sending activity and spread network traffic over an entire scheduling window.
Connection Time-out: Specifies a default number of seconds before the Distributor times out when connecting to another node, or specifies the number of seconds a Subscriber will wait for a response from a Distributor (receiving) or a Subscriber (sending) before ending the connection.
After the time has transpired, a Distributor will end the connection and not retry until the Channel's Send schedule starts again. If a connection is ended during sending or receiving, a Subscriber will not start again until the next time the Channel's Send schedule starts.
The default value is 300 seconds (five minutes). The available range in seconds is 1 to 60,000. You should select a reasonable time to wait for a response from one node to another.
IMPORTANT: This interval must be increased on slow or busy links where longer delays are frequent.
Working Directory: Enter a default TED directory to store Distributions, persistent status, and temporary files on a server. The directory needs to be located where there is enough free space to handle processing of Distributions.
The Working Directory field allows the use of variables to specify the volume/drive and directory names. However, variables will only work with Subscribers.
IMPORTANT: Distributors are not able to resolve variables and will use exactly what is specified in the Working Directory field. For example, if the value was %VOL%TED1\WORKING, the Distributor would create a working directory on the SYS: volume named SYS:\%VOL%\TED\WORKING, because it could not resolve %VOL%.
For more information, see Working Directories.
Parent Subscriber: Subscribers should generally not receive their Distributions directly from a Distributor. You can browse for a Subscriber to be the default parent Subscriber for your whole network that will pass on Distributions when a Subscriber object might not have a parent Subscriber defined in its properties.
Disk Space Desired To Be Left Free: Use this as the default value to ensure there will be enough free disk space for receiving Distributions where you might not have this value defined in a Subscriber object's properties. A Subscriber will not attempt to receive a Distribution if the disk space value set here is insufficient.
Click the General tab > click Messaging > fill in the fields:
Server Console: Procedure to follow when displaying messages at the server console. The default is Level 4 (Information & Level 3 Messages).
SNMP Trap: Procedure to follow when sending SNMP traps. The default is Level 0 (No Messages).
Log File: Procedure to follow when recording information to a log file. The default is Level 5 (Trace Information & Level 4 Messages).
Filename: By default, this field is blank. Whatever log filename you select, it replaces TED.LOG for the servers where this policy is enforced.
To create a log file, enter the log file's filename using the following format:
installation_path\directory_path\filename.filename_extension
The installation_path is not required for ZENworks to locate the log file, but it is easier for you to locate the file if the path is included.
IMPORTANT: Because the log file can become quite large, for NetWare servers we recommend that you do not use the SYS: volume.
Some filename examples:
DIST.LOG
TEDLOG.TXT
Delete Log Entries Older Than __ Days: Controls disk space usage. For log files, it is important to set the message levels at minimal detail and to purge entries older than six days (the default).
E-Mail: Procedure to follow when sending e-mail messages. None or Errors Only are recommended to minimize unnecessary e-mail traffic. The default is Level 0 (No Messages).
Users: Add users, groups, or e-mail addresses.
Address Attribute: Displays the attribute of the associated user or group. You can change the attribute from the drop down list, which displays over three dozen options.
Following are some of these options:
To assign default values to variables used by the Subscriber, click the Variables tab > click Add > fill in the fields:
Variable: Name of the variable. It should indicate how the variable will be used. For example, WORKINGVOL.
The variable name can be derived from predefined and user-defined variables.
Value: The value that the Subscriber will use when this variable is specified. For example, DATA:.
A value can be another variable name. You can nest variables using this method.
To ensure that extraction will take place, provide an absolute path to the Subscriber. For example, if the path is only the DATA volume, make sure the colon (:) is included, because it is a necessary part of the full path.
Description: Describes how the variable will be used. For example:
Volume for the working directory.
Note that if a variable defined here does not exist in a Subscriber's variables list, it will automatically be added. However, if the variable does exist in the Subscriber's variables list, the definition in the Subscriber will prevail.
To assign a default refresh schedule for all Distributors, click the Schedule tab > click Distributor Refresh Schedule > select a schedule in the Schedule Type field > configure the schedule:
For information on the refresh schedule, see TED Object Schedules.
IMPORTANT: We recommend the Distributor's Refresh schedule be daily, unless changes to Distributions warrant a more frequent refresh. However, do not refresh the Distributor more often than every five minutes. The following can need up to five minutes to complete their processes: Distribution building, eDirectory replication, and tree walking (when no Search policy is defined).
To assign a default extraction schedule for all Subscribers, click the Schedule tab > click Subscriber Extract Schedule > select a schedule in the Schedule Type field > configure the schedule:
For information on the extraction schedule, see TED Object Schedules.
Click OK to close the policy.
To associate the policy package so that the Tiered Electronic Distribution policy will be enforced on the Distributor, click the Associations tab > click Add.
Browse to select the container where the Distributor object resides (or any container above it) > click OK.
If you click Cancel, the association you made will not be saved.
Sets the DN for locating a ZENworks Database object. This policy must be in effect for ZfS to locate a database file for logging successes and failures that are used in creating reports. If a database object is not identified with this location policy, ZfS will not use the corresponding database file to log reporting information. Therefore, you should create this policy for each database object in the tree.
Use this property page to select the database object that will be associated with the current ZENworks Database policy. The policy will not be in effect until you have distributed the policy to the Subscribers, or associated the policy with the Distributor.
The ZENworks database is used to store reporting information for Distributions and Server Policies.
To configure the ZENworks Database policy:
In ConsoleOne, right-click the Service Location Package > click Properties.
Click the ZENworks Database policy > click Properties.
If the box under the Enabled column is not checked for the ZENworks Database policy, click it before clicking Properties. A policy must be enabled to activate the Properties button.
Click the Policy/Distribution Management tab.
In the Database DN field, browse for the ZENworks Database object that represents the database for this policy > click OK.
To associate the policy package so that the ZENworks Database policy will be enforced on the Distributor, click the Associations tab > click Add.
Browse to select the container where the Distributor object resides (or any container above it) > click OK.
If you click Cancel, the association you made will not be saved.
You can configure Distributed Server Package policies to automate control of various server behaviors and processes and to automate control of SMTP Host TCP/IP addresses, SNMP Trap Targets, and the ZENworks database DN.
There are several Policies tab options for server policies, one for each supported operating system. The policies that are available on the General tab apply to servers on all platforms. The policies available on the specific platform tabs apply only to the servers for those platforms.
Platform-specific policies, such as those on the NetWare tab, always override similar policies on the General tab for a particular policy package.
All policies are contained in the NetWare policies. Therefore, only the NetWare policies are documented here. The information applies equally to each platform.
To configure Distributed Server Package policies, review the following sections:
The Copy Files policy enables copying of files on a server from one location to another by using policy configurations. You can either copy or move the files.
To configure the Copy Files policy:
In ConsoleOne, click the Distributed Server Package's container > right-click the Distributed Server Package > click Properties.
Click the Policies tab > select the platform from:
Click Add > click Copy Files > enter a policy name > click OK.
Click Properties.
The Copy Files tab displays.
Click Add.
Local File Copy #1 defaults. You can edit that name.
Fill in the fields:
Source Path: Enter the full path where the files to be copied are located.
You can use wildcards in the path:
Target Path: Enter the full path where the copied files are to be placed.
You can use wildcards in this path. This path does not need to mirror the source path. However, you could mirror an existing target path.
Include Subdirectories: Includes all subdirectories and their files beginning from the directory at the end of the path; otherwise, only the files in the directory at the end of the path will be copied.
Maintain Attributes: Maintains the file attributes in the target's file system that exist in the source's file system.
Overwrite Destination Files: Overwrites files of the same name in the destination directories, regardless of differences in file dates. If you do not enable this option, files of the same name will not be replaced.
Maintain Trustees: Maintains the file's trustee attributes.
When a File Is Locked: Select one or both:
Retry __ Times: Retries overwriting a locked file the number of times you select before failing to replace the file. Leave this check box unchecked to not replace locked files on the target file system.
Kill Connection of Open Files: Attempts to kill the connection of locked files so they can be overwritten. This applies only to files being extracted, not to files being accessed to build the Distribution. If a file belonging to a Distribution is locked when the Distribution is being built, the build will fail. Server and NLM connections cannot be killed.
Error Processing: Fail On Error is checked by default. This stops the file copying process when an error is encountered in copying. To continue file copying when an error is encountered, click Continue On Error.
Operation: Sets whether to copy or move the files identified in the Source Path.
Click the Schedule tab > schedule the policy (see Scheduling Policies).
Click OK to close the policy.
You can automate the use of SET parameters by your servers.
To configure NetWare SET parameters:
In ConsoleOne, click the Distributed Server Package's container > right-click the Distributed Server Package > click Properties.
Click the Policies tab > NetWare (or General).
Click Add > select NetWare Set Parameters.
Enter a name for this SET parameters policy > click OK.
Because the policies selected from this dialog box are plural, you can have multiple SET parameter policies listed on the Policies tab. Therefore, enter a unique name for this policy.
When you click OK after naming the SET parameters policy, it will be checked and selected on the Policies tab.
Click Properties.
The Set Commands tab displays.
Click Add.
The NetWare Server SET Command Wizard opens.
Select the server containing the SET parameters > click Next.
IMPORTANT: The Policy/Package Agent must be running.
Select all of the commands you want to configure in the policy.
You can select whole categories by clicking the check box for the category, or clicking the plus sign to expand a SET command category and clicking the check boxes for individual commands to be included.
WARNING: Do not select the Set Developer Option SET command and change the default of Off to On. This parameter is meant to help developers debug server abends. It disables some of the operating system checking to prevent certain abends from occurring. Also, if the Set Developer Option is turned On, running NCPTM scripts that require keyboard entry could abend the server.
Click Finish when you are finished selecting the commands.
The selected commands are now displayed in the Set Commands tab for the policy.
To edit a SET command, click its plus sign to expand its attributes.
To edit an attribute, click the attribute > click Edit.
A dialog box is displayed in which you can make changes to the attribute.
Repeat the previous step for each attribute to edit for a given SET command.
Repeat Step 10 through Step 12 to edit another SET command's attributes.
Schedule the policy (see Scheduling Policies).
Click OK to close the policy.
If you click Cancel, neither the schedule nor the SET parameter changes will be saved.
You can automate when and how you want a server to go down, and whether it should be automatically brought back up.
To configure a scheduled downing for a server:
In ConsoleOne, right-click Distributed Server Package > click Properties.
Click the Policies tab > NetWare (or other platform).
Click Add > select Scheduled Down.
Enter a unique name for the policy > click OK.
Because the policies selected from this dialog box are plural, you can have multiple Scheduled Down policies listed on the Policies tab. Therefore, enter a unique name for this policy.
When you click OK after naming the Scheduled Down policy, the policy will be checked and selected on the Policies tab.
Click Properties.
The Up Procedure tab displays.
Select the downing method:
| Downing Option | Description |
|---|---|
Reset Server |
Downs the server and then does a warm boot |
Restart Server |
Downs the server and then restarts it |
Down Server |
Downs the server, does not restart it |
Schedule the policy (see Scheduling Policies).
Click OK to close the policy.
If you click Cancel, neither schedule for your newly scheduled Down policy will be saved.
You can automate scheduled loading and unloading of NLM files and Java Class processes, and Linux and Solaris executables.
To configure the schedules:
In ConsoleOne, click the Distributed Server Package's container > right-click the Distributed Server Package > click Properties.
Click the Policies tab > NetWare (or other platform).
Click Add > select Scheduled Load/Unload.
Enter a name for this Load/Unload policy > click OK.
Because the policies selected from this dialog box are plural, you can have multiple Load/Unload policies listed on the Policies tab. Therefore, enter a unique name for this policy.
When you click OK after naming the Load/Unload policy, it will be checked and selected on the Policies tab.
Click Properties.
The Scheduled Load/Unload tab displays.
Click Add.
Select one of the following options:
Click an item for further instructions on configuring it.
Repeat Step 6 and Step 7 for each NLM or process to be included.
To rearrange the order, use the arrow keys.
Schedule the policy (see Scheduling Policies).
Click OK to close the policy.
If you click Cancel, your newly scheduled Load/Unload policy will not be saved.
You can automate the procedures your servers use when they are downed.
To configure the downing process for a server:
In ConsoleOne, click the Distributed Server Package's container > right-click the Distributed Server Package > click Properties.
Click the Policies tab > NetWare (or other platform).
Click the Server Down Process policy > click Properties.
If the box under the Enabled column is not checked for the Server Down Process policy, click it before clicking Properties. A policy must be enabled to activate the Properties button.
To configure procedures for downing, click the Down Procedure tab > Down Procedures.
To enable the policy's options, check the box labeled Follow This Procedure When a Down Server Is Triggered > enter the number of minutes to wait before downing the server.
To disable login before downing, check the box > enter the number of minutes before downing to disable login.
To drop connections before downing, check the box > enter the number of minutes before downing the server to drop connections.
To configure an order for unloading, click the Down Procedure tab > click Ordered Unload.
To configure reporting, click the Notification tab > Reporting.
To have another server send an SNMP alert if the server is not up after a specified time, check the Send SNMP Alert box > enter the number of minutes.
For information about displaying SNMP traps on your management console, see Compiling ZENTRAP.MIB.
To specify which servers can watch for the restart and send the alert in case of failure, click Add to display an ordered list of candidate servers.
Policy and Distribution Services starts at the top of the list to communicate with the first server and use it for the alert notification. If Policy and Distribution Services cannot communicate with a server, the next one on the list is tried. The first server that can be used will be the one that is scheduled to send the alert.
Browse to select a server.
To change the order, use the arrow keys.
To configure broadcast messages, click the Notification tab > Broadcast Messages > Send Messages To Connected Users.
Enter the number of times to send the message.
To broadcast custom text, enter it in the box.
To include the predefined message containing a time as the last line of your broadcast, check the box.
The x minutes is derived from dividing the number of times from Step 10.a into the number of minutes left before the server will be downed, then subtracting that amount (in whole minutes) for the amount to display in each broadcast. For example, if there are 10 minutes left and you select 5 in Step 10.a, the message will be broadcast every two minutes. The number of minutes left after each broadcast will be two minutes less than at the last broadcast.
To configure targeted messages, click the Notification tab > Targeted Messages > Send E-mail To Selected Users When Server Is Going Down.
To configure the conditions for downing a server, click the Conditions tab > Use Conditions.
To enter the conditions, click Add.
Select from the following conditions to specify when not to bring the server down:
Some of these conditions require you to enter valid names. Others use the Select Object dialog box to browse for them.
File Open: If the files that you specified are open. For example, an .EXE.
NLM Loaded: If the NLM files that you specified are running.
Server Connected: If the server that you specified is connected.
User Connected: If the users that you specified are connected.
Number of User Connections: If the number of users connected exceeds the number you specify. In other words, don't bring the server down if too many users would be affected.
Workstation Connected: If the workstations that you specified are connected.
Repeat Step 12.a and Step 12.b for each condition to add to the list.
To change the order, use the arrow keys.
Click OK to close the policy.
If you click Cancel, none of the Server Down Process policy changes made on any of the tabs will be saved.
You can automate script usage by your NetWare servers.
To configure server scripts:
In ConsoleOne, click the Distributed Server Package's container > right-click the Distributed Server Package > click Properties.
Click the Policies tab > NetWare (or other platform).
Click Add > select Server Scripts.
Enter a unique name for the policy.
Because the policies selected from this dialog box are plural, you can have multiple Script policies listed on the Policies tab. Therefore, enter a unique name for this policy.
When you click OK after naming the Script policy, it will be checked and selected on the Policies tab.
Click Properties.
The Script tab displays.
Click Add > select Server Scripts.
Enter a script name.
Script #1 displays.
Select the script type (NCF, NetBasic*, PERL).
Enter the script text.
Use the arrow keys to arrange the order to execute the scripts.
Schedule the policy (see Scheduling Policies).
Click OK to close the policy.
If you click Cancel, neither the schedule nor any of the scripts entered will be saved.
You can set the TCP/IP address of the relay host that processes outbound Internet e-mail.
To configure the SMTP Host policy:
In ConsoleOne, right-click the Service Location Package > click Properties.
Click the SMTP Host policy > click Properties.
If the box under the Enabled column is not checked for the SMTP Host policy, click it before clicking Properties. A policy must be enabled to activate the Properties button.
The SMTP Host tab defaults.
Enter the TCP/IP address or DNS name (such as mail.novell.com) > click OK to close the policy.
If you click Cancel, the TCP/IP address will not be saved.
This policy provides configuration and scheduling of SNMP community strings.
To configure the SNMP Community Strings policy:
In ConsoleOne, click the Distributed Server Package's container > right-click the Distributed Server Package > click Properties.
Click the Policies tab > NetWare (or other platform).
Click the SNMP Community Strings policy > click Properties.
If the box under the Enabled column is not checked for the SNMP Community Strings policy, click it before clicking Properties. A policy must be enabled to activate the Properties button.
The SNMP Community Policy tab displays.
Fill in the Community Strings fields:
Community Strings are case sensitive. Enter a string for each field as needed.
Click the Schedule tab > schedule the policy (see Scheduling Policies).
Click OK to close the policy.
You can set targets for SNMP traps for the Subscriber Agent and Policy/Package Agent.
For information about displaying SNMP traps on your management console, see Compiling ZENTRAP.MIB.
The following abbreviations are used in this section to represent these Windows registry locations:
AGENT_KEY: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\SNMP\Parameters
ZFS_KEY: HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Zenworks for Servers
The Windows SNMP trap target policy enforcer performs in the following sequence:
To configure the SNMP Trap Targets policy:
In ConsoleOne, right-click the Service Location Package > click Properties.
Click the SNMP Trap Targets policy > click Properties.
If the box under the Enabled column is not checked for the SNMP Trap Targets policy, click it before clicking Properties. A policy must be enabled to activate the Properties button.
Click Add.
Enter a new target > click OK.
HINT: Enter the TCP/IP address or DNS name of the target server. IPX addresses are not supported.
Click the Schedule tab > schedule the policy (see Scheduling Policies).
Click OK to close the policy.
If you click Cancel, none of the targets that you entered will be saved.
You can automate changes to text files on your servers.
To configure text file changes:
In ConsoleOne, click the Distributed Server Package's container > right-click the Distributed Server Package > click Properties.
Click the Policies tab > NetWare (or other platform).
Click Add > select Text File Changes.
Enter a unique name for the policy.
Because the policies selected from this dialog box are plural, you can have multiple text file policies listed on the Policies tab. Therefore, enter a unique name for this policy.
When you click OK after naming the text file policy, it will be checked and selected on the Policies tab.
Click Properties.
The Text Files tab defaults.
Click Add.
After one text file has been added, you will be given the opportunity to select whether you are adding another text file or another change item for the selected text file.
To add another text file, select Text File. It does not matter which text file or change item is selected in the left pane---the text file will be added to the far left level.
To add another change to a text file, in the left pane click the text file for the change > click Add > select Change. The change item will be added under the selected text file.
If you are adding a text file, enter the name of the text file.
Accept the default name (such as Change #1) or rename it > if you are adding a text file, click OK.
Click the down-arrow for the Change Mode field > select the change mode from the drop-down list.
Click the down-arrow for the Search Type field > select the search type from the drop-down list.
Enter the exact search string.
Check the box if you want the string search to be case sensitive.
To find all occurrences of the search string, make sure the box is selected, or deselect the box to find only the first occurrence.
Click the down-arrow for the Result Action field > select the action from the drop-down list that should result if a string is matched.
If you will be replacing a string or entering a new one, enter the text in the New String text box.
Repeat Step 6 through Step 15 for each text file to add or each change to be made.
To reorder the text files and change items, use the arrow keys.
Schedule the policy (see Scheduling Policies).
Click OK to close the policy.
If you click Cancel, neither the schedule nor any of the text files entered will be saved.
If you have installed the ZENworks database, you can set its DN so that the server this policy is associated with can find the database for logging information.
To configure the ZENworks Database policy:
In ConsoleOne, right-click the Service Location Package > click Properties.
Click the ZENworks Database policy > click Properties.
If the box under the Enabled column is not checked for the ZENworks Database policy, click it before clicking Properties. A policy must be enabled to activate the Properties button.
Click the Policy/Distribution Management tab.
The Inventory Management tab defaults. Make sure you are using the correct tab.
Enter the DN of your ZENworks Database object, or browse to select the DN > click OK to close the policy.
If you click Cancel, the DN will not be saved.
This policy provides basic configuration parameters for Policy and Distribution Services.
To configure the ZENworks for Servers policy:
In ConsoleOne, click the Distributed Server Package's container > right-click the Distributed Server Package > click Properties.
Click the Policies tab > NetWare (or other platform).
Click the ZENworks for Servers policy > click Properties.
If the box under the Enabled column is not checked for the ZENworks for Servers policy, click it before clicking Properties. A policy must be enabled to activate the Properties button.
The General - Status tab displays.
To determine the policy's general status:
Select the procedure to follow when displaying messages at the server console.
Select the procedure to follow when sending SNMP traps.
For information about displaying SNMP traps on your management console, see Compiling ZENTRAP.MIB.
Select the procedure to follow when recording information to a log file.
IMPORTANT: Set the E-Mail Messages option to either None or Errors Only. If you set this to a more detailed level, performance will degrade because of the extra e-mail messages that will be created.
To determine the policy's configuration, click the ZENworks for Servers tab > Configuration.
Enter a console prompt.
You can customize the prompt using plain text and variables. The default is:
%SERVER_DN% - ZfS>
You can use any of the predefined or user-defined variables (for more information, see Types of Variables).
Enter a working path.
This is for Policy and Distribution Services temporary and backup files. The default directory is ZENWORKS\PDS\SMANAGER\WORKING.
To determine how old database information should be before purging, enter the number of days.
All Policy and Distribution Services information older than the number of days entered will be purged when ZfS is started on the same server where ZFSLOG.DB resides.
IMPORTANT: The database can only be purged if ZfS is running on the same server where ZFSLOG.DB is located.
Click OK to close the policy.
If you click Cancel, none of the policy changes on any of the tabs will be saved.
If you want to create custom log files, you can use either the Tiered Electronic Distribution policy (Service Location Package) or the ZENworks Server Management policy (Distributed Server Package):
Tiered Electronic Distribution policy: With this policy, you associate its Service Location Package to an eDirectory container, and all Distributor and Subscriber objects under it can use this policy. The Use Policy check box that is displayed in each of the object's properties allows you to individually select whether that Distributor or Subscriber should use the policy. The check box is disabled by default.
Using this policy, the Distributor Agent and Subscriber Agent log TED information to your custom log file for the selected Distributors and Subscribers.
ZENworks Server Management policy: With this policy, you distribute its Distributed Server Package to the servers where you want the policy enforced.
Using this policy, the Policy/Package Agents for these servers log policy and software package information to your custom log file.
When creating and configuring one of these policies, the Path and Filename field for the log file is blank by default.
For information on how to create and configure these policies, see: