When running the mail-box enable process with Exchange 2007, it appears to take far too long to complete, fails, or appears as though it is timing out.
When running mailbox enabling we use the following process:
- Find the object
- Open the 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.
- 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.
Attribute replication with Exchange 2007 powershell, can be a slow process.
We use CDOEXM with powershell in 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 cache on the exchange server. This takes no more than 15 minutes to update on the local Exchange computer. During this time the changes are passed over to the Global Catalog then onto Active Directory for replication.
- Confirm that Notes Migrator is pointing at the correct domain and a Global Catalog.
- Confirm that the hub-transport of Exchange 2007 is pointing at GC, preferably, the closest and same GC Notes Migrator is pointing at.
- Confirm directory synchronization with 'netdiag /fix' and dcdiag. Confirm all SRV LDAP records are in existence.
- If running Exchange 2003, change the DC that RUS is pointing to, to be that of a closer GC
- Upgrade to the latest build of Notes Migrator
Please see solution number SOL20675. This solution tells you how to chose which DC/GC you are pointing to.