立即与支持人员聊天
与支持团队交流

Active Roles 8.1.3 - Console User Guide

Introduction Getting started User or service account management Group management Computer account management Organizational Unit management Contact management Exchange recipient management

Deprovisioning a user account

Active Roles provides the ability to deprovision rather than delete or only deactivate user accounts. Deprovisioning a user refers to a set of actions that are performed by Active Roles in order to prevent the user from logging in to the network and accessing network resources such as the user mailbox or home folder.

The Deprovision command on a user account updates the account according to the deprovisioning policies. Active Roles comes with a default policy to automate some commonly-used deprovisioning tasks, and allows administrators to configure and apply additional policies.

You can deprovision Active Directory user accounts with the Active Roles Console.

To deprovision a user account

  1. In the Console tree, locate and select the folder that contains the user account you want to deprovision.

  2. In the details pane, right-click the user account, then click Deprovision.

  3. Wait while Active Roles updates the user account.

NOTE: Consider the following when deprovisioning a user account:

  • You can deprovision multiple accounts at a time. Select two or more user accounts, right-click the selection, then click Deprovision.

  • The Deprovision command is also available in the Active Roles Web Interface. When you click the Deprovision command, the operation progress and results are displayed. When the operation is completed, Active Roles displays the operation summary, and allows you to examine operation results in detail.

  • On a deprovisioned user account, you can use the Deprovisioning Results command to view a report that lists the actions taken during the deprovisioning of the account. For each action, the report informs about success or failure of the action. In the event of a failure, the report provides a description of the error situation.

  • If a deprovisioned user account needs to be restored (for example, if a user account has been deprovisioned by mistake), the account can be reset to the state it was in before the deprovisioning occurred. This can be accomplished by using the Undo Deprovisioning command on the deprovisioned account.

Restoring a deprovisioned user account

Active Roles provides the ability to restore deprovisioned user accounts. The purpose of this operation, referred to as the Undo Deprovisioning operation, is to roll back the changes that were made to a user account by the Deprovision operation. When a deprovisioned user account needs to be restored (for example, if a user account has been deprovisioned by mistake), the Undo Deprovisioning operation allows the account to be restored to the state it was in before the changes were made.

You can restore previously deprovisioned Active Directory user accounts with the Active Roles Console.

To restore a deprovisioned user account

  1. In the Console tree, locate and select the folder that contains the user account you want to restore.

  2. In the details pane, right-click the user account, then click Undo Deprovisioning.

  3. In the Password Options dialog, choose the options to apply to the password of the restored account, then click OK.

    For information about each option, open the Password Options dialog, then press F1.

  4. Wait while Active Roles restores the user account.

    When you click the Undo Deprovisioning command, the operation progress and results are displayed. When the operation is completed, Active Roles displays the operation summary, and allows you to examine the operation results in detail. You can view a report that lists the actions taken during the restore operation. For each action, the report informs about success or failure of the action. In the event of a failure, the report provides a description of the error situation.

Managing user certificates

You can use Active Roles to add or remove digital (X.509) certificates from user accounts in Active Directory. By adding a certificate to a user account you make the certificate (including the public key associated with the certificate) available to other Active Directory users and to Active Directory-aware applications and services.

The certificates added to Active Directory user accounts are referred to as published certificates. Published authentication certificates are used by Active Directory domain controllers during certificate-based authentication. Published encryption certificates can be used to enable access to encrypted contents. For instance, in the case of e-mail encryption, the sender retrieves the recipient’s certificate from the Active Directory user account and uses that certificate to encrypt the email message so that the recipient could decrypt the message by using the private key associated with the certificate. A similar process occurs when you want to allow a given user to read an encrypted file. The certificate retrieved from the user account is used to encrypt the file encryption key so that the file encryption key could be obtained by using the private portion of the user’s certificate to decrypt the encrypted key material.

To view or change the list of digital certificates for a particular user account, open the Properties page for that user account in the Active Roles Console or Web Interfaceand go to the Published Certificates tab. From the Published Certificates tab, you can perform the following tasks:

  • View the list of the certificates published for the user account in Active Directory.

  • Examine each of the published certificates in detail.

  • Add a certificate from the local certificate store (available in the Console only).

  • Add a certificate that is saved in a certificate file.

  • Remove a certificate from the user account.

  • Copy a published certificate to a certificate file.

For each of the certificates that are listed on the Published Certificates tab, you can view the following information:

  • The purposes that the certificate is intended for (available in the Console only).

  • The name of the person or company to which the certificate was issued.

  • The name of the certification authority that issued the certificate.

  • The time period for which the certificate is valid.

  • Additional information about the certification authority that issued the certificate, if available.

  • The list of all X.509 fields, extensions, and associated properties found in the certificate.

  • The hierarchy of certification authorities for the certificate (available in the Console only).

To add or remove a certificate for a user account using the Active Roles Console

  1. Open the Properties dialog for the user account and click the Published Certificates tab.

  2. Do the following:

    • Click Add from Store to add a certificate from the local certificate store.

    • Click Add from File to add a certificate that is saved in a certificate file.

    • Select a certificate from the list on the tab and click Remove to remove the certificate.

From the Published Certificates page in the Active Roles Console, you can also view or export any of the certificates listed on that page. Select a certificate from the list, then click View Certificate to examine the certificate in detail or click Copy to File to save a copy of the certificate to a file.

Management of group Management Service Accounts

You can administer group Managed Service Accounts (gMSAs) with Active Roles. gMSA is a domain security principal whose password is managed by Domain Controllers (DCs) and can be retrieved by multiple systems running supported Windows Server operating systems. Having Windows services use gMSA as their login account minimizes the administrative overhead by enabling Windows to handle password management for service accounts. gMSAs provide the same functionality as Managed Service Accounts (MSAs), but extend that functionality over multiple servers.

As you can use a single gMSA on multiple servers, gMSA provides a single identity solution for services running on a server farm. With a service hosted on a server farm, gMSA enables all service instances to use the same logon account (which is a requirement for mutual authentication between the service and the client), while letting Windows change the account password periodically instead of relying on the administrator to perform that task.

For more information about group Managed Service Accounts, see Group Managed Service Accounts Overview.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级