Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

If you have Windows servers with local users and groups, you can add those servers to EmpowerID as managed account stores. This allows you to inventory local users and groups and manage those objects from EmpowerID, providing you with automated role-based access control, delegated permissions administration, and provisioning policy capabilities with a full audit trail of any actions involving those objects. This article demonstrates how to manage local Windows users in EmpowerID.

...

Manage local Windows

...

user accounts

...

  1. On the

...

  1. navbar, expand Identity Administration and click User Accounts.

  2. On the Find Accounts page, select the User Accounts tab and then enter the name of the local Windows machine with the user accounts you want to manage in the Locations search field and then press ENTER.

  3. Select the node for the local Windows machine to filter the user accounts in the grid to those belonging to that computer only.

    Image Added


  4. Search for the user account you want to manage and then click the Logon Name link for that account.

    Image Added



    This directs you to the View One page for the user account. View one pages allow you to view and edit the objects to which they are linked.

    Image Added


  5. To view a list of actions that you can perform against the account, expand

...

  1. the Actions

...

  1.  accordion.

...

  1. To perform an action, click the tile or button for that action. For example, if you want to edit one or more attributes, you click

...

  1. the Edit

...

  1.  button; if you want to create an EmpowerID Person from the account, you click the

...

  1.  Create Person From Account

...

  1.  button; if you want to delete the account you would click the

...

  1.  Delete Account

...

  1.  button, and so on.

...

Info

Each Action corresponds to a specific EmpowerID workflow. The number of actions available in the Actions accordion will vary depending on the Access Levels of the person who is currently logged in. To see a particular Action, the person must have the Initiator Access Level for the workflow that corresponds to the Action.

...