2.8 Troubleshooting User Sources

This section contains explanation on some of the user source problems.

A user group of a Domain Services for Windows user source does not list the members of the group

Explanation: In ZENworks Control Center, a user group of a Domain Services for Windows (DSfW) user source might not list its members even though users have been added as members of this group.
Possible Cause: Objects such as users and user groups listed within the OESSystemObjects container might not have the objectSid attribute defined.

To determine whether an object has the objectSid attribute defined or not, perform the following steps:

  1. Log in to ConsoleOne.

  2. Right-click the object.

  3. Click Properties.

  4. Click the Other tab.

  5. Select the Show read only option and check if the objectSid attribute exists.

Action: In ConsoleOne, edit the description of such objects to generate the objectSid attribute for the objects.
Possible Cause: ZENworks Control Center throws an unknown host exception when you choose to list the members of the group:

Example:

Root exception is java.net.UnknownHostException: srmdsfw.com

Action: Edit the %WINDIR%\system32\drivers\etc\hosts on the Windows server or the /etc/hostsfile on the Linux server to add the following entry for the unknown host:

ip hostname.com hostname

Example:

ip srmdsfw.com srmdsfw

Logging in to the user source on a ZENworks Server from a managed device might be slow if Trend Micro AntiVirus Plus AntiSpyware is installed on the device

Explanation: During installation of the ZENworks agent on a device, an executable file named NalView.exe, which is configured to run at user login, is added to the Run registry key. This addition enables the bundle icon to be placed on the Start menu, desktop, notification area, and the Quick Launch area of the Windows taskbar.

During the user login, NalView.exe runs on the device, resulting in a delay in the overall login time.

Action: To speed up the login process, do one of the following:

  • Disable NalView.exe at login time:

    NOTE:If you choose to disable Nalview.exe at login time, the bundle icon is not placed on the device Start menu, desktop, notification area, and the Quick Launch area of the Windows taskbar. However, the bundle icon is placed in the application window of the device.

    1. Open the Registry Editor.

    2. Go to HKLM\SOFTWARE\Netware\Nal\1.0\NalView\.

    3. Create a DWORD called Disabled and set its value to 1.

    4. Log in to the device again.

  • Launch NalView.exe after a delay of x seconds from the login time:

    1. Open the Registry Editor.

    2. Go to HKLM\SOFTWARE\Netware\Nal\1.0\NalView\.

    3. Create a DWORD called Delay and set its value to the time (in seconds) by which you want to delay the launch of NalView.exe.

    4. Log in to the device again.

An error occurs after adding an administrator group from Active Directory, when the AD is linked to the AD Root Domain

Explanation: While you configure a User Source, if you use Active Directory as the LDAP server and then add the root domain into the Context field, an error occurs. To resolve this problem, make sure you also add the AD Server to your hosts file.
Action: On a Windows managed device:

  1. Open %SystemRoot%\system32\drivers\etc\hosts in a text editor.

  2. Add the <IP-Address-of-the-AD-Server> <Domain-Name> entry to the file.

    For example, you could add the 164.99.165.51 sussex.nhs.uk entry to C:\WINDOWS\system32\drivers\etc\hosts, where 164.99.165.51 is the IP address of the AD server and sussex.nhs.uk is the domain name.

Action: On a Linux managed device:

  1. Open /etc/hosts in a text editor.

  2. Add the <IP-Address-of-the-AD-Server> <Domain-Name> <Short-Hostname> entry to the above file.

    For example, you could add the 164.99.165.51 sussex.nhs.uk sussex entry to /etc/hosts, where 164.99.165.51 is the IP address of the AD server, sussex.nhs.uk is the domain name, and sussex is the short hostname.