troubleshooting Question

Move Windows 2003 primary domain controller and active directory database to a new Windows 2003 server

Avatar of bgcmcfl
bgcmcfl asked on
Windows Server 2003Active DirectoryDNS
4 Comments1 Solution1106 ViewsLast Modified:

My goal is to move my current Windows 2003 primary domain controller and active directory database to a new server that I am going to purchase.  Here is some history and details.

I currently have a Windows2003 Server as a primary domain controller running active directory.  Also running on this server is an access database and a terminal server.  When I first set this up this way it was fine for my organization, but since then we have expanded and are adding an exchange 2007 server soon.

Before I implement the Exchange 2007 server I would like to pay some attention on the active directory server first  and break it up into two servers.  I am purchasing an additional server that will allow me do have active directory running on one server by itself and the terminal server and database running on another.

Ideally I would like to move my current domain and active directory database to this new server.  Is this possible? My main goal is to not have to do any work on the workstations that are connected to the directory.  I don't want to have to re-attached them to the domain and want the users experience to be seamless.  Is this possible?

Also, I do not want to just move the terminal server and access database off of this current active directory server and leave the active directory the way it is, because this server has some performance issues and other issues that I would rather not try and fix since it will take too much time.  And this current active directory server was my first attempt at creating a domain and it used to be a file server and other things before, so it just would be better to reformat and start over with this system.

What do you think?  Is this going to work.  Any best practices I should keep in mind.

Also, during this process would it be possible to change the domain name, since we have changed our company name? This is not as important but if there is a way I might want to try it.  And since we haven't implemented the exchange server yet I think I read that it might be possible, but after the exchange server that it is definitely not an option.  And I understand that if I choose to change the domain name that this will definitely affect the workstations and I will have to re-attach them.  However, once re-attached would the user accounts be the same as before, so that the users experience would still be seamless?

It is all about the users in my case.  I want as few interruptions as possible for them.

Any help would be greatly appreciated.  Let me know if you need more information.  I hope I have been clear enough.  This is my first post to experts.  Thanks.
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 4 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 4 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros