Target Device Naming Requirements For Ldap Implementation - Dell Remote Console Switch User Manual

<username@domain> or <domain>\<username> or <domain>/<username>
(where username is an ASCII string of 1–256 bytes). No white space and no
special characters (such as \, /, or @) are allowed in either the username or the
domain name.
NOTE: You cannot specify NetBIOS domain names, such as Americas, since
those names cannot be resolved.
NOTE: If a domain name is not included, the local database in the Remote
Console Switch will be used to authenticate the user.
Target Device Naming Requirements for
LDAP Implementation
If you experience the following error:
Login Failure. Reason: Access cannot be granted due to Authentication Server
errors
Please verify that the SIP object was created in the Active Directory and its
name exactly matches the name assigned to that SIP via the OBWI at the
console switch.
The Dell Standard Schema and the Dell Extended Schema use specific object
classes in the Microsoft Windows Active Directory to represent SIPs. The
Microsoft standard naming conventions for these object classes prohibit the use
of special characters or spaces. If you intend to use LDAP in a deployed
environment where target device names in SIPs currently include spaces or
special characters, you will need to rename them without spaces or special
characters.
Renaming a target device in a SIP should be done through the OBWI at the
console switch and then resynchronized through the RCS software. It is
important to note that while the OBWI will allow you to enter spaces into the
names assigned to the SIPs, Active Directory does not. You must name SIP
objects according to the Microsoft Active Directory rules.
LDAP Feature for the RCS
xxx | xxx
151