Exchange won't create mailboxes for new users
- We have a small 2 server domain and after one of the servers went down (perhaps permanently) I cannot configure new mail accounts. I can create them in AD but when I go to Mailbox Store under Exchange System Manager their mailboxes aren't there. I've tried configuring the accounts using the Mail function in Control Panel, this doesn't work either. All of the pre-existing accounts seem to work.
Any ideas?
Thanks...
Answers
Hi,
As my understanding, the issue could be E-mail address do not stamp to the new created user.Please try to follow the steps below to troubleshoot the issue.
1. Please try to use ADUC which is installed on the Exchange Server to new user with mailbox.
2. Please force DC replica with each other.
3. Please open Exchange system manager and enable the diagnostics logging on “MsexchangeAL” attribute.
4. Please try to manually rebuild “Recipient Update Service” from Exchange System Manger.
5. We then restarted the Microsoft exchange system attendant service.
If the problem persists, then please check the event log and then post the error here.
If there’s no error event there, then please try to download ExBPA(Microsoft Exchange Best Practices Analyzer) and then have a health scan. Please post the result here.
Related information to share with you:Initiating Replication Between Active Directory Direct Replication Partners
http://support.microsoft.com/kb/232072
Microsoft Exchange Best Practices Analyzer v2.8
Regards,
Xiu
- Marked As Answer byJames-LuoMSFT, ModeratorFriday, November 13, 2009 9:14 AM
All Replies
- The mailboxes wont show up in ESM until they are opened or receive a message ( Assuming everything is working and RUS has stamped the account).
- Hi,
As Andy mentioned, unless you open/recivce mail....it wouldn't
Create New Mailbox
Send Mail to it
Open it via Outlook/OWA
Check ESM again !
Nitin Gupta (gupnit) | MVP - Exchange | http://www.nitingupta.in/blogs I sent some emails to the accounts and that didn't work. Also I don't see a way to create new mailboxes in ESM...
Hi,
As my understanding, the issue could be E-mail address do not stamp to the new created user.Please try to follow the steps below to troubleshoot the issue.
1. Please try to use ADUC which is installed on the Exchange Server to new user with mailbox.
2. Please force DC replica with each other.
3. Please open Exchange system manager and enable the diagnostics logging on “MsexchangeAL” attribute.
4. Please try to manually rebuild “Recipient Update Service” from Exchange System Manger.
5. We then restarted the Microsoft exchange system attendant service.
If the problem persists, then please check the event log and then post the error here.
If there’s no error event there, then please try to download ExBPA(Microsoft Exchange Best Practices Analyzer) and then have a health scan. Please post the result here.
Related information to share with you:Initiating Replication Between Active Directory Direct Replication Partners
http://support.microsoft.com/kb/232072
Microsoft Exchange Best Practices Analyzer v2.8
Regards,
Xiu
- Marked As Answer byJames-LuoMSFT, ModeratorFriday, November 13, 2009 9:14 AM
- Thanks for the help, I'll try those steps. I believe since one of the DCs is down, the replication isn't happeneing. From the event log (I've bolded what I think is going on):
This is the replication status for the following directory partition on the local domain controller.
Directory partition:
DC=DomainDnsZones,DC=fod,DC=co-ops
The local domain controller has not recently received replication information from a number of domain controllers. The count of domain controllers is shown, divided into the following intervals.
More than 24 hours:
1
More than a week:
1
More than one month:
1
More than two months:
1
More than a tombstone lifetime:
0
Tombstone lifetime (days):
180
Domain controllers that do not replicate in a timely manner may encounter errors. It may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled.
