Next Topic

Previous Topic

Book Contents

View AD Users

The View AD Users page lists all Active Directory users discovered by LAN Watch when LAN Watch runs on a system hosting Active Directory. Using View AD Users:

  • Agents can be automatically installed on each machine an Active Directory user logs onto.
  • VSA administrators can be created based on Active Directory users.
  • VSA users can be created based on Active Directory users.
  • Contact information can be extracted from Active Directory users and applied to the contact information for machine IDs.

Note: You must select a Detail View to see AD users listed on this page.

Switching From Summary View to Detail View

  1. Select <All Groups> from the Select Machine Group drop-down list in the Machine ID / Group ID filter to display a summary view of all domain controllers discovered by LAN Watch.
  2. Identify the machine groups and subgroups listed in the Discovered By column.
  3. Select one of the machine groups or subgroups in Step 2 above from the Select Machine Group drop-down list to display a details view of domain controllers for that machine group.

Summary View

The summary view of the View AD Users page lists all domain controllers that ran LAN Watch for all machine groups you're authorized to access.

Discovered By

Lists the machine ID.group ID names of domain controllers that have performed a LAN Watch scan.

Users Found

Lists the number of users contained in Active Directory found on a domain controller that ran LAN Watch.

Assigned

Lists the number of Users Found whose contact information has been extracted from the Active Directory and assigned to a machine ID.

Details View

The details view of View AD Users displays a list of Active Directory users on domain controllers that ran LAN Watch within a specified machine group.

Installing Agents on Any Machine an AD User Logs Onto

You can associate an install package with an AD user. This installs an agent package on any machine a user logs onto, unless the agent is already installed. Even if the agent is subsequently removed from a machine, the agent will be re-installed the next time the user logs on. You can specify the agent package installed for each AD user.

Note: See Install Issues and Failures if an agent fails to install.

To associate an install package with an AD user:

  1. Select AD users listed in the Canonical Name column of the paging area.
  2. Select an agent package from the Select an Agent Package drop-down list.
  3. Click Install Agent Policy.
  4. Select an AD user and click Cancel to un-associate an install package with an AD user.

Creating VSA Administrators Based on AD Users

Create VSA administrators based on AD users. Administrators created using this method log onto the VSA using their AD domain, user name, and password. This means administrators only have to maintain credentials in a single location, the Active Directory.

Note: A VSA administrator created based on an AD user cannot use System > Preferences to change their username or password. If there are problems with an Active Directory, System > Set Password still provides you with the ability of changing a VSA administrator's password, even if that VSA administrator is based on an AD user.

To create a new VSA administrator based on an AD user:

  1. Select an AD user from the Canonical Name column in the paging area.
  2. Select an administrator role from the Select Admin Role drop-down list.
  3. Click Create Admin.

You can confirm the creation of the new VSA Administrator using System > Create / Delete Admin Accounts. VSA administrator names based on AD users are formatted as follows: <domainname>|<username>.

Creating VSA Users Based on AD Users

Create VSA users based on an AD users. VSA users created using this method log onto the VSA using their AD domain, user name, and password. This means credentials only have to be maintained in a single location, the Active Directory.

VSA users must be associated with a specific machine ID. Assign a Machine ID to an AD user before creating a VSA user based on the AD user.

Note: If a VSA user is created based on an AD user, the VSA user's username and password cannot be changed within the VSA, only in Active Directory.

To create new VSA user based on an AD user:

  1. Click the unassigned link for an AD user listed in the Canonical Name column of the paging area.
  2. Select a machine ID.group ID account in the popup window. The popup window closes.
  3. Select the checkbox for this same AD user in the left most column.
  4. Click Create User.

You can confirm the creation of the new VSA user using Agent > User Access.

Updating Contact Information for Machine IDs based on AD Users

If a machine ID is assigned to an AD user, then the VSA updates its own contact information for that machine ID with the latest contact information for that user in the Active Directory each time the user logs onto the machine ID. This enables administrators to update contact information once in the Active Directory and know the contact information for machine IDs in the VSA will be updated automatically.

To assign an AD user to a machine ID:

  1. Click the unassigned link for an Active Directory user listed in the Canonical Name column of the paging area.
  2. Select a machine ID.group ID account in the popup window. The popup window closes.

Converting Your VSA Logon to use your Domain Logon

You can convert your own VSA logon to use your domain logon as follows:

  1. Open the System > Preferences page in the VSA.
  2. Enter your  current VSA password in the Old Password field.
  3. Enter you domain and domain logon name, formatted all in lowercase as dom/username, where dom is your domain name and username is your logon name, in the Change Logon Name field.
  4. Enter your domain password in the New Password / Confirm Password fields.

This enables you to logon to the VSA using your domain logon and have your VSA logon name and password managed using Active Directory. At the same time, you can continue to use all your previous VSA share rights, scripts and other administrator settings.