MSM7xx Controllers Configuration Guide v6.4.0

Active directory settings
General
Device name
Specify a name that identifies the controller to Active Directory. The controller uses this name
to connect to the active directory server, just like any standard active directory client does.
Domain NetBIOS name
Specify the NetBIOS domain to which the controller belongs. Generally, the NetBIOS domain
name is the first segment of the Windows domain name. For example: if Windows domain is
rd.mycompany.com, then NetBIOS would be rd.
Windows domain
Specify the Windows domain to which the controller belongs. The controller must be part of
a Windows domain (mydomain.com, for example) to authenticate users that belong to that
domain.
Check Active Directory access with attribute
Enable this option to have the controller only accept users with a specific setting in their account.
• Use Active Directory remote access permission: Use the standard attribute defined in Active
Directory for remote access (MsNPAllowDIalin). If this attribute is set, then the user can be
authenticated via Active Directory.
• Use LDAP attribute: For non-standard implementation of Active Directory, set this according
to the equivalent setting on the Active Directory server.
Join
Before the controller can process user authentication using Active Directory, you must join the
controller with the Active Directory server. Fill in the required parameters and select Join Realm
Now. This is usually a one-time event. (Note: The controller cannot be used with an Active Directory
domain that is configured to support multiple DNS servers balanced by the Round Robin feature.)
Username
Username the controller will use to join Active Directory.
Password
Password the controller will use to join Active Directory.
NOTE: For security reasons, Username and Password are not stored on the controller.
Join Realm Now
Select to join the realm immediately.
Status
Shows the status of the join operation as follows:
• Unknown: System is processing, no status to report. Refresh the page to update the status.
• DNS unavailable: DNS not working, cannot access Active Directory.
• Missing Config: No configuration, so join cannot proceed.
• Never Joined: Administrator never selected Join Realm Now.
• Not joined: Not joined: May be joined with the domain, but the join is not confirmed yet.
Status will change to Joined once confirmed. If the Not Joined status persists, check
connectivity between the controller and Active Directory or re-join.
• Joined: Active Directory reports that controller successfully joined.
370 Authentication services