Moving mailboxes between Exchange 2003 servers in same domain

Posted on 2009-03-28
Medium Priority
Last Modified: 2012-05-06
Here goes,

Server1: Exchange - 20 or so mailboxes
Server2: Exchange

Both servers are domain controllers

I am doing the transfer of all malboxes from server 1 to server2 remotely this weekend.

I have just piloted one mailbox from server 1 accross to server 2 - it was successful.

However, my problem is my outlook didnt automatically update the profile, this is a big problem for me obviously doing this remotely.

The way i am testing it, is i have VPN connected, setup outlook, connected to pilot mailbox on server1, exit outlook and vpn, login to server remotely, transfer mailbox from server1 to 2, reconnect VPN, open outlook - just says trying to connect in bottom right hand corner. It seems to connect for a split second and then disconnects.

When it connects and disconnects for the first time, i then go into the mail properties and can see that the server has changed from 1 - 2. however myoutlook is dosconnected. i then try and reconnect it, it fails straight away, i check the mail properties again, and its changed back to server 1???? its mind bogglings

Event log on the new exchange server gets this:

Event ID 1022

Logon Failure on database "First Storage Group\Mailbox Store (SERVER2)" - Windows 2000 account MYCOMPANY\USER; mailbox /o=First Organization/ou=first administrative group/cn=Recipients/cn=USER
Error: 1144

I know im not logging the whole computer onto the domain, but these outlook testing purposes it should matter should it?

how can i troubleshoot why this isnt working easily,

Question by:dazzydawazzy
  • 2
LVL 23

Assisted Solution

by:Stacy Spear
Stacy Spear earned 80 total points
ID: 24011413
I've never done this over VPN, but on the domain, Outlook will switch easily to the new server as long as name resolution is working correctly. Users won't even notice the change usually.
LVL 25

Expert Comment

ID: 24011454
Yeah, I would expect this is a problem with the VPN more than anything else.  VPNs break name resolution really easily.

Accepted Solution

dazzydawazzy earned 0 total points
ID: 24011472
Found the fix, have tested and works, for anyone else who comes accross this on google etc this may be of help, thanks

As per Microsoft:
To resolve this issue, manually rebuild the Recipient Update Service (RUS) so that every user object receives the correct attributes. To rebuild the Recipient Update Services follow these steps:
1. Open Exchange System Manager.
2. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
3. Expand Recipients, and then expand Recipient Update Services.
4. In the right pane is a list of all Recipient Update Services, in this pane right-click each Recipient Update Service, one at a time, and then click Rebuild.

Author Comment

ID: 24011477
Found solution myself and posted for other readers

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

What is the biggest problem in managing an exchange environment today? It is the lack of backups, disaster recovery (DR) plan, testing of the DR plan or believing that it won’t happen to us.
Let us take a look at the scenario, you have a database that is corrupt and you run the ESEUTIL command only to find you are unable to repair it. How do you now get the data back?
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…

624 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question