Resolution
Directory and Resource Administrator 6.x
fact
Directory and Resource Administrator 7.x
symptom
Directory and Resource Administrator does not default to the first UPN suffix like native tools does when creating a new user.
cause
Directory and Resource Administrator (DRA) always defaults to the default UPN suffix that was defined when the domain was created.
fix
If an additional UPN is defined in Active Directory using Active Directory Domains and Trusts, then Active Directory Users & Computers (AD U&C) makes the first alternative UPN the default UPN suffix when creating new accounts in AD U&C. If you add more than one UPN Suffix, AD U&C defaults to the first additional UPN that was defined. Directory and Resource Administrator always defaults to the UPN suffix defined when the domain was defined. It does not default to any alternative UPN suffixes that have been defined.
In order to change the default UPN suffix in DRA, when a user account is created, the following workaround is available:
- Use a Pre-task trigger to automatically set the UPN suffix to the desired value.
- Clone a user with the desired UPN suffix. DRA will set the UPN suffix to be the same as the template account.
- Customize the Web Console by hard coding the default UPN suffix. For more information on this topic, please refer to the followign Knowledge Base article
How do I configure the default UPN suffix in the Web Console for user create and or clone operations?
https://www.netiq.com/kb/esupport/consumer/esupport.asp?id=NETIQKB30103
An Enhancement Request has been opened with Development to include this functionality in a future version of Directory and Resource Administrator.