If your Sametime
® servers connect to an Active Directory (LDAP) server and you prefer to use the DN attribute rather than the objectGUID attribute for the Sametime
internal user ID, you must assign the DistinguishedName attribute to be the internal ID for Sametime
users. Doing so guarantees that Active Directory returns the DN attribute in the same case-sensitive and space-sensitive format. Forcing Sametime
to use a consistent attribute for the internal user ID prevents awareness problems caused by ambiguous internal user IDs.
About this task
If you choose the DN attribute for the Sametime
internal user ID, but do not assign the DistinguishedName attribute as the internal ID, you may see the following problems:
- Awareness for some users does not work.
- A user's name appears multiple times in the same Contact list.
Note that you can assign the objectGUID attribute as the internal user ID to eliminate the need to run the name change tool in the future.
Parent topic: Specifying a user's login ID
Migrating older user IDs to a unique directory attribute sta852ifr1
- Log in to the Integrated Solutions Console.
- Click Sametime System Console -> Sametime Servers -> Sametime Community Server.
- In the Sametime Community Servers list, click the deployment name of the Sametime Community Server.
- Click the Configuration tab.
- Under LDAP Attributes for The attribute used for determining the internal user ID, enter the value DistinguishedName.
- Click OK.
- Restart the Sametime Community Server so the change can take effect.