Assignment rules determine how servers are synced from Active Directory (AD) and assigned to projects. Rules are applied in the order they’re listed; higher priority rules are listed first. You can drag and drop rules to change their priority.
When a job runs, multiple rules may match a server, but the server is assigned based on the rule with the highest priority.
Assignment rules consist of several parts:
- Base DN: Controls where the rule searches for servers
- LDAP Query: Controls the specific criteria used to filter servers
- Assigned Projects: Specifies a project to associate with matching servers
Common Base DN settings
You can use the Base DN setting to control where the LDAP query searches for devices. By default, the search scope uses the domain information you specified when creating the connection.
|Search the consumer organizational unit within the ocorp.com domain||
|Search the prod organizational unit within the live.ocorp.org domain||
|Search the devops object located in the eng organizational unit within the test.ocorp.edu domain||
Common LDAP queries
You can adjust the LDAP query to locate devices that meet specific criteria. The following examples will likely need to be modified to fit your specific needs. By default, assignment rules include an LDAP query to locate every computer within the search scope.
|Locate every computer||
|Locate every computer running Windows 10||
|Locate every computer running Windows Server 2016 that isn’t a domain controller||
|Locate every computer with RDP in the description||
|Locate every computer with RDP in the description that isn’t running Windows Server 2016||
Any servers that match the rule are assigned to the specified project. You must enable AD support on a project before you can assign it to the rule. See Enable Active Directory support for projects.