LegacyExchangeDN name is created using the samAccountName of the user account instead of the Alias. (NETIQKB39133)

  • 7739133
  • 02-Feb-2007
  • 19-Jun-2007

Resolution

fact
Directory and Resource Administrator 7.0

fact
Directory and Resource Administrator 7.0 SP1

symptom
LegacyExchangeDN name is created using the samAccountName of the user account instead of the Alias.

symptom
When creating an Exchange 2000 or 2003 mailbox, using Directory and Resource Administrator, the 'LegacyExchangeDN' name of the mailbox is generated using the samAccountName of the user account, instead of the Alias name.  However, if the mailbox is created using Active Directory Users & Computers the 'LegacyExchangeDN' name is created correctly based on the Alias.

cause

Exchange 2000/2003 sets the LegacyExchangeDN (using the Alias name) when the mailbox is created.  If the user does not have the Alias property (actually mailNickname), defined, Exchange will use the samAccountName instead.

When Directory and Resource Administrator (DRA) creates a mailbox, it is creating the mailbox first, then sets the mailbox properties, including the Alias



fix

This is corrected in Directory and Resource Administrator (DRA) 7.5 and later. To resolve this issue upgrade to the latest version of DRA.

You can implement the following workaround if the Alias property in your enviornment is not the same as the samAccountName, then :

  • Download the SetLegacyExchangeDN.vbs script from the DRA Knowledge Depot (requires username and password):


    https://www.netiq.com/support/dra/extended/knowledgedepot/default.asp


  • Create a Trigger in Directory and Resource Administrator on the primary server.

  • Configure the trigger as a pre-task trigger.

  • Associate the trigger with the MailboxCreate, MailboxCopy, UserCopy and UserCreate operations.

Once enabled the triggers will ensure that the LegacyExchangeDN field is generated based on the Alias name field instead of the samAccountName.



Additional Information

Formerly known as NETIQKB39133