Chat now with support
Chat with Support

Directory Sync Pro for Active Directory 20.11 - User Guide

Additional Configuration Options

Changing the attribute used for "Created by Dirsync" or "Updated by Dirsync"

By default, the adminDescription attribute is stamped on objects on the Target that are created or updated by Directory Sync Pro for Active Directory with "Created by Dirsync" or "Updated by Dirsync" to define which objects can be safely deleted from the Target. An app setting is available in the config file to allow you to define a different attribute/field for this purpose.

To use an attribute other than adminDescription or $BTAction, define a new DirSyncAttribute setting in the <appSettings> section of the config file. For example, the below setting will use adminDisplayName instead of adminDescription:

Warning: This must be configured before the initial sync.

<appSettings>

<add key="DirSyncAttribute" value="adminDisplayName"/>

</appSettings>

Setting msExchRecipientDisplayType and msExchRecipientTypeDetails Exchange attributes

A configuration option to allow you to set msExchRecipientDisplayType and msExchRecipientTypeDetails Exchange attributes based on the value of a configurable attribute is available. This option is only applied to target objects not created by Directory Sync Pro for Active Directory.

The configuration option must defined in the <appSettings> section of the config file, as shown below. “Value=” should be contain the attribute to be used. (proxyAddresses shown below). If the value of the target attribute is null, msExchRecipientDisplayType and msExchRecipientTypeDetails will be populated. See the list below for the values that will be populated.

<appSettings>

<add key="RecipientType_MailEnabledAttribute" value="proxyAddresses"/>

</appSettings>

Mail Enabled Users in the source:

  • msExchRecipientDisplayType = 6
  • msExchRecipientTypeDetails = 128

Room Mailbox in the source:

  • msExchRecipientDisplayType = 7
  • msExchRecipientTypeDetails = 16

Resource Mailbox in the source:

  • msExchRecipientDisplayType = 8
  • msExchRecipientTypeDetails = 32

Shared Mailbox in the source:

  • msExchRecipientDisplayType = 0
  • msExchRecipientTypeDetails = 4

Allow objects with remote mailboxes to be treated as mailbox-enabled objects

A setting that allows objects with connected O365 remote mailboxes to be treated as mailbox-enabled objects is available. To enable this feature, add the RemoteMailboxAsMailboxEnabled option to the <appSettings> section of the BinaryTree.DirSync.Exchange.exe.config file as displayed below.

<appSettings>

<add key="RemoteMailboxAsMailboxEnabled" value="True"/>

</appSettings>

If this setting is set to any value other than True or if omitted from the file, objects with remote mailboxes will be treated as non-mailbox-enabled. If set to True, objects with remote mailboxes will be treated as mailbox-enabled.

Specify a timeout for password sync

A configuration option in the appSettings section of the config file to specify a timeout for password sync is available. In large environments, it may take longer than the default 300 second timeout to complete the password sync process and may need to be lengthened.

This setting should be added to the BinaryTree.DirSync.Exchange.exe.config file.

<appSettings>

<add key="PasswordSyncTimeoutSeconds" value="300"/>

</appSettings>

Set the value to configure the timeout to a specific number of seconds. If this setting is omitted, or set to an invalid value, the timeout will be set to 300 seconds (5 minutes). To disable the timeout functionality, set to -1 (or any negative value).

Disable the caching of group members

A configuration option can be used in the appSettings section of the config file to disable the caching of group members.

This setting should be added to the BinaryTree.DirSync.Exchange.exe.config file.

<appSettings>

<add key="OptimizeGroupSyncMemoryUsage" value="true"/>

</appSettings>

Valid values are true and false. If this setting is omitted, or set to an invalid value, the value defaults to false. If set to false, group members will be cached during push and pull. If set to true, group members will not be cached during push and pull.

Disable the initialization of the sync report

A configuration option can be used in the appSettings section of the config file to disable the initialization of the sync report. If disabled, a sync report will still be recorded, but it will not be initialized between syncs. The result will be that an object will show data from the last time it was processed by Directory Sync Pro for Active Directory, rather than just the most recent time it was processed. In other words, if an object is inserted during a sync, it will show in the sync report as Inserted. Assuming a second sync does not touch this object, then if the sync report is initialized, a second sync will show this object as No Change, but if the sync report is not initialized, the object will still show as Inserted.

