Changing the hostname of an exchage server and its effects on outlook clients
We will be moving exchange accounts from one machine to another (exchA and exchB). After this move we will be removing exchA from the AD domain and renaming exchB to exchA. How will this effect the outlook clients assuming the clients were originally pointed at exchA for mail.
Another way to look at this question is do the outlook clients use DNS or SIDs to find and talk to the exchange server.
The environment is AD2000 with exchA running Exchange2000 and exchB running Exchange2003. The clients are a mix from Outlook XP to Outlook 2007.
Thanks,
Louis
Another way to look at this question is do the outlook clients use DNS or SIDs to find and talk to the exchange server.
The environment is AD2000 with exchA running Exchange2000 and exchB running Exchange2003. The clients are a mix from Outlook XP to Outlook 2007.
Thanks,
Louis
Asked:
Who is Participating?
To confirm what has been said above - you cannot rename an Exchange server.
No workarounds.
If you want to rename the Exchange server you will have to move all of the data off to another machine - that is another Exchange server, not just move the databases, remove Exchange, drop the machine in to a workgroup, wipe it, rebuild it with the new name, reinstall Exchange and then move all of the data back.
There are many reasons for this, but it is mainly down to the use of the machine name in the Exchange org, databases and other areas that cannot be changed easily. You would have to adjust every user account manually for example - if you could get the databases to mount.
Any reason you want to use the old name?
If you did then you should have done a swing migration to a temporary machine with another name so that the new server could be built after the original one has been removed with the new name.
Simon.
No workarounds.
If you want to rename the Exchange server you will have to move all of the data off to another machine - that is another Exchange server, not just move the databases, remove Exchange, drop the machine in to a workgroup, wipe it, rebuild it with the new name, reinstall Exchange and then move all of the data back.
There are many reasons for this, but it is mainly down to the use of the machine name in the Exchange org, databases and other areas that cannot be changed easily. You would have to adjust every user account manually for example - if you could get the databases to mount.
Any reason you want to use the old name?
If you did then you should have done a swing migration to a temporary machine with another name so that the new server could be built after the original one has been removed with the new name.
Simon.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
-
Course of the Month5 days, 21 hours left to enrollMonitoring and Operating a Private Cloud with System Center 2012 R2 273 lessons
Your best bet is to just keep the new exchange server as a new name, or you will need to exmerge all the data out> swap servers>exmerge data in to the new server or do a swing migration or exchange.