• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 459
  • Last Modified:

Exchange 2010 to 2010 migration

I have a site in where we've had some serious issue in installing Exchange 2010 SP1 on to the server. We are at the point now where the server is up and running but limping along. Our plan is to install a temporary server, prep it up with Windows 2008 and Exchange 2010 and migrate the existing server (also running Windows 2008 and Exchange 2010) over to the temporary server. Once that is done, we are going to reformat and reinstall.

Are there any hurtles that I should now about before we start this work? I can't find any information on migrating from 2010 to 2010.
0
johnbowden
Asked:
johnbowden
  • 2
  • 2
1 Solution
 
ThorrssonCommented:
I wouldn't think there would be too many issues with the procedure itself, the limping server may introduce some unexpected results though.

Install your second Exchange server
Configure it  and test it (Connectors, etc...make sure mail is flowing through the correct Transport server)
Test and Move Mailboxes
Test some more (make sure that the mail is not routing through the existing transport server etc)
**Properly** remove the bad server from the Exchange Org (Link:http://technet.microsoft.com/en-us/library/ee332361.aspx)


0
 
Rajith EnchiparambilOffice 365 & Exchange ArchitectCommented:
It should be fine.
0
 
johnbowdenAuthor Commented:
ok, I guess I need a document on how to move the email over to the new server. is there a link that someone can provide me?
0
 
johnbowdenAuthor Commented:
I tried to move a few users over to the new server and I received this error. This was the first user that I tried to move to the temp server

Error:
The queue in 'Mailbox Database' database already contains a move request for 'Administrator', while AD reports the mailbox as not being moved. It is possible that someone created this move request recently, while targeting a different domain controller, and AD replication did not yet occur. You can examine this move request by running 'Get-MoveRequestStatistics -MoveRequestQueue 'Mailbox Database' -MailboxGuid 60feff6b-f767-4d86-b319-94bc50c04ca1 -IncludeReport | fl'. If you believe this to be an abandoned move request, you can remove it by running 'Remove-MoveRequest -MoveRequestQueue 'Mailbox Database' -MailboxGuid 60feff6b-f767-4d86-b319-94bc50c04ca1'.
0
 
ThorrssonCommented:
Try a user other than the Administrator account, or run the remove-moverequest provided and try again
Or by this time the move may have finished and you will see the administrator account on the new server
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now