After migrating your Exchange server (I’ve seen this in transition to exchange 2007 and 2010) the PublicFolderDatabase for your OfflineAddressBook is still pointing to the old servers public folder store.

When you run the get-OfflineAddressBook | fl command in a exchange management shell on your new server, you get a result like this:

At Server you see the new servername and the PublicFolderDatabase is still pointing to your old server. Public folder replica’s and offline address book generation server are already moved to the new server.

Solution: I found if you do the following steps you can change the PublicFolderDatabase.
First start adsiedit and browse to CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=First Organization, CN=Address Lists Container, CN=Offline Address Lists and open the properties of CN=Default Offline Address List

Look for the siteFolderServer attribute, here you will see the old public folder store. Choose clear and close with ok, now you may close adsiedit.

Now go to the exchange management console, Organization Configuration, Mailbox, Offline Address Book open the properties of the Default Offline Address List and go to the tab distribution.

Uncheck “Outlook version 2 and 3″ at client support and uncheck “Enable public folder distribution”. Make sure “Web-based distribution” is enabled. Choose apply and ok, then right click on Default Offline Address List and choose update. After that go back to properties and distribution and check “Outlook client support version 2 and 3″ and “Enable public folder distibution”. Again choose apply and ok and right click and choose update.

When you go back to the exchange management shell and repeat get-OfflineAddressBook | fl you now will see the public folder store on your new server.

Link: http://blog.ronnypot.nl/?p=212

Tagged with:
 

Accessing Exchange 2010 mailbox move history data

On 2011-05-19, in Exchange 2010, by Mattias Jönsson
0
By default, the Exchange 2010 Mailbox Replication Service (MRS) keeps the last two logs for moves performed on a mailbox.  Each log occupies approximately 300KB and, if desired, you can increase the number of logs that MRS keeps by editing its configuration file (MSExchangeMailboxReplication.exe.config), which is kept in the Exchange binaries folder on CAS servers. Like many of the Exchange configuration files, this is an XML document that you can edit with a text editor (NotePad is just fine).  The setting you want to change is MaxMoveHistoryLength, which can be set to any value between 0 (zero) and 100. (mer…)
Tagged with:
 

Problem:
We get error when we try to move mailboxes from exchange 2007 to exchange 2010.
These mailboxes have been started with new-moverequest with -SuspendWhenReadyToComplete option. When we resume moverequest to migrate the last 5% of the mailbox we get at failed mailboxmove with an errormessage: ”Unable to delete folder”.

Solution:
You can try to remove your current moverequest and make a new moverequest. This time move your mailbox in one hole pieace without -SuspendWhenReadyToComplete option.
This works for me!

Tagged with:
 

Slow mailbox move with Exchange 2010 SP1

On 2011-03-23, in Exchange 2010, by Mattias Jönsson
0

Problem:
If you think moving mailboxes to Exchange 2010 SP1 is slow and taking longer time than in RTM version, here’s why!
In RTM Exchange it was doing 5 parallel moves at a time, but in SP1 Microsoft changed MaxActiveMovesPerTargetMDB from 5 to 2 concurrent moves.

What is changed:
RTM values:

MaxActiveMovesPerSourceMDB: This property indicates the number of mailboxes that can be moved on the source mailbox database at one time. The default value is 5 concurrent moves.
MaxActiveMovesPerTargetMDB: This property indicates the number of mailbox moves that can be moved on the target mailbox database at one time. The default value is 5 concurrent moves.

SP1 values:

MaxActiveMovesPerSourceMDB: This property indicates the number of mailboxes that can be moved on the source mailbox database at one time. The default value is 5 concurrent moves.
MaxActiveMovesPerTargetMDB: This property indicates the number of mailbox moves that can be moved on the target mailbox database at one time. The default value is 2 concurrent moves.

The change in MaxActiveMovesPerTargetMDB in SP1 means that we can only do 2 concurrent connections.

The workaround:
Pull open Notepad. If you have UAC enabled, be sure to Run as Administrator. Browse to the install location of Exchange and open the following file:
C:\Program Files\Microsoft\Exchange Server\V14\Bin\MSExchangeMailboxReplication.exe.config
you can change
MaxActiveMovesPerTargetMDB back to 5 to allow 5 concurrent moves.
Save the file, and restart the Microsoft Exchange Mailbox Replication service and do this configuration change on all your CAS servers.
Review the other settings to make sure they reflect what you’d like to see in your environment, and to ensure you’re not getting throttled on any other setting that may pertain to what you’re trying to accomplish.

These lines control the upper and lower limits for these settings:

MaxActiveMovesPerSourceMDB - 5, 0, 100
MaxActiveMovesPerTargetMDB - 5, 0, 100

Links:
Increasing the number of simultaneous Remote/Local Move Request on Exchange 2010 (http://madoxr.blogspot.com/2010/01/increasing-number-of-simultaneous.html)
Understanding Move Requests (http://technet.microsoft.com/en-us/library/dd298174.aspx)

 

Tagged with: