We have seen in part 1 of this tutorial the classical approach to single mailbox recovery from backups using Exchange 2010 and how this method can only restore the mailbox content to a new structure and this could be annoying for some.
Analyzing the findings of our first approach we can deduce that the problem lies behind the fact that the new mailbox of user2 has a different GUID than the one in the backup. So, logically, changing the GUID of the new mailbox and setting it to the same as the one in backup should solve the issue right ?
Let's see how we can accomplish this to make the magic happens.
Disclaimer:This article contains steps that tell you how to use ADSIEdit.msc. However, serious problems might occur if you use it incorrectly. Therefore, make sure that you follow these steps carefully and I cannot be held responsible for any damage you might bring do to your system.
I have written a 2 part tutorial at simple-talk.com about Microsoft Exchange 2010 Backup and Restore in which I have covered all steps needed to successfully backup your database as well as different recovery scenarios. This article can be looked at as an extension of the recovery process, part 2, and will cover the case when a single mailbox needs to be recovered from the backup.
I would like to stress first that it is not usually needed to recover a single mailbox from a backup when running Microsoft Exchange 2010 because deleted mailbox can be found in the "Disconnected Mailboxes" under "Recipient Configuration" and can simply be reconnected. However if you are just curious to learn or you are in need to recover a single mailbox for whatever reason keep on reading.
I will assume in this article that you are already familiar with the backup and restore process and that a successful full backup of the database already exists.
I will show you today how to manage, backup and restore you sender safe list on Exchange 2007 and 2010 using exchange management shell cmdlets.
To add a entry
$SafeSenders = (Get-ContentFilterConfig).bypassedSenders $SafeSenders.Add("email@example.com") Set-ContentFilterConfig -BypassedSenders $SafeSenders
To remove an entry
I have received comments about my "Installing your first Exchange 2010 CAS" 3 parts - tutorial that it didn't include any reference to services other than OWA. The reason behind this is simply because other services like ActiveSync, POP3, IMAP4, will work through proxying without the need for any additional configuration other than what has already been covered.
However I have faced a strange issue with Exchange Web Services and coexistence of Exchange 2007 and 2010. Since it is clearly stated on technet that
Clients that use Exchange ActiveSync, Exchange Web Services, POP3, and IMAP4 can't use redirection.
I thought it is safe to assume that EWS traffic will be proxied just like it is the case of ActiveSync, POP3 and IMAP4. My thoughts were further confirmed by the same technet article stating that Proxying supported between Client Access servers in the same Active Directory Site for the Exchange Web Services protocol (check section "Client Access protocols for redirection and proxying"), but obviously my thoughts were wrong!
Doing some tests with requests hitting the Exchange 2010 CAS server & using the famous test exchange connectivity website showed failures for users who's mailboxes are still on Exchange 2007 with the following error, while the test passed for users who's mailboxes are now on Exchange 2010.
The Client Access server version doesn't match the Mailbox server version of the resource that was being accessed. To determine the correct URL to use to access the resource, use Autodiscover with the address of the resource.
So it seems that the only way for EWS to work in a mixed Exchange 2007-2010 environment is that the application itself should support Autodiscover.
This is bad news, it means that my client will need to edit manually the settings for all its Blackberry Internet Service (BIS) users!
At this point I am still unsure if it is a bug but it looks like one, so if someone has more insight about it I would really appreciate the feedback.