Active Directory
![](https://docs.lithnet.io/~gitbook/image?url=https%3A%2F%2F1984618955-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FAsBzwJDeLC2ny10RHLdI%252Fuploads%252Fgit-blob-65f1183bf9f868147084071d3fdd390e7b0997df%252Fui-page-activedirectory.png%3Falt%3Dmedia&width=768&dpr=4&quality=100&sign=6b300fd7&sv=1)
Schema
A list of forests is shown along with an indication of the deployment status of the Microsoft LAPS schema, and the Lithnet Access Manager schema.
You can use the Deploy Schema...
button to access a script that will deploy the Lithnet Access Manager schema to the selected forest. You'll need to run this script as a member of the Schema Admins group in the forest you need to update.
If you need to deploy the Microsoft LAPS schema, refer to the Microsoft guides on how to complete this process.
Domain Permissions
In order for the Access Manager service to evaluate user permissions, its service account needs to be a member of two built-in groups of each domain. The first is the Windows Authorization Access Group
. This allows the service account to compute the tokenAndUniversalGroups
for a user in the directory. This ensures that the service account can see the user's full group membership.
The second group is the Access Control Assistance Operators
group. This allows Access Manager to ask a domain controller in a trusting forest to perform access checks on its behalf. Membership in this group is not technically required in the domain and forest that the Access Manager Service runs in.
These groups provide read only access to authorization information within the domain.
Last updated