The following policies come with ZENworks:
Use this to specify which files to download from the network to one or more workstations. The types of files you can manage using this policy are ASCII text (such as .BAT, .INI, or .CFG) or binary (such as .EXE, .COM, or .DLL).
Use this to list printers and drivers available to the Windows* 95/98 or Windows NT* workstations associated with this policy.
Use this to set a collection of settings for a default Windows 95/98 or Windows NT Computer.
This policy contains Control Panel contents with nothing enabled. Use it to set default display preferences and mouse buttons.
Use this to create settings for a default Windows 95/98/NT user.
This policy lets you set a variety of attributes related to the computer system the user is running. Unlike the Computer System Policy, which applies to the individual workstation, the User System Policy follows the user regardless of which workstation is used to access the network.
Policy settings are created to ensure that users cannot log in with full workstation access by simply canceling the login or login bindery. Every user should be associated with a policy. Then, every time the user logs in, the policy is recorded in the workstation registry. These settings are permanent until changed by another policy.
If a user is not associated with a policy, that user inherits the policy of the previous user on the workstation. If a user with a policy logs in to the workstation of a user without a policy, the workstation is set based on the policy associated with the user who is logging in.
For a user to operate without restrictions, a policy that removes all restrictions applied by the previous user must be associated with the user who is to have no restrictions.
Use this to configure the User created on an NT workstation after successfully authenticating to NDS.
You must set a Help Desk Policy in order for your users to be able to use the Help Requester program. This policy requires a current name and telephone number or e-mail address for the support contact. Use this primarily to establish communication rules between users and your Help Desk. You can choose to allow users to send help requests (trouble tickets) to an e-mail address. When they do, the program will automatically supply each help request with the e-mail address and other pertinent information about the user and workstation.
Setting up a Help Desk Policy for your users lets you collect help requests in a consistent manner. It will provide you with pertinent user information, such as user context or network address, with little effort required from the user.
As a network administrator, you create a Help Desk Policy object in NetWare® Administrator. The policy establishes help desk rules, such as whether a Help Request is sent through e-mail. A policy can be associated with a User, a Group, or a Container object.
When users or members of the group or container associated with that policy run the Help Requester on the workstation, they can send a request for help through e-mail. By selecting a problem category to display in the e-mail subject line and then entering a message, they will access support contact information, such as an e-mail address or phone number, and will be able to view information specific to their workstations.
For example, Kim is a network administrator who set a Help Desk Policy for Joe and other users in his group. Kim added three items to the Subject drop-down list: Server problem, Application problem, and Hardware problem. Kim also decided that she wanted the group's help requests to be e-mailed to her, so she placed her e-mail address in the Contact information.
Joe can't access a spreadsheet program, so he contacts the help desk by using these steps:
The next time Kim checks her e-mail she has a message from Joe with "Application" in the subject line. When Kim opens the e-mail, she sees all the pertinent information about the workstation, the user, and the problem.
This policy is a large collection of client configurations settings. The parameters are grouped in the following ways:
This is a placeholder for Dial-Up Networking settings. Use this to list printers and drivers available to the Windows NT users associated with this policy. This policy is the first step in allowing a workstation to be controlled remotely, which can help you resolve workstation problems from your own office. Here you specify whether remote controlling is allowed for workstations associated with the policy package containing this policy. You can specify other settings regarding remote control as well (for example, giving users a visible or audible warning before starting a remote session). The following outlines how you would check the policy settings. The Disable flag for the remote operation is not set on the effective workstation policy for the Workstation object. The Disable flag for the remote operation is not set on the effective user policy for the user logged in to the target workstation. If Prompt User for Permission for the remote operation is checked on the effective workstation policy for the Workstation object, the user logged in to the target workstation must approve the remote operation by clicking OK on the message box that is displayed. If Prompt User for Permission for the remote operation is checked on the effective user policy for the user logged in to the target workstation, that user must approve the remote operation by clicking OK on the message box that is displayed. Remote operations such as Talk and Diagnostics do not support the Prompt User for Permission option. If this option is checked on the effective workstation policy for the workstation object, the user has allowed that an audible signal should be sent to the managed station every time the administrator accesses the target station. If this option is checked on the effective user policy for the user logged in to the target workstation, the user has specified that an audible signal should be sent to the managed station every time the administrator accesses the target station. This option is enabled for remote operations such as remote control and remote view only. If this option is checked on the effective workstation policy for the workstation object, the user has allowed that the visible signal should be sent to the target station every time the administrator accesses the target station. If this option is checked on the effective user policy for the user logged in to the target workstation, the user has specified that an visible signal should be sent to the target station every time the administrator accesses the target station. This option is enabled for remote operations such as remote control and remote view only. If this option is checked on the effective workstation policy for the workstation object, the user has allowed the display of the remote control agent icon. This icon indicates that the remote operation agent is loaded at the target station. If this option is checked on the effective user policy for the user logged in to the target station, the user has allowed the display of the remote control agent icon. This icon indicates that the remote operation agent is loaded at the target station. The remote operation agent icon is enabled for remote operations such as remote control and remote view only. Use this policy to set rules regarding login times and occurrences. A Search policy (which resides in the Container Package) lets you search containers for associated policy packages and effective policies. A Search policy can be associated only with containers. A search policy can also limit how high in the tree ZENworks searches for effective policies. For example, you might want to search only to the root of a partition for performance reasons. Policy package associations flow down a tree, much like the NDS inherited rights. When you choose to view the associated policy packages for an object, the system, by default, starts at the object and searches up the tree for all policy packages associated with the object, associated with any Group that the object belongs to, and associated with any of the object's parent containers up to Root. You can avoid unnecessary LAN traffic by searching to the partition instead of [Root]. The default Search policy will recognize the policy package associated with the User or Workstation object before it will look in any Group or container where the object resides. The default search order, Object > Group > Container > Root, can be reordered and can be limited to one, two, or all three locations. For instance, you can set the search order to Object > Container to not search Groups. A Search policy provides the following three things:
You can create a search policy to modify the default search policy. This limits which objects ZENworks searches. For example, you may not want to use group membership to determine policies. This policy is used to set rules on how Workstation objects are named and where they are created. You must decide if you want to create Workstations in their own containers, or in the container where the user resides, as part of the User Workstation Package. You may find it simpler to manage Workstation objects in a common container if your User objects are in various containers. Or, you may find it easier to keep User and Workstation objects in the same container to minimize the number of policies you must create and associate in order to use all ZENworks features.NT RAS Configuration Policy
NT User Printer Policy
Remote Control Policy
Checking the Policy Settings for Remote Operations
Restrict Login Policy
Search Policy
Workstation Import Policy