When running mailbox enabling process for exchange 2007 we use the following process:
- Find the user object
- Open the user object
- Disable the mail enabled user. We do this because you cannot mailbox enable an existing mail-enabled account. This removes all Exchange attributes, such as the legacyexchangedn. Note that if you did not run the merge process, because you had no connector created contacts, this process will fail because we will disable the mail enabled user. Because the user in this scenario will not be mail-enabled, it will fail so you must run the merge process regardless. This will bring over any of the target alias addresses and target address the user has from the source.
- Then we run a test to check the existence of the legacyexchangedn attribute. We do this to confirm it does not exist and that the object is not a mail-enabled object. This process loops until it confirms the deletion, and will wait for Active Directory replication to complete.
- When it is confirmed that the attribute does not exist, then the mailbox is created and enabled.
Sometimes the replication of information can cause issues. For example, when mailbox enabling and migrating. The Attribute replication with Exchange 2007 PowerShell, can be a slow process.
We use CDOEXM with PowerShell for migration processes to perform functions against the Exchange server such as adding or removing attributes from users and mailbox enabling etc. When we make these changes, the attributes are cached by the directory service access (DSAccess), which is the local directory service cached on the Exchange server. This takes no more than 15 minutes to update on the local Exchange Server. During this time the changes are passed over to the Global Catalog then onto Active Directory for replication.
If you are having issue to do the following:
- Confirm that Notes Migrator is pointing preferably to a Global Catalog and that the Global Catalog is the same DC that is specified as the Exchange 2007 configuration domain controller
- Confirm directory synchronization with 'netdiag /fix' and dcdiag. Confirm all SRV LDAP records are in existence.
- If running Exchange 2007, change the DC configuration domain controller, set in Exchange, to be a local, or the DC the application is pointing to
- Upgrade to the latest build. This includes extra switches that can be used to retry and wait in case of replication lags with updates from the Exchnage server and Active Directory. There are two switches that can be added which are brielfy:
These are explained in much more detail within the Parameters Reference Guide.