Rename Domain or Create new Domain or Domains

Hello,

We have a W2K3 domain with domain controllers located in 5 differnt
locations and are running Exchange 2003, and a SQL2000 server, about 100
workstations and users. The domain name contains an underscore (xxx_xxxxx). I
have not had showstopper problems because of the underscore but some
applications and devices such as NAS don't like it. I am useing VPN over
mostly DSL between the home office and remote locations.

I have tried Domain rename (useing a DC and workstation I pulled from the
production domain) in a limited lab enviorment It did work and I was
comfortable with the process but I am worried about doing the production
network, if things go wrong it will be an overwhelming amount of work to
recover concidering the 5 different locations. Once the domain is renamed I
intend to start upgrading DC's in the primary location to W2K8 (remote areas
will be W2K3 until the next HW change), install a new Exchange server with
W2K8 and Exchange 2007. Exchange 2003 will then be retired.

Can I simply create a new domain, trust the two and move resources, users
computers etc in planned phases? If so, please give me an idea of how to go
about it or any references you might know of.

I also have looked at the idea of making a domain for each location, would
this be a better way to go? I only have one server on each remote site, so if
I do this I would have only one DC for each of the remote location. As things
are now, one can fail and I can quickly create a new one. ?????

Really need some help here, as each day goes by I feel like I'm digging a
deeper hole by not doing a rename... and the CEO is looking for some new
features in Exchange...

Thank You Very mich for your help!

Domain rename with exchange involved requires additional tasks afterwards.
About SQL i don't know, maybe use the SQL forums to be sure about.
http://technet.microsoft.com/en-us/m...ainrename.aspx

http://msexchangeteam.com/archive/20...30/222719.aspx

http://support.microsoft.com/kb/838623

http://support.microsoft.com/kb/925822

I would prefer the way to migrate to the new domain with ADMT 3.1 and directly
use the enw domain with 2008 and exchange 2007:
http://www.microsoft.com/downloads/d...displaylang=en

http://www.microsoft.com/downloads/d...displaylang=en

http://technet.microsoft.com/en-us/l.../bb124008.aspx

Also see the included links to part 2/3:
http://www.msexchange.org/tutorials/...007-Part1.html

http://support.microsoft.com/kb/555854

Making a domain for each location isn't necessary in your environment, more
administrative work and not really any advantage. Configure AD sites and
services properly and use OUs for each location with the machines and user
account, this way you can configure GPOs for each location and also delegate
control without having the need for domain admins outside the main site.

You should have at least in each location one DC/DNS/GC, better of course
for failover and redundancy is always having 2 of them. For recovery with
having more then one DC, as you already have, it is safe also with one DC
in each site. IMPORTANT is that replication works correct between all sites
and is configured in AD sites and services to good replication schedule,
default is 180 minutes for inter-site replication. Depending on the connection
speed you can lower this.

domain rename can be quite painful.
less painful would be a migration to a new domain