Migrating Exch 2010 to 2010

I am in a situation of needing to move my current 2010 exchange server to a new server (VM).  I am unable to update the SP or roll-up of my current exchange (details here) so I need to migrate my current server to a fresh install of the same version of exchange.

I am not seeing any articles online on migrating to the same version of Exchange.  I also have a some questions regarding the move:

Does the new exchange install need to match my current servers build number?( Keeping in mind from the link above my current exchange is confused about what SP and RU it has.

Can this be done with new server concurrent to minimize downtime?

Can someone please help with this and provide me with some detailed instructions on the best way to handle this situation?

Thanks!
raymann77Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Scott CSenior EngineerCommented:
It's not really a migration.   Just install your new Exchange 2010 server, create the databases and move your users to the new databases.

The best thing to do is keep your new Exchange server at the same SP/RU level as your current one.  Once things are moved over, decommission the old server by performing an uninstall and then update your new server.  I see that your current Exchange server is confused as to where it is in patch level.  Get it as close as you can and move everybody off as quickly as possible.

http://exchangeserverpro.com/move-mailboxes-exchange-server-2010/

https://www.youtube.com/watch?v=ffbH0Bvdxkk
Seth SimmonsSr. Systems AdministratorCommented:
Does the new exchange install need to match my current servers build number?

in this case, no, but it should be at the latest release (SP3 with update rollup 10)

Microsoft Exchange Server 2010 Service Pack 3 (SP3)
http://www.microsoft.com/en-us/download/details.aspx?id=36768

Update Rollup 10 For Exchange 2010 SP3 (KB3049853)
http://www.microsoft.com/en-us/download/details.aspx?id=47676

Can this be done with new server concurrent to minimize downtime?

yes, the new server can be built while the current one is running

Can someone please help with this and provide me with some detailed instructions on the best way to handle this situation?

have not done this myself, but once your server is built, need to migrate mailboxes and public folders over, change your mail routing (depends on what you have for send connectors, etc.) to use the new server, and check your web services (OWA, outlook anywhere, etc.) to make sure the URLs point to the new server

hopefully this can get you started
oh, and i'm assuming the old server has all of the roles (mailbox, transport, cas)?
raymann77Author Commented:
h, and i'm assuming the old server has all of the roles (mailbox, transport, cas)?
Sorry forgot to mention its a single server scenario with all roles.

It appears I am getting conflicting responses if the  new and old server need to match or closely match SP and RU.  

I failed to mention that the new server is 2012, so it looks like I will need SP3 for exchange to function?

Thanks for the comments guys! This will get me started and I will let you know if I have any questions.
Simon Butler (Sembee)ConsultantCommented:
The new server does not have to match the existing server at all.
It can be a later version of Exchange, a later version of Windows (as long as it is supported).

Windows 2012 does require Exchange 2010 SP3. The service packs are the complete product, so download SP3, plus the latest rollup. Put the rollup in to the Updates directory.

However there are two things to remember. As soon as the server goes live you will need to use it for client access as Exchange can downgrade on CAS but not upgrade (so Exchange 2010 SP3 can access Exchange 2010 SP2 mailboxes, but not the other way round).

The other thing to worry about is how clients connect. Unless you have a CAS Array the clients will NOT move to the new server automatically. You will need to visit each one and repair the profile. If you haven't got a CAS Array in place then create one so that the clients will use that instead.

Simon.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.