Novell Home

My Favorites

Close

Please to see your favorites.

Troubleshooting ZENworks Policy Packages not downloading.

(Last modified: 31Mar2004)

This document (10013297) is provided subject to the disclaimer at the end of this document.

goal

Troubleshooting ZENworks Policy Packages not downloading.

fact

Novell ZENworks 1.0

Novell ZENworks 1.1

Novell ZENworks for Desktops 2

Formerly TID 2940854

symptom

A User Policy Package is not being downloaded or applied when a user logs in.

fix

This information document was written to troubleshoot why ZENworks Policy Packages might not be downloading. It will be updated as new causes and solutions are discovered.

TROUBLESHOOTING:
1. Make sure you have created the appropriate type of Policy Package (i.e. if the user is logging in from NT, make sure you have created a WINNT User Policy Package). The Policy Package will only be downloaded if it is of the same type as the operating system.

2. Make sure that you have associated the user to the Policy Package. This can be verified by looking at the Details of the Policy Package within NWADMN32.EXE and clicking on the Associations tab. Make sure that the user you are logging in as is listed here, is a member of a group listed, or exists in a container listed. If you are only using the container to associate the user, make sure to look for potential problems with a Container Policy Package. When in doubt, it is a good idea to associate the user directly (as a troubleshooting step, not as an implementation design).

3. Make sure there is at least 1 policy to download. For the WINNT User Package there are 8 default policies (Dynamic Local User, Help Desk Policy, NT Desktop Preferences, NT User Printer, NT User System Policies, Remote Control Policy, and Workstation Import Policy). For the WIN95 User Package there are 5 default polices (95 Desktop Preferences, 95 User System Policies, Help Desk Policy, Remote Control Policy, and Workstation Import Policy). If no policies are enabled, then there will be no noticeable change to the user/workstation environment to detect.

4.  Make sure that when you installed the client for win95/98, that the workstation manager component was installed.  It is installed by default, so it should automatically be there.  To make sure it has been installed you can go into the control panel/network configuration tab and look for the service called Novell Workstation Manager.

5. Make sure that the workstation has listed the active tree as a "Trusted Tree".  The Workstation Manager component of ZENworks uses the concept of "Trusted Trees" and a 95/NT Workstation will only attempt to search for a ZENworks Policy Package if the tree you are logging into is listed as a Trusted Tree. This feature gives greater administrative flexibility as to what workstations are controlled by ZENworks.

When installing the Novell Client for NT or 95, you will only be prompted for the "Trusted Tree" if you select a Custom Installation. If you select a Typical Installation, it will automatically set the tree you first login to as the "Trusted Tree". The "Trusted Tree" can be viewed on an NT workstation by going to Control Panel/Network/Services/Properties of Novell Workstation Manager. Make sure that the option for "Enable Workstation Manager" is checked and that the "Tree" field has the NDS Tree name spelled correctly. WARNING: The NDS Tree field does not attempt to validate the tree name to make sure it exists. If the Tree name does not exist, then the Client will never search for Policy Packages and there will not be any type of an error at the Client.

The "Trusted Tree" property is not visible through a dialog box when using the Novell Client for Windows 95 version 2.5 (TID2940876 is an enhancement request to provide a dialog box to control the Trusted Tree settings), however you can view the registry key directly. This registry key is the same for Windows NT Client version 4.3. The registry location for the Trusted Tree is :

key:
HKEY_LOCAL_MACHINE\SOFTWARE\NOVELL\Workstation
Manager\Identification

value:
Tree : REG_SZ : Tree_Name   (how it views in Windows NT) Tree "Tree_NAME" (how it views in Windows 95)

6. If the policy that is not downloading is a NT Desktop Preferences or NT User System Policies ZEN policy, then it may be an issue with the NDS object timestamp. The workstation will keep a copy of these Policy timestamps and will only download these policies again if the NDS timestamp is newer than the workstation timestamp. You can force these to download each login regardless of the timestamp by enabling the "Always update workstation during NDS Authentication" checkbox in the NT Desktop Preferences policy. This setting in the NT Desktop Preferences policy will affect the NT User System Policies download as well.
.

ISSUE:
A Workstation Policy Package is not being downloaded or applied when a user logs in.

TROUBLESHOOTING:
1. Make sure a valid NDS Workstation Object has been created and is linked to the workstation being logged-in from. This can be checked by viewing the following values on a workstation:

key:
HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Workstation Manager\Identification

values:
Registered In : REG_SZ : .OU=ZEN.OU=Site.O=Company
Registration Object : REG_SZ : UserName, IPX_Network_Address,
IP_Network_Address, Station_Name, etc...
Workstation Object : REG_SZ :
CN=StationName123456789012.OU=ZEN.OU=Site.O=Company

