Add Exchange 2010 Server to Domain, Remove Current Exchange 2010 Server
This is probably a stupid question, but I want to be sure. Currently we have a single Exchange 2010 server hosted on a VM in our environment (ESX). The VM that it was housed was created with several configuration errors (4 vcpu's, etc.). Also the internal Exchange is pre SP 1, just having the roll-up packs. When I try and install even SP 1, I get a setup screen that looks like a webpage whose graphics have not loaded. I have opened a Microsoft ticket on it, but we were unable to resolve. My thought here is to kill two birds with one stone and start fresh. I want a new VM and I will install a clean instance of MS Exchange 2010 and then I would like to migrate everyone over from the first Exchange server to the second behind the scenes with no downtime. Is this possible? What issues could I possibly run into here? I was going to install the new Exchange Server installation on a machine that is housing the front end of SharePoint 2010 (database server is seperate) - Anyone think this is a mistake? Will I have to reconfigure everyone's Outlook (majority of users on 2007, several on 2010) after migration? Presuming all of this is possible - what steps do I take to deprecate and remove the faulty Exchange server from my domain evironment? Any pitfalls that anyone here sees that I am missing? Any insight here from others would be greatly appreciated, as I have never added a second Exchange server to a domain environment and am unsure of what to expect. Thank you in advance for your time. Chris
July 12th, 2012 11:25am

Install the OS, load the Exch binaries, move users across http://blogs.technet.com/b/schadinio/archive/2010/07/20/exchange-moving-mailboxes-exchange-2007-vs-exchange-2010.aspx If you haven't got a CAS array configured, I would configure one now, then the new Exch server will join the CAS array. As for the OLK clients, you will have to do a repair I believe to update the profile, dont believe autodiscover will correct itself. Move over any others services like OAB/PF replication/MX records/External DNS records etc to point to the new Exch server. Once all done, use add/remove to remove Exch from old server. I storngly suggest that you dont install Exch with SP, dedicate a server for Exch.Sukh
Free Windows Admin Tool Kit Click here and download it now
July 12th, 2012 12:59pm

If you install Exchange 2010 SP2 with the latest rollup, plus have the CAS array in place then you shouldn't have to touch the clients. http://blogs.technet.com/b/exchange/archive/2012/05/30/rpc-client-access-cross-site-connectivity-changes.aspx As long as both servers are active, then things should move across. Worst case is that when you remove the original server autodiscover will kick in and redirect the users. Mixing Sharepoint and Exchange never ends well in my experience. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.
July 12th, 2012 5:17pm

Hi ChrisLokey Did you try the above links? CheersZi Feng TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
July 16th, 2012 4:14am

Not as of yet, I have been pretty slammed. I very much appreciate Sukh and Simon's answers however, and will be investigating those links in the next week. I also appreciate the feedback as to not mixing Exchange/SP. I had hoped for a different answer, as that means I have to ask for more money, but better forwarned. Is there a way I can mark both as answers?
July 16th, 2012 12:03pm

Hi Yes, you can Mark Sukh and Simon's answers if you want, because they were providing the suggestion to your issue in a correct way CheersZi Feng TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
July 17th, 2012 11:00pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics