We help IT Professionals succeed at work.

move exchange 2010 with AD role on it to new exchange server with excact settings

thisis_it asked
Is there a good detailed guideline to move an Exchange 2010 server that has AD role on it to new hardware (with also Exchange 2010 but without AD) and then migrate all the settings to that new server ? I see I can mailbox moves, but can I also do more "moves" ?

Or any suggestions on how to uninstall AD without losing Exchange ? (not possible I think).

I already saw the following articles;


Watch Question

Most Valuable Expert 2014
"Or any suggestions on how to uninstall AD without losing Exchange ? (not possible I think)."

While technically possible, it is unsupported to do that. It will usually break Exchange.

The fact that you have Exchange on a domain controller makes no difference - it is the same as a regular migration. Most settings are domain wide, so will not need to be configured again. The only things you will have to do are server specific - so that includes Receive Connector configuration, SSL certificate, URLs within Exchange and database configuration.

Your biggest headache will be moving the clients to use the new server. That does not happen automatically if you do not have an RPC CAS Array configured. Even after moving the mailboxes, the clients will continue to use the old server.
If you do not have an RPC CAS Array then you have three options.

1. Remove the old server (and it will have to be completely gone, so Exchange removed, DC removed and then shutdown/wiped) and cross your fingers that Autodiscover works. Believe it or not, but this is what Microsoft expect you to do, but you cannot test it, because Autodiscover requires the old server to be gone. Once it has gone, it will be too late to change things.

2. Configure an RPC CAS Array, then visit every client and repair their Outlook profile so they get the CAS Array address. When you move the mailboxes, move the CAS Array DNS entry to the new server.

3. Don't configure an RPC CAS array, but change the client access server value on the databases to the new server, then touch every client to repair their profile, either before or after the migration to update.

Basically you are either crossing your fingers or touching every client.