I got the following error when I had migrated a customer from a Small Business Server to our local Hosted Exchange.
Outlook on a domain looks to Active Directory to get the auto discover information. If you run the Outlook connectivity tester on the affected computer, you will see that it returns the local SBS server autodiscover settings, even if you have configured Outlook to use an external provider.
The simplest way to fix this if the SBS server is still in used and Exchange is still installed, is to run the following commands:
You may have got the following error when using CU1 or CU2 with Exchange 2013 when the routing plugin for multi tenancy is being used.
2 smtp;532 5.3.2 STOREDRV.Deliver; Missing or bad StoreDriver MDB properties
Now there are a couple of reasons for this, which are well documented.
The first reason is if you have a mailbox that is hidden from the address book. You need to un-hide the mailbox.
Another issue that will cause this that isn’t well documented is if you are using Email Address policies that check certain things like custom attributes or organizational units (OUs). If the user is sitting in the wrong OU, and the address policy specifies they need to be in another OU, you will get this error.
I had an interesting issue. I had an old Windows 2000 SBS server on my clients network. Been there for a long time as they needed to use the legacy application that it runs. Most services were disabled (ISA, Exchange). Problem arose as it had been disconnected from the domain for some time. This proved interesting when I tried to remove it from the domain. We had to do a adprep /forceremoval (undocumented).
Anyway, the next issue arose when the new Exchange 2010 server was being installed. We could not create mailboxes for exiting users. What gives? I thought Exchange was not being used on the old server? Seems it was, at one stage.
Ok, time to remove this.
[PS] C:Windowssystem32>get-mailbox LegacyUser
Name Alias ServerName ProhibitSendQuota —- —– ———- —————– Legacy User LegacyUser OldSBS2000 unlimited
Ok, the user still seems to be there. I managed to find a command which disables the mailbox AND removes the legacy information from Active Directory.
[PS] C:Windowssystem32>disable-mailbox LegacyUser
Confirm Are you sure you want to perform this action? Disabling Mailbox “LegacyUser” will remove the Exchange properties from the Windows user object and mark the mailbox in the database for removal. [Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is “Y”):
If you don’t disable the user, you will get the following error:
[PS] C:Windowssystem32>remove-mailbox LegacyUser
Confirm Are you sure you want to perform this action? Removing the Mailbox “adeleg” will remove the Active Directory user object and mark the mailbox in the database for removal. [Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is “Y”): Active Directory operation failed on LegacySBS2000.domain.local. This error is not retriable. Additional information: Acc ess is denied. Active directory response: 00000005: SecErr: DSID-03151D12, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0 + CategoryInfo : NotSpecified: (0:Int32) [Remove-Mailbox], ADOperationException + FullyQualifiedErrorId : 103F99DF,Microsoft.Exchange.Management.RecipientTasks.RemoveMailbox
Now you can add mailboxes to these users.You can also remove this information from AD using ADSI Edit, but I STRONGLY DO NOT RECOMMEND THIS. It does work however 😉