Any impact if renaming W2K8 AD domain name?

This is using a single W2K8 single-domain AD. Due to political issue, my boss want me to rename the domain name. I read through some articles about the renaming, and just don't understand why every workstation has to be rebooted twice after the renaming process.

What other considerations, impacts I have to be aware if any? Any how about the sure-work renaming steps?
BalackAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Chris DentPowerShell DeveloperCommented:

The first thing to note is that if Exchange 2007 / 2010 is involved you should not attempt a domain rename. And if you happen to be running SBS then you cannot use Domain Rename.

Otherwise you must read the documentation here:

http://technet.microsoft.com/en-us/library/cc794869%28WS.10%29.aspx

Chris
0
NJComputerNetworksCommented:
"just don't understand why every workstation has to be rebooted twice after the renaming process. "

You can use this procedure to restart member computers after a domain rename operation. After the domains are renamed, you have to create a process by which all member computers in the renamed domains in your forest recognize and propagate the domain name changes to all applications and services that are running on member computers. You can do this by notifying all users to restart their computers (the member computers) to cause those computers to pick up the domain name changes.

When the member computers are restarted, their Domain Name System (DNS) host names will also change after the restart as a result of the fact that their primary DNS suffix changes as a result of the name change of the domain of which they are members. The primary DNS suffix of a member computer in an Active Directory domain is, by default, configured to change automatically when domain membership of the computer changes. If you have very large domains whose DNS name was changed by the domain rename operation and these domains have a large number of member computers, you might observe a large replication storm and a surge in network traffic as a result of the member computer restarts. For information about how to avoid excess replication under these conditions, see Configure Member Computers for Host Name Changes.

Restart all member computers twice.
Restart twice all member workstations, member servers, and standalone servers (excluding domain controllers) that are running Windows 2000, Windows XP, Windows Server 2003, and Windows Server 2008 in the renamed domains in your forest. When you restart these computers twice, this ensures that each member computer learns of the domain name changes and propagates the changes to all applications and services that are running on the member computer.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Chris DentPowerShell DeveloperCommented:
NJ...

Can you post a link to the source for the text above please. If you copy and paste text you must cite the source.

Chris
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Chris DentPowerShell DeveloperCommented:

Thank you :)

Chris
0
B HCommented:
he got that from here:
http://technet.microsoft.com/nl-nl/library/cc816689%28WS.10%29.aspx

with only one server, nothing you can move everything to temporarily, it's a really bad idea to up and change the name...

but if your boss needs you to do it anyway, i would strongly suggest something more generic so you dont have to do this in a year again when the company changes their name or dumps a partner or something
0
BalackAuthor Commented:
No Exchange server.
0
BalackAuthor Commented:
Good explanation
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.