Hello, I am planning the migration from Exch2003 to Exch2010 at a new company I started working for. I walked into the company with them already attempting to migrate to Exch2007. They've already installed (2) 2007 servers into the existing 2003 Org both server only have the Hub Transport and Client Access roles. I would like to remove the 2007 servers and only be left with the 2003 servers. What would be the correct steps to remove the 2007 servers? Should I even bother removing them before migrating to 2010? As far as I can tell the 2007 servers are not doing any routing and of course no mailboxes have been migrated from 2003 to 2007 yet. Thanks, Gene

The only supported method is to remove them using add/remove programs. There is no other supported method for the removal of Exchange 2007 from a domain. Therefore run add/remove programs, follow the wizard. If there is a reason why they will not remove, then it will tell you. One reason will probably be the routing group connector. In EMS on one of the Exchange 2007 servers run get-routinggroupconnector and then use remove-routinggroupconnector to remove the Exchange 2003 to 2007 RGC. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

If Exchange 2007 is already installed then I would take the route of migrating to Exchange 2007 (add mailbox role) from Exchange 2003 first, then after successful removal of Exchange 2003 from Exchange 2007 Org, install Exchange 2010. Link to help you migrate, http://www.msexchange.org/tutorials/Transitioning-Exchange-2000-2003-Exchange-Server-2007-Part1.html You can also run ExBPA to see what issues you currently have but this is going to be your best route to getting to Exchange 2010.MVP Exchange Server

Hi, Agree with Simon. The safe way to remove exchange 2007 is by using "add/remove programs". Before you removing exchange 2007, please first power off it for some days and check if all things are working properly.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Gen Lin-MSFT

Personally, if it were me, i'd install the Mailbox role, upgrade to Exchange 2007 service pack 2 then plan an Exchange 2010 deployment when you get an opportunity, when 2007 SP2 is deployed you will be able to install Exchange 2010 without issue, they work well together. Also with Exchange 2007 SP2 deployed the AD has already been extended to support Exchange 2010 which makes the deployment far less hastle. You are right in that the 2007 servers won't be doing much if 2003 infrastructure already has the hub and transport roles installed. You could have a look at the deployment via powershell to get the topology layout to the CAS services using the following powershell command Get-MailboxDatabase | fl name rpc* Cheers Phil

I have to disagree. Why spend the time deploying a version they don't want? The migration path isn't that much different between 2007 and 2010, so just remove an incomplete Exchange 2007 deployment and move straight to 2010. Less time involved. Moving to 2007 then 2010 gains nothing other than confused users. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Thanks, Simon and all for the replies. The removal sounds simple enough. I had concerns that removing 2007 would somehow adversely affect the 2003 Org but that doesn't seem to be the case. I'd agree too that I'd rather skip 2007 and move straight to 2010. The time invested in trying to move to 2007 I'd rather spend on moving to 2010. Plus I don't trust the existing 2007 boxes anyway they seem kinda flakey already and I didn't do the install. :) Thanks again for the quick responses.

Yes, in reviewing my response it does not make any sense to migrate to Ex2007 then Ex2010. Double the work for no reason since you technically have not moved any mailboxes yet. MVP Exchange Server