The Workstation Object is the critical value. It identifies what NDS Workstation Object the workstation is using when it is logged into. All Workstation Policy Packages will need to be associated with this NDS Workstation Object or to a Workstation Group that has this NDS Workstation Object as one of it's members. If a Workstation Policy Package is not associated to the NDS Workstation Object listed in the Workstation Object registry value (or a group it belongs to) then no Workstation Policy Packages will be downloaded and applied.

For detailed steps on how to create the NDS Workstation Object, see TID 2940885

2. Make sure you have created the appropriate type of Policy Package (i.e. if the workstation is Microsoft Windows NT 4.0, make sure you have created a WINNT Workstation Policy Package). The Policy Package will only be downloaded if it is of the same type as the operating system.

3. Make sure that you have associated the NDS Workstation Object to the Policy Package. This can be verified by looking at the Details of the Policy Package within NWADMN32.EXE and clicking on the Associations tab. Make sure that the NDS Workstation Object you are logging in as is listed here, is a member of a Workstation Group listed, or exists in a container listed. If you are only using the container to associate the NDS Workstation Object, make sure to look for potential problems with a Container Policy Package. When in doubt, it is a good idea to associate the NDS Workstation Object directly (as a troubleshooting step, not as an implementation design).

4. Make sure there is at least 1 policy to download. For the WINNT Workstation Package there are 7 default policies (Novell Client Configuration, NT Computer Printer, NT Computer System Policies, NT RAS Configuration, Remote Control Policy, Restrict Login, Workstation Inventory).

For the WIN95 Workstation Package there are 6 default polices (95 Computer Printer, 95 Computer System Policies, Novell Client Configuration, Remote Control Policy, Restrict Login, Workstation Inventory).

If no policies are enabled, then there will be no noticeable change to the user/workstation environment to detect.

5. Make sure that the workstation has listed the active tree as a "Trusted Tree".  The Workstation Manager component of ZENworks uses the concept of "Trusted Trees" and a 95/NT Workstation will only attempt to search for a ZENworks Policy Package if the tree you are logging into is listed as a Trusted Tree. This feature gives greater administrative flexibility as to what workstations are controlled by ZENworks.

When installing the Novell Client for NT or 95, you will only be prompted for the "Trusted Tree" if you select a Custom Installation. If you select a Typical Installation, it will automatically set the tree you first login to as the "Trusted Tree". The "Trusted Tree" can be viewed on an NT workstation by going to Control Panel/Network/Services/Properties of Novell Workstation Manager. Make sure that the option for "Enable Workstation Manager" is checked and that the "Tree" field has the NDS Tree name spelled correctly. WARNING: The NDS Tree field does not attempt to validate the tree name to make sure it exists. If the Tree name does not exist, then the Client will never search for Policy Packages and there will not be any type of an error at the Client.

The "Trusted Tree" property is not visible through a dialog box when using the Novell Client for Windows 95 version 2.5 (TID2940876 is an enhancement request to provide a dialog box to control the Trusted Tree settings), however you can view the registry key directly. This registry key is the same for Windows NT Client version 4.3. The registry location for the Trusted Tree is :

key:
HKEY_LOCAL_MACHINE\SOFTWARE\NOVELL\Workstation Manager\Identification

value:
Tree : REG_SZ : Tree_Name   (how it views in Windows NT)
Tree "Tree_NAME" (how it views in Windows 95)

6. If the policy that is not downloading is a NT Desktop Preferences or NT Computer System Policies ZEN policy, then it may be an issue with the NDS object timestamp. The workstation will keep a copy of these Policy timestamps and will only download these policies again if the NDS timestamp is newer than the workstation timestamp. Unlike the User Policy Package there is not an "Always update workstation during NDS Authentication" setting available in ZENworks 1.0 or 1.01. This feature was implemented in ZENworks 2.0 as part of the Computer Extensible Policy policy and was not rolled back into future versions because of the extensive code changes to support Computer Extensible Policy policies. The setting is a "Force application of policy" checkbox inside an extensible policy (NT Workstation Policy Package/Computer Extensible Policies/User Extensible Policies tab/double-click on Computer Policies/Force application of policy)..

7. See this document to make sure search policies aren't messing things up:
10058051 Understanding search policies for ZENworks for Desktops 2 and 3.

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

  • Document ID:
  • 10013297
  • Solution ID: 4.0.7705216.2251053
  • Creation Date: 28Jul1999
  • Modified Date: 31Mar2004
    • NovellManagement Products

      NetWare

Did this document solve your problem? Provide Feedback