Incorrect “Mailbox Store” in Active Directory

active-directoryexchange

I recently had to restore our primary domain controller from a backup, but the backup was taken before a mailbox was moved (from mail1 to mail2). The user now has the problem that they cannot access their email. This appears to be because Outlook is looking for the emails on mail1.domain.com, whereas the actual emails are on mail2.domain.com.

In AD, the users "Mailbox Store" attribute is set to "MAIL1/First Storage Group/Mailbox Store (MAIL1)".

In event viewer on MAIl1 (which is also our PDC), the following event is logged :

Event Type: Error
Event Source:   MSExchangeIS Mailbox Store
Event Category: General 
Event ID:   1205
Date:       26/10/2009
Time:       09:30:49
User:       N/A
Computer:   MAIL1
Description:
Failed to create the mailbox of 
/o=DOMAIN/ou=first administrative group/cn=Recipients/cn=<user> with error 0x50c.

How can I tell AD where the mailbox is correctly located?

Best Answer

Fixed the problem with this article.

Related Solutions

Active Directory DNS issue? Event ID 13 Access Denied,

Okay. Got it solved. It was definitely an AD/DNS issue. There were some bad DNS records that were fouling up AD replication and in turn causing authentication issues.

Windows – Active Directory – Dynamically set user attribute based on group membership

The only approach I can think of would be to run a script to periodically scan your Active Directory and update the attribute you're interested in, based on the group membership of the account.

It's relatively easy to do with PowerShell, and you could run it as a scheduled task to keep things current.

The Scripting Guy has a blog entry that's pretty topical - Use the PowerShell AD Provider to modify user attributes. Use that to form the core of your script, slap some logic around it, and you're good to go.

In his example, he's fiddling with the physicaldeliveryofficename attribute, and uses the Set-ItemProperty cmdlet, combined with a Filter to switch the value of that attribute between Charlotte and Raleigh. You would probably not take that approach, but instead just use the Set-ItemProperty cmdlet to set to the attribute your Sonicwall/Dell checks to something, based on what group the user's in.

Set-ItemProperty -Filter "physicaldeliveryofficename=Raleigh" -Path * -Name physicaldeliveryofficename -Value Charlotte

Best Answer

Related Solutions

Active Directory DNS issue? Event ID 13 Access Denied,

Windows – Active Directory – Dynamically set user attribute based on group membership

Related Topic