Troubleshooting Desktop Management

Desktop management is difficult to troubleshoot because several network components are involved; this includes the server, clients, eDirectory, and the LAN.

The following sections discuss the most common areas to review when you are troubleshooting desktop management issues.

Reduce LAN Traffic

If you find that LAN traffic is unacceptable after you create and associate policy packages with objects, you might need to reduce the LAN traffic. One effective way you can reduce LAN traffic is by limiting how the system searches the tree for associations between policy packages and objects discussed in earlier chapters. Limiting the searches should reduce LAN traffic.

To reduce LAN traffic in this way, use the following steps in ConsoleOne:

  1. Create a Container Policy Package. Right-click it and select Properties from the drop-down menu.

  2. Enable the Search Policy on the Policies tab.

  3. Highlight the Search Policy and click the Properties button.

  4. On the Search Level tab, set the Search For Policies Up To field to Partition, and then choose OK to close the Search Policy properties window. This limits how many directory levels are searched for associations between policy packages and objects.

  5. Select the Associations tab, and associate this Container Policy Package to the container where you want to make the Search Policy effective. Remember that the Search Policy affects all containers below the associated container, because the workstation manager looks for the container package.

Troubleshooting Workstation Import Issues

If an attempt to import a workstation was unsuccessful, you might need to troubleshoot import by using the suggestions covered in the following sections.

NOTE

A workstation does not synchronize with eDirectory until after it has been imported and the Workstation Registration program runs again.


Verify Workstation Setup

The first step in troubleshooting workstation import issues is to verify that the correct client is installed on the workstation. This client can be installed from the ZENworks for Desktops CD, or can be downloaded from Novell's Web site.

Validate the Workstation Import Policy

The next step in troubleshooting workstation import issues is to validate the Workstation Import Policy. First verify that the Workstation Import Policy is enabled for the server in to which the user is logging. Do so following these steps:

  1. From ConsoleOne, right-click the server that the user, not registering their workstation, is logging into and select Properties.

  2. Click the ZENworks, Effective Policies tab.

  3. Select the correct platform for the server that the user is logging into and then click Effective Policies.

  4. There should be a policy package listed for the Workstation Import Policy. If not, you need to create-enable the Workstation Import Policy in a Server Policy Package and associate it to the server.

Check Registry Keys for Workstation Manager

Next check the Registry keys for Workstation Manager to ensure that the workstation is not already imported. Follow these steps:

  1. Launch REGEDIT.EXE (or REGEDT32.EXE for NT/2000/XP).

  2. Browse to the following Registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Workstation Manager\Identification
  3. Workstation registration might be in three states (No WS Import Policy, Registration, or Imported).

    If the workstation is in the No WS Import Policy state, the Registered In, Registration Object, and Workstation Object values will be either NULL or will not exist.

    If the workstation is in the Registration state, the Registered In and Registration Object values will be populated, but the Workstation Object value will not exist.

    If the workstation is in the Imported state, the Registered In, Registration Object, and Workstation Object values will be populated.

NOTE

A good general troubleshooting step for registration is to delete the Registered In, Registration Object, and Workstation Object values. They will be recreated at the next boot up login attempt.


Verify the Trusted Tree for Workstation Manager

Once you have verified the Registry keys, ensure that the Workstation Manager Trusted Tree is set to the correct tree name by using the following steps:

  1. Launch REGEDIT.EXE (or REGEDT32.EXE for NT).

  2. Browse to the following Registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Workstation Manager\Identification
  3. The tree value must exactly match the tree name the user is logging into. ZENworks is enabled for one tree at a time, and this tree name is listed here. If the tree you are logging into does not match this Registry value, all of ZENworks is disabled (including the Workstation Import Policy).

Ensure That the Automatic Workstation Import Is Running

Verify that the Automatic Workstation Import service is running on your server and that an import policy is associated with that server.

Also check to make sure that the workstation is pointing to the import service by having the string "ImportServer=<DNS of the import service server>" or "ImportServer=<IP address of the import service server >" in the following Registry key :

HKEY_LOCAL_MACHINE\Software\Novell\ZENworks\zenwsreg
View the Error Log

When troubleshooting workstation import issues, you can also view the WSREG32.LOG log file at the root of the C: drive. Look for errors and then continue troubleshooting from there.

Re-Register the Workstation

As a final option, you can re-register the workstation by running the register utility from the following location:

C:\Program Files\Novell\ZENworks\zwsreg.exe

Use the unreg option to unregister and no parameters to register. Use /? or -? for additional options.



Novell's ZENworks for Desktops 4. Administrator's Handbook
Novell ZENworks for Desktops 4 Administrators Handbook
ISBN: 0789729857
EAN: 2147483647
Year: 2003
Pages: 198
Authors: Brad Dayley

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net