Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Exchange 2013 is out, available for some epople already. Got if from the VLC Center, now trying to get an upgrade path that works for some customers.

Problem:

  • There is no upgrade. It is "install on new Server, move mailboxes. This means coexistence with Exchagne 2010 for the time to move the Mailbox.
  • Sadly the only compatible Exchange is Exchange 2010 Sp3 - which is not going to be bout for quite some time.

Any way to still do an update? Backup, restore to new Server? Any beta of the SP that is good enough to ONLY move the mailboxes? I do not care about the rest - this really is "install Exchange 2013, move mailboxes, UNINSTALL 2010".

I am quite - ah - unhappy that at the end the only one who will be able to intall 2013 are new companies right now.

share|improve this question
    
in the past what I've done is install Exchange in a new environment, make sure it has a distinctly different URL to the old exchange box (for OWA, EWS, etc). This is required to maintain compatibility between both systems. In other words, get the Exchange 2013 fully operational, but without mailboxes. Then, in Exhchange 2010 start doing Mailbox move to the new server, one by one (or all at once, whatever). The Outlook clients will be told of the change of server and update all their settings (server, proxy/outlook anywhere etc). –  Mark Henderson Oct 31 '12 at 20:23
4  
@MarkHenderson (see technet.microsoft.com/en-us/library/…) that won't work at this time. MS require a rollup for Ex 2007 and a SP for Ex 2010 to support co-existance between Ex 2013 and anything else in the same forest, and neither patch is available right now. This is affecting me too, as it happens. –  RobM Oct 31 '12 at 20:26
    
Well I guess we're all shit-out-of-luck then. I was planning a lab setup of 2013 in the coming weeks; I might hold off now. –  Mark Henderson Oct 31 '12 at 20:34
    
Yeah. An entire upgrade path seems like a big thing to leave out of a released product, or is that just me? –  RobM Oct 31 '12 at 20:38
3  
The only "path" right now is to export all the mailboxes to PST files, uninstall Exchange 2007/2010, install the new Exchange 2013 and Import the PST files. MS really screwed the early adopters on this one. –  Chris S Oct 31 '12 at 22:44

3 Answers 3

up vote 6 down vote accepted
+25

If there isn't even an officially supported upgrade path out there yet, may it be that Exchange 2013 is a bit... too young to actually deploy it in a production environment?

share|improve this answer
2  
Possibly, but it is released and you can deploy new. Small company here, but even for a dozen mailboxes only - export + import is complex. –  TomTom Nov 6 '12 at 22:44

There is now an official co-existence and migration path.

You need Exchange 2010 SP3 and Exchange 2013 CU1. This will allow for co-existence and migration of mailboxes within the same organization. 2013 CU1 is set to be released on April 2, 2013.

share|improve this answer

It works but it is not supported. I am currently moving more than 2000 mailboxes to Exchange 2013 with mailbox + CAS roles on separate server but coexisting in the same forest/domain.

Mailbox migration works when initiated from the 2013 side. I had a lot of problems to work through to get it working but finally managed it.

i came from ex2007, i guess its the same for 2010 but this is only my estimate.

first update to sp3, a lot of troubles, was a cas array first, one node removed, the sp3 setup didnt work quite well, but i guess you guys manage to update your servers :P

after that, two new servers, 2012 servers. domain function level to 2008 r2, forest level 2003.

now you may start the setup for exchange 2013 after installing UCMA and stuff, setup will NOT give you an error regarding the old exchange in the organization.

now comes the weird part:

in the ex mgmt shell on the new servers, i got some errors when creating new databases, version mismatch etc. If you create the database from the webgui with the assistant, just name it Test, dont mount it, leave it at the default path - it will be created successfully. thereafter, you may rename and relocate the databases.

i also had troubles with public folders migration, didnt work out, i saved everything from the old public folders to a pst and deleted them, the database and everything. had to do it in adsiedit because it wouldnt remove otherways because again of a version mismatch.

then you may configure everything else, autodiscover, connectors and stuff, works flawlessly.

now move offline adressbooks and the mailboxes, thats it. just have to start it from the 2013 web gui, but this is normal behavior.

why i did it, well, first i read in the internets that from ru9, exchange 2013 migration will be supported, this was a wrong info because the update needed is not yet out. i already got most thing up by this time, also hybrid is needed and with exchange 2013 you dont need a dedicated hybrid server.

if you have any further questions, ask.

share|improve this answer
1  
If you are going to make this statement, you might want to explain 1) how you got it working, 2) what troubles you had, 3) fixes to fix said problems. –  Rex Feb 1 '13 at 22:42
2  
and why an unsupported path with 2000 mailboxes? –  chewbakka Feb 1 '13 at 23:11

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.