This setting should be added to the BinaryTree.DirSync.Exchange.exe.config file.

<appSettings>

<add key="DisableSyncReportInitialization" value="true"/>

</appSettings>

Valid values are true and false. If this setting is omitted, or set to an invalid value, the value defaults to false. If set to false, the sync report will be initialized. If set to true, the sync report will not be initialized.

Set the maximum number of users and groups synced simultaneously

During pull processing, Directory Sync Pro for Active Directory will sync multiple Active Directory user and group objects simultaneously into the target AD. The maximum number of users and groups synced simultaneously can be changed using the ThreadCount setting in the config file. If this configuration option is not specified, the ThreadCount will be set to the same number of logical processor cores of the server on which Directory Sync Pro for Active Directory is running.

The configuration option is not included by default. To add, modify the BinaryTree.DirSync.Exchange.exe.config file located at C:\Program Files\Binary Tree\DirSync and add a new key to the <appSettings> section as follows:

<appSettings>

<add key="ThreadCount" value="4"/>

</appSettings>

This option should never be set to a number greater than the number of processor cores on the server. However, you may need to specify a lower number if other applications also running on the server require a specific number of cores set aside for processing. Best practice is to leave the setting at the default value and lower it only if additional processing power is needed for other applications on the server.

Multiple passes will be needed to make sure all data is synchronized to the target when multi-threading is used. An example scenario is:

  • User B is the Manager of User A.
  • User A is synchronized first.
  • Then, User B is synchronized.
  • Another sync is needed for User B to be the Manager on User A.

Passwords are copied if a prior sync failed

A configuration option can be used in the appSettings section of the config file to ensure passwords are copied even if a prior sync failed.

This setting should be added to the BinaryTree.DirSync.Exchange.exe.config file.

<appSettings>

<add key="RepushAllPasswords" value="true"/>

</appSettings>

Valid values are true and false. If set to true, Directory Sync Pro for Active Directory will process passwords for all users during the push. Any users with changed passwords will be processed on the pull. Using this option will increase the sync time, but ensure that all passwords are made current. If set to false or the setting is omitted, this option is disabled.

Set the number of objects selected when the user selects all (Ctrl+A)

A configuration option can be added to control how many objects are selected when the user selects all (Ctrl+A):

<appSettings>

<add key="SelectAllLimit" value="1000"/>

</appSettings>

If this configuration option is omitted, the default value is 1000. Setting this option to a high number may cause performance issues when selecting and marking objects.

Setting select all limit when marking objects as Ready to Sync

Selecting objects to mark as Ready to Sync can be done from the Objects tab within the Sync Report, which contains all object types.

A configuration option can be used in the appSettings section of the config file to control how many objects are selected when the user selects all (Ctrl+A):

This setting should be added to the BinaryTree.DirSync.Exchange.exe.config file.

<appSettings>

<add key="SelectAllLimit" value="1000"/>

</appSettings>

If this configuration option is omitted, the default value is 1000. Setting this to a high number may cause performance issues when selecting and marking objects.

This option does not apply to Windows Server Migration profiles.

Set the attribute used for the linking function

A configuration option can be added to change the attribute used for the linking functionality.

This setting should be added to the BinaryTree.DirSync.Exchange.exe.config file.

<appSettings>

<add key="LinkedIDAttribute" value="adminDisplayName"/>

</appSettings>

If this configuration option is omitted, adminDisplayName is used.

Set the delay period before running a post sync PowerShell script

A configuration option can be added to change the delay length prior to running the post sync PowerShell script. By default, the delay is 300 seconds (5 minutes).

This setting should be added to the BinaryTree.DirSync.Exchange.exe.config file.

<appSettings>

<add key="PostScriptDelaySeconds" value="300"/>

</appSettings>

Using the User, Group, and Device LDAP filters

Active Directory provides a powerful way of retrieving data through the use LDAP filters. Directory Synchronization exposes three filters during the creation of a synchronization profile: User OU Filter, Group OU Filter, and Device OU Filter whose defaults are:

  • Users: (&(!(adminDescription=Created By DirSync))(|(objectClass=Person)(objectClass=room))(!(objectClass=computer)))
  • Groups: (&(!(adminDescription=Created By DirSync))(objectClass=Group))
  • Devices: (&(!(adminDescription=Created By DirSync))(objectClass=computer)(!(primaryGroupID=516)))

These filters are per organizational unit and apply to sub-OUs when the Sync Sub-OUs option is selected.

Modifying these filters requires a basic understanding of the attributes, their value representations, and their data types. LDAP filters support any number of options including filtering by date ranges, wildcards, and the use of bitmasks as in the userAccountControl property.

The use of the objectClass and objectCategory properties can greatly reduce the number of records retrieved resulting in improved performance. You may use other attributes to further restrict your results.

The following are common examples of queries and their LDAP query syntax.

  • Selecting users that are part of the ‘Accounting’ department:
    • (&(objectClass=User)(objectCategory=Person)(department=Accounting))
  • Selecting mailbox-enabled users:
    • (&(objectClass=User)(objectCategory=Person)(homeMDB=*))
  • Selecting mail-enabled users and contacts:
    • (|(&(objectClass=User)(objectCategory=Person)(!homeMDB=*))(objectClass=Contact))
  • Selecting users created after January 1, 2011:
    • (&(objectClass=User)(objectCategory=Person)(whenCreated>=20110101000000.0Z))
  • Selecting distribution lists:
    • (&(objectClass=Group)(groupType=2))

Binary Tree recommends that you use the Active Directory Users and Computers management console to test your filters to prevent Directory Synchronization from failing due to an invalid filter.

Using the User and Group LDAP Filters

Active Directory provides a powerful way of retrieving data through the use LDAP filters. Directory Synchronization exposes two filters during the creation of a synchronization profile: User OU Filter and Group OU Filter whose defaults are:

  • Users: (&(!(adminDescription=Created By DirSync))(|(objectClass=Person)(objectClass=room))(!(objectClass=computer)))
  • Groups: (&(!(adminDescription=Created By DirSync))(objectClass=Group))

These filters are per organizational unit and apply to sub-OUs when the Sync Sub-OUs option is selected.

Modifying these filters requires a basic understanding of the attributes, their value representations, and their data types. LDAP filters support any number of options including filtering by date ranges, wildcards, and the use of bitmasks as in the userAccountControl property.

The use of the objectClass and objectCategory properties can greatly reduce the number of records retrieved resulting in improved performance. You may use other attributes to further restrict your results.

  • Selecting users that are part of the ‘Accounting’ department:
    • (&(objectClass=User)(objectCategory=Person)(department=Accounting))
  • Selecting mailbox-enabled users:
    • (&(objectClass=User)(objectCategory=Person)(homeMDB=*))
  • Selecting mail-enabled users and contacts:
    • (|(&(objectClass=User)(objectCategory=Person)(!homeMDB=*))(objectClass=Contact))
  • Selecting users created after January 1, 2011:
    • (&(objectClass=User)(objectCategory=Person)(whenCreated>=20110101000000.0Z))
  • Selecting distribution lists:
    • (&(objectClass=Group)(groupType=2))

The following are common examples of queries and their LDAP query syntax.

Binary Tree recommends that you use the Active Directory Users and Computers management console to test your filters to prevent Directory Synchronization from failing due to an invalid filter.

Default Mappings

AD Source – AD Target Default Mapping

The below table displays the default values of the AD Source to AD Target mapping table.

Source Field Internal Field Target Field Source Type Target Type 1 Target Type 2 Comments
accountExpires AccountExpires accountExpires any any    
altRecipient ForwardingAddress altRecipient any any    
assistant Assistant   any any    
authOrig AuthOrig authOrig any any    
C CountryAbbreviation C any any    
cn CommonName cn any any    
Co CountryName Co any any    
codePage CodePage codePage any any    
Comment Comment Comment any any    
company Company company any any    
countryCode CountryCode countryCode any any    
deletedItemFlags DeletedItemFlags deletedItemFlags any any    
delivContLength DelivContLength delivContLength any any    
department Department department any any    
departmentNumber DepartmentNumber departmentNumber any any    
description Description description any any    
displayName DisplayName displayName any any    
division Division division any any    
dLMemSubmitPerms DLMemSubmitPerms dLMemSubmitPerms any any    
dLMemRejectPerms DLMemRejectPerms dLMemRejectPerms any any    
employeeID EmployeeID employeeID any any    
employeeNumber EmployeeNumber employeeNumber any any    
employeeType EmployeeType employeeType any any    
expirationTime ExpirationTime expirationTime any any    
extensionAttribute1 Extension1 extensionAttribute1 any any   These are Exchange defined custom attributes.
extensionAttribute10 Extension10 extensionAttribute10 any any   These are Exchange defined custom attributes.
extensionAttribute11 Extension11 extensionAttribute11 any any   These are Exchange defined custom attributes.
extensionAttribute12 Extension12 extensionAttribute12 any any   These are Exchange defined custom attributes.
extensionAttribute13 Extension13 extensionAttribute13 any any   These are Exchange defined custom attributes.
extensionAttribute14 Extension14 extensionAttribute14 any any   These are Exchange defined custom attributes.
extensionAttribute15 Extension15 extensionAttribute15 any any   These are Exchange defined custom attributes.
extensionAttribute2 Extension2 extensionAttribute2 any any   These are Exchange defined custom attributes.
extensionAttribute3 Extension3 extensionAttribute3 any any   These are Exchange defined custom attributes.
extensionAttribute4 Extension4 extensionAttribute4 any any   These are Exchange defined custom attributes.
extensionAttribute5 Extension5 extensionAttribute5 any any   These are Exchange defined custom attributes.
extensionAttribute6 Extension6 extensionAttribute6 any any   These are Exchange defined custom attributes.
extensionAttribute7 Extension7 extensionAttribute7 any any   These are Exchange defined custom attributes.
extensionAttribute8 Extension8 extensionAttribute8 any any   These are Exchange defined custom attributes.
extensionAttribute9 Extension9 extensionAttribute9 any any   These are Exchange defined custom attributes.

facsimileTelephoneNumber

OfficeFAXNumber

facsimileTelephoneNumber

any

any

 

 

generationQualifier

Suffix

generationQualifier

any

any

 

 

givenName

FirstName

givenName

any

any

 

 

homePhone

HomePhoneNumber

homePhone

any

any

 

 

HomePostalAddress

HomePostalAddress

HomePostalAddress

any

any

 

 

Info

Info

Info

any

any

 

 

initials

Initials

initials

any

any

 

 

internationalISDNNumber

InternationalISDNNumber

internationalISDNNumber

any

any

 

 

internetEncoding

internetEncoding

internetEncoding

any

any

 

 

ipPhone

IPPhone

ipPhone

any

any

 

 

jpegPhoto

JPEGPhoto

jpegPhoto

any

any

 

 

l

OfficeCity

l

any

any

 

 

language

Language

language

any

any

 

 

legacyExchangeDN

LegacyExchangeDN

legacyExchangeDN

any

any

 

Created using the source object's GUID as the CN.

localeID

LocaleID

localeID

any

any

 

 

mail

InternetAddress

mail

any

any

 

 

mailNickname

PrimaryAlias

mailNickname

any

any

 

 

manager

Manager

 

any

any

 

 

mAPIRecipient

MAPIRecipient

mAPIRecipient

any

any

 

 

middleName

MiddleName

middleName

any

any

 

 

mobile

CellPhoneNumber

mobile

any

any

 

 

msDS-PhoneticCompanyName

msDSPhoneticCompanyName

msDS-PhoneticCompanyName

any

any

 

 

msDS-PhoneticDepartment

msDSPhoneticDepartment

msDS-PhoneticDepartment

any

any

 

 

msDS-PhoneticDisplayName

msDSPhoneticDisplayName

msDS-PhoneticDisplayName

any

any

 

 

msDS-PhoneticFirstName

msDSPhoneticFirstName

msDS-PhoneticFirstName

any

any

 

 

msDS-PhoneticLastName

msDSPhoneticLastName

msDS-PhoneticLastName

any

any

 

 

msExchAddressBookFlags

msExchAddressBookFlags

msExchAddressBookFlags

any

any

 

 

msExchALObjectVersion

msExchALObjectVersion

msExchALObjectVersion

any

any

 

 

msExchArchiveGuid

msExchArchiveGuid

msExchArchiveGuid

any

any

 

 

msExchArchivename

msExchArchivename

msExchArchivename

any

any

 

 

msExchAssistantName

msExchAssistantName

msExchAssistantName

any

any

 

 

msExchBlockedSendersHash

msExchBlockedSendersHash

msExchBlockedSendersHash

any

any

 

 

msExchBypassAudit

msExchBypassAudit

msExchBypassAudit

any

any

 

 

msExchELCExpirySuspensionEnd

msExchELCExpirySuspensionEnd

msExchELCExpirySuspensionEnd

any

any

 

 

msExchELCExpirySuspensionStart

msExchELCExpirySuspensionStart

msExchELCExpirySuspensionStart

any

any

 

 

msExchELCMailboxFlags

msExchELCMailboxFlags

msExchELCMailboxFlags

any

any

 

 

msExchExternalOOFOptions

msExchExternalOOFOptions

msExchExternalOOFOptions

any

any

 

 

msExchHideFromAddressLists

msExchHideFromAddressLists

msExchHideFromAddressLists

any

any

 

 

msExchMailboxAuditEnable

msExchMailboxAuditEnable

msExchMailboxAuditEnable

any

any

 

 

msExchMailboxAuditLogAgeLimit

msExchMailboxAuditLogAgeLimit

msExchMailboxAuditLogAgeLimit

any

any

 

 

msExchMailboxGuid

msExchMailboxGUID

msExchMailboxGuid

any

any

 

 

msExchMDBRulesQuota

msExchMDBRulesQuota

msExchMDBRulesQuota

any

any

 

 

msExchMessageHygieneFlags

msExchMessageHygieneFlags

msExchMessageHygieneFlags

any

any

 

 

msExchMessageHygieneSCLDeleteThreshold

msExchMessageHygieneSCLDeleteThreshold

msExchMessageHygieneSCLDeleteThreshold

any

any

 

 

msExchMessageHygieneSCLJunkThreshold

msExchMessageHygieneSCLJunkThreshold

msExchMessageHygieneSCLJunkThreshold

any

any

 

 

msExchMessageHygieneSCLQuarantineThreshold

msExchMessageHygieneSCLQuarantineThreshold

msExchMessageHygieneSCLQuarantineThreshold

any

any

 

 

msExchMessageHygieneSCLRejectThreshold

msExchMessageHygieneSCLRejectThreshold

msExchMessageHygieneSCLRejectThreshold

any

any

 

 

msExchModerationFlags

msExchModerationFlags

msExchModerationFlags

any

any

 

 

msExchPoliciesExcluded

msExchPoliciesExcluded

msExchPoliciesExcluded

any

any

 

 

msExchPoliciesIncluded

msExchPoliciesIncluded

msExchPoliciesIncluded

any

any

 

 

msExchProvisioningFlags

msExchProvisioningFlags

msExchProvisioningFlags

any

any

 

 

msExchRecipientDisplayType

msExchRecipientDisplayType

msExchRecipientDisplayType

any

any

 

This mapping is ignored and msExchRecipientDisplayType is set to 6 when the profile is set to sync users as Mail-Enabled Users or Disabled Mail-Enabled Users, or the profile is set to sync users “As-Is” and the object in the source is Mailbox-Enabled.

msExchRecipientTypeDetails

msExchRecipientTypeDetails

msExchRecipientTypeDetails

any

any

 

This mapping is ignored and msExchRecipientTypeDetails is set to 128 when the profile is set to sync users as Mail-Enabled Users or Disabled Mail-Enabled Users, or the profile is set to sync users “As-Is” and the object in the source is Mailbox-Enabled.

msExchRequireAuthToSendTo

msExchRequireAuthToSendTo

msExchRequireAuthToSendTo

any

any

 

 

msExchResourceCapacity

msExchResourceCapacity

msExchResourceCapacity

any

any

 

 

msExchResourceDisplay

msExchResourceDisplay

msExchResourceDisplay

any

any

 

 

msExchResourceMetaData

msExchResourceMetaData

msExchResourceMetaData

any

any

 

 

msExchResourceSearchProperties

msExchResourceSearchProperties

msExchResourceSearchProperties

any

any

 

 

msExchSafeRecipientsHash

msExchSafeRecipientsHash

msExchSafeRecipientsHash

any

any

 

 

msExchSafeSendersHash

msExchSafeSendersHash

msExchSafeSendersHash

any

any

 

 

msExchTransportRecipientSettingsFlags

msExchTransportRecipientSettingsFlags

msExchTransportRecipientSettingsFlags

any

any

 

 

msExchUMDtmfMap

msExchUMDtmfMap

msExchUMDtmfMap

any

any

 

 

msExchUMSpokenName

msExchUMSpokenName

msExchUMSpokenName

any

any

 

 

msExchUserCulture

msExchUserCulture

msExchUserCulture

any

any

 

 

msExchVersion

msExchVersion

msExchVersion

any

any

 

 

name

Name

name

any

any

 

 

O

O

O

any

any

 

 

objectGUID AdminDisplayName adminDisplayName any any    

otherFacsimileTelephoneNumber

OtherFacsimileTelephoneNumber

otherFacsimileTelephoneNumber

any

any

 

 

otherHomePhone

OtherHomePhone

otherHomePhone

any

any

 

 

otherIpPhone

OtherIpPhone

otherIpPhone

any

any

 

 

otherMobile

OtherMobile

otherMobile

any

any

 

 

otherPager

OtherPager

otherPager

any

any

 

 

otherTelephone

OtherTelephone

otherTelephone

any

any

 

 

pager

PagerNumber

pager

any

any

 

 

personalPager

PersonalPager

personalPager

any

any

 

 

personalTitle

PersonalTitle

personalTitle

any

any

 

 

Photo

Photo

Photo

any

any

 

 

physicalDeliveryOfficeName

Location

physicalDeliveryOfficeName

any

any

 

Important, particularly for printers.

pOPCharacterSet

POPCharacterSet

pOPCharacterSet

any

any

 

 

pOPContentFormat

POPContentFormat

pOPContentFormat

any

any

 

 

postalAddress

PostalAddress

postalAddress

any

any

 

 

postalCode

OfficeZip

postalCode

any

any

 

 

postOfficeBox

PostOfficeBox

postOfficeBox

any

any

 

 

preferredDeliveryMethod

PreferredDeliveryMethod

preferredDeliveryMethod

any

any

 

 

primaryInternationalISDNNumber

PrimaryInternationalISDNNumber

primaryInternationalISDNNumber

any

any

 

 

primaryTelexNumber

PrimaryTelexNumber

primaryTelexNumber

any

any

 

 

proxyAddresses

ProxyAddresses

 

any

any

 

ProxyAddresses contains the InternetAddress as the primary SMTP, the legacyExchangeDN of both the source and target as X500 addresses, and any email policies from the target (if enabled).

pwdLastSet PwdLastSet          

roomNumber

RoomNumber

roomNumber

any

any

 

 

sAMAccountName

SAMAccountName

sAMAccountName

any

any

 

The following restricted chars will be replaced with underscores:

, + " < > ; = / [ ] : | * ? \

showInAdvancedViewOnly

ShowInAdvancedViewOnly

showInAdvancedViewOnly

any

any

 

 

sn

LastName

sn

any

any

 

Sometimes used as surname.

st

OfficeState

st

any

any

 

 

street

Street

street

any

any

 

 

streetAddress

OfficeStreetAddress

streetAddress

any

any

 

 

  TargetAddress targetAddress any any    

telephoneAssistant

TelephoneAssistant

telephoneAssistant

any

any

 

 

telephoneNumber

OfficePhoneNumber

telephoneNumber

any

any

 

 

terminalServer

TerminalServer

terminalServer

any

any

 

 

textEncodedORAddress

TextEncodedORAddress

textEncodedORAddress

any

any

 

 

thumbnailLogo

ThumbnailLogo

thumbnailLogo

any

any

 

 

thumbnailPhoto *

ThumbnailPhoto *

thumbnailPhoto *

any

any

 

 

title

JobTitle

title

any

any

 

 

unauthOrig UnauthOrig unauthOrig any any    

url

WebSite

url

any

any

 

 

userCert

UserCert

userCert

any

any

 

 

userCertificate

UserCertificate

userCertificate

any

any

 

 

userPrincipalName

UserPrincipalName

userPrincipalName

any

any

 

 

userSMIMECertificate

UserSMIMECertificate

userSMIMECertificate

any

any

 

 

wWWHomePage

WWWHomePage

wWWHomePage

any

any

 

 

managedBy

ManagedBy

 

group

group

contact

 

groupType

GroupType

groupType

group

group

 

 

* thumbnailPhoto values are synced directly from the Source to the Target.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating