I know you can't rename an Exchange server and have it work. Our Exchange 2010 is built virtually on a Hyper-V host server. Can I just build another exchange server then move the mail database over to it? What's the process for renaming a server if you can't just do it manually? This is what I'd like to do: Build a new virtual server with the correct naming convention used (which changed since the original deployment).Migrate the databases to the new server.Remove the old server.Renew the certificates (which expired about a week ago) with our service provider and reinstall them on the new server. Can I do something like this? Noel Stanford Oveson jeremyNLSO MCTS, MCITP, CCENT, CNE, MCSE, CLSE Berlin, Germany

Hi, This should help: http://social.technet.microsoft.com/Forums/en-NZ/exchange2010/thread/900d4d08-c81c-4dd8-adf0-14feb3f49aa1 Leif

The biggest problem will be moving the clients. Do you have an RPC CAS Array in place? If not then the clients will not start using the new server automatically. You have two options, both of which should be considered after deploying the RPC CAS array. 1. Touch every client, by doing an Update in the Outlook profile. 2. Remove the first server and then cross your fingers that Autodiscover will redirect the client to the new server address (the RPC CAS Array host). I would try and move the databases to the new server, instead just move the mailboxes using the built in tools. Zero risk, zero downtime. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

I actually want to put a high availability, fault tolerant system in place. I want to build 4 Exch2010 servers--two for the mail databases using DAG, and 2 for the transport & CAS roles and then use built-in NLB. I want to do this with virtual machines under Hyper-V. But before all that, I just want to rename the server to the new naming convention. You're saying I should just install the new server w/the new name, move the mailboxes (not the databases) over, and then remove the old server? Am I understanding that correctly? Thanks... Noel Stanford Oveson jeremyNLSO MCTS, MCITP, CCENT, CNE, MCSE, CLSE Berlin, Germany

Windows Network Load Balancing is no longer recommended for use with Exchange by the product team themselves, which is a good thing because it sucks pretty bad. Otherwise, what I am saying is what you have written, the only issue is that the clients will NOT start using the new server automatically, because they connect to the CAS role, not the mailbox role, and the mailbox databases do not "belong" to any server. They are an org setting. Your biggest headache is going to be getting the clients to use the new platform. Personally the way that I would do it is to install the new CAS/Hub servers first, setup the RPC CAS Array to point to one of the new CAS role holders. Outlook ANywhere, OWA, ActiveSync etc can all be pointed to the new servers once the SSL certificate has been sorted out. Exchange 2010 SP2 with the latest rollup naturally. Then build the new mailbox servers, with the DAG etc in place and test it. Once you are happy then start to move the mailboxes to the new platform. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Windows Network Load Balancing is no longer recommended for use with Exchange by the product team themselves, which is a good thing because it sucks pretty bad. Otherwise, what I am saying is what you have written, the only issue is that the clients will NOT start using the new server automatically, because they connect to the CAS role, not the mailbox role, and the mailbox databases do not "belong" to any server. They are an org setting. Your biggest headache is going to be getting the clients to use the new platform. Personally the way that I would do it is to install the new CAS/Hub servers first, setup the RPC CAS Array to point to one of the new CAS role holders. Outlook ANywhere, OWA, ActiveSync etc can all be pointed to the new servers once the SSL certificate has been sorted out. Exchange 2010 SP2 with the latest rollup naturally. Then build the new mailbox servers, with the DAG etc in place and test it. Once you are happy then start to move the mailboxes to the new platform. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Hi If one post is helpful to you, please mark it.Terence Yu TechNet Community Support