I am trying to install Exchange 2013 in my domain. If I create a Server 2012 and try to install a fresh Exchange 2013 I get prereq errors saying that all Exchange 2010 servers must have SP3 installed. Clearly SP3 seems to not be available until mid-2013. My Exchange 2010 server is at SP2 Rollup 4. So I try to upgrade the Exchange 2010 machine to Exchange 2013. When I open the Exchange 2013 DVD and try to run setup.exe I get a CMD prompt window to quickly open and then close. Nothing happens. No obvious errors or messages. It seems very starnge that MS would release a product that could not co-exist with it's predesessor or be able to upgrade it. Is Exchange 2013 only meant to be installed in new installations? Tell me it ain't so. Thanks, Doug Doug

You will need to wait for SP3 (scheduled for first half of next year): http://blogs.technet.com/b/exchange/archive/2012/09/25/announcing-exchange-2010-service-pack-3.aspxAlexei

So the only way to install Exchange 2013 is to remove the current version of Exchange and then install Exchange 2013 as a new install? Or will that even work? Ptrobly something left in the AD to preclude that approach. Maybe just create a new domain? You can't co-exist with any version. You can't upgrade an installed system. This seems unbelievable. Doug Doug

See also "Supported Coexistence Scenarios" in the following article. http://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspxTony www.activedir.org blog:www.open-a-socket.com

So the only way to install Exchange 2013 is to remove the current version of Exchange and then install Exchange 2013 as a new install? Or will that even work? Ptrobly something left in the AD to preclude that approach. Maybe just create a new domain? You can't co-exist with any version. You can't upgrade an installed system. This seems unbelievable. Doug Doug Yes, it is disappointing. An in-place upgrade wasn't possible from 2007 to 2010, so I strongly doubt whether 2010 to 2013 will be possible.Alexei

Hi If you remove (uninstall) all 2010 servers from your domain then you will be able to install 2013. I did this in my lab as an experiment. It seems that Exchange 2013 came out in quite a hurry for reasons that I haven't discovered yet so the fact that the 2010 coexistence service pack isn't ready yet doesn't surprise me. Cheers, Steve

Doug, as for the CMD prompt opening and closing, I ran into that. You need .NET 4.5. Open a cmd prompt, and run setup from the command line. It will give you the URL to what you need. Chad

So the only way to install Exchange 2013 is to remove the current version of Exchange and then install Exchange 2013 as a new install? Or will that even work? Ptrobly something left in the AD to preclude that approach. Maybe just create a new domain? You can't co-exist with any version. You can't upgrade an installed system. This seems unbelievable. The suggestion to remove Exchange 2010 was done to offer a way to install Exchange 2013 in your lab, that's not the regular upgrade path. Unfortunately your right about the coexistence, currently Exchange 2013 cannot be installed in a forest with an older version of Exchange installed. As soon as SP3 for Exchange 2010 comes available you can deploy the Exchange 2013 side by side with the Exchange 2010 SP3 server and move your mailboxes. An in-place upgrade was available until Exchange 2003, not for newer verions of Exchange.Did my post help? Please use "Vote As Helpful", "Mark as answer" or "Propose as answer". Thank you!

Do let us know when you find out what this is all about. What information are you looking for?Did my post help? Please use "Vote As Helpful", "Mark as answer" or "Propose as answer". Thank you!

Well : why does RU 4 mess up so consistently with .NET 4 and WMI3 which have been around for a while? Why did RU5 get released then removed? Why can't some basic prerequisite checking be included - or at least some warnings in the release notes, along perhaps with some powershell to clean up before trying to install these RUs. I think Exchange is a great product, but these last few RUs make me wonder what is going on - is information not getting passed from the Windows team to the Exchange one? CarolChi

Well : why does RU 4 mess up so consistently with .NET 4 and WMI3 which have been around for a while? Why did RU5 get released then removed? I fully agree with your QA concerns but fail to see how this relates to the subject of this discussion. You need Exchange 2010 SP3 on all Exchange 2010 servers before you can introduce Exchange 2013 in the environment. And SP3 will be released in the first half of 2013. This has nothing to do with UR4 or the bug in UR5.Did my post help? Please use "Vote As Helpful", "Mark as answer" or "Propose as answer". Thank you!

Do let us know when you find out what this is all about. Some of us are still having trouble with RU4. RU5 has been released but with a "do not install" warning. Rather frustrating having to build a new domain to look at Exchange 2013. BTW does anyone move the inappropriate questions (Exchange 2003 and 2007) to other forums?CarolChi