Bonnie_K
asked on
2003 Domain rename with Exchange 2003, 2007 and Server 2008 DC's
Hello,
Our client need to rename their domain. We are in the middle of moving them from a 2003 domain with exchange 2003 to a 2008 domain with exchange 2007. We didn't find out the wanted to rename the domain until we built 2 new DC's a new exchagne, 4 citrix servers, etc... with the old domain name.
So instead of rebuilding the 2008 domain we are planning to use the tools to rename a 2003 domain before we move the roles to the 2008 server and down the 2003 domain.
Any opinions about this based on experience with domain rename would be helpful.
Thanks,
Bonnie
Our client need to rename their domain. We are in the middle of moving them from a 2003 domain with exchange 2003 to a 2008 domain with exchange 2007. We didn't find out the wanted to rename the domain until we built 2 new DC's a new exchagne, 4 citrix servers, etc... with the old domain name.
So instead of rebuilding the 2008 domain we are planning to use the tools to rename a 2003 domain before we move the roles to the 2008 server and down the 2003 domain.
Any opinions about this based on experience with domain rename would be helpful.
Thanks,
Bonnie
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I still wouldn't do it. I have seen too many business networks (running on both 2003 and 2008) crippled as a result of a rename, with no network left to retrieve data from Exchange, User Accounts etc. It often works 25 times in a lab, but put it on a production system and it doesn't work.
Of course, if the author wants to proceed, that is their opinion, but from my own experience I would never recommend this.
-tigermatt
It goes without saying that you would get full backups of all your critical servers before you attempt an operation like this (you should have them already though =] ).
I have done this a few times in production 2003 environments with Exchange 2003 without issues. They were single site domains with between 3 and 20 servers and 25 and 250 clients.
So yeah... test it in a lab, do it on a weekend, and have a recovery plan if you decide to do it.
I have done this a few times in production 2003 environments with Exchange 2003 without issues. They were single site domains with between 3 and 20 servers and 25 and 250 clients.
So yeah... test it in a lab, do it on a weekend, and have a recovery plan if you decide to do it.
They were comfortable enough with the RENDOM utility that they included it with Windows. It is now a supported operation ("unsupported" in Server 2000 & 2003).
Having an Exchange server in the organization shouldn't affect the chances of success in this instance.