Troubleshooting Policy Packages

Another troubleshooting area that you should be familiar with is the policy packages. No formal method exists for troubleshooting the Workstation Policy Package; however, the following are some steps you can take to identify problems and find resolutions.

Review eDirectory Workstation Object

In the case of a Workstation Policy Package, make certain a valid eDirectory Workstation object has been created and is linked to workstations that use the policy package. This can be checked by viewing the values listed in Table 19.1 in the workstation's Registry.

Table 19.1. Identification Key in Workstation's Registry

KEY	VALUES
HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Workstation Manager\Identification	Registered In:REG_SZ:.OU=ZEN.OU=Site.O=Company Registration Object: REG_SZ: UserName, IPX_Network_Address, IP_Network_Address, Station_Name, and so on. Workstation Object:REG_SZ:CN=StationName123456789012.OU=ZEN.OU=Site.O=Company

You are specifically looking for the Workstation object value. It identifies which eDirectory Workstation object the workstation is using when it is logged in. All Workstation Policy Packages need to be associated with this eDirectory Workstation object or to a Workstation Group that has this eDirectory Workstation object as one of its members.

If a Workstation Policy Package is not associated to the eDirectory Workstation object listed in the Workstation object Registry value or a group it belongs to, no Workstation Policy Packages are downloaded and applied. You can also check for effective policies on the effective policies panel of a container object's properties page.

Review Policy Package Type

Make certain that the appropriate type of policy package has been created. For example, if the workstation is running Windows NT/2000, make sure you have created a WINNT Workstation Policy Package.

Review Workstation Object Associations

In the case of a Workstation Policy Package, make certain that eDirectory Workstation objects have an association to the policy package. This can be verified by looking at the details of the policy package within ConsoleOne by clicking on the Associations tab.

Make certain that all the workstations that use the eDirectory Workstation object are listed there, are members of a Workstation group listed, or exist in a container listed.

TIP

Make certain to look for potential problems with a Container Policy Package if you are only using the container to associate the eDirectory Workstation Object. If you are not sure, it is a good idea to associate the eDirectory Workstation object directly (as a troubleshooting step, not as an implementation design).

Enable Policies

Make certain that at least one policy is enabled to download. If no policies are enabled, the user cannot detect any change to the user/workstation environment and might question if it is working properly.

Review Trusted Trees

Make certain that workstations have the active tree listed as a trusted tree. The Workstation Manager component of ZENworks uses the concept of trusted trees, and Windows 95/98 or NT/2000 Workstations attempt to search for a ZENworks policy package only if the tree is listed as a trusted tree. This feature gives greater administrative flexibility as to which workstations are controlled by ZENworks.

You can set the trusted tree by selecting the custom installation of the Novell client for NT/2000 or 95/98. If Typical Installation is selected, it automatically sets the tree that you first log in to as the trusted tree.

To view the trusted tree property on a Windows workstation, view the Registry key directly at the following location:

HKEY_LOCAL_MACHINE\SOFTWARE\NOVELL\Workstation Manger\Identification