13

Im not a expert admin in Active Directory so I'm in need of some help.

At my work, we have bought a new server with the 2008 server OS. And the old AD domain controller is run on a 2003 server.

The thought is to make the 2008 server the new DC and the 2003 server is to be a file server.

What is the best way to move the AD and all it's settings, members, groups, rights etc to the new server?

And how do you remove the AD-settings from the old one?

Thank you in advance.

6 Answers 6

16

The quick answer is to use dcpromo to add the 2008 server as a domain controller in the same domain that the 2003 server is in. Once the 2008 server is a DC, you can run dcpromo on the 2003 server to remove it as a domain controller. This will allow you to keep your Active Directory intact, but move the services to another server.

Also, as a general rule, it's highly recommended to have 2 servers be domain controllers (and global catalog servers) for your domain. That way your Active Directory stays up in the event of a failure (or reboot!)

There are lots of good articles from Microsoft and bloggers that describe this process. Here are some links:

2003 to 2008 Active Directory

Upgrading to Windows 2008 Active Directory

4

Here is a TechNet guide. Probably a good place to start.

Planning to Upgrade Active Directory Domains to Windows Server 2008 AD DS Domains

3

I have done this many times. There are quite a few things that you need to keep in mind. If you currently only have one DC it might be in your best interest to have two DC's.

Also if you want to have just one instead you will need to install the services that you run on the current DC onto the 2008 DC. These are services such as DNS, and DHCP.

If you currently only run one single 2003 server, then that server also serves as your FSMO role holding server. You will first need to move your FSMO roles to the 2008 server before demoting the 2003 server. If you do not you will have severe problems.

Another service to move will be the Global Catalog. You will need to make the new 2008 server a Global Catalog and make sure the replictation has taken place before demoting the 2003 server.

The steps:

  1. Install 2008 on the new server.
  2. DCpromo the new server. Make sure AD is replicating.
  3. Install DNS, DHCP or any other services that you need.
  4. Make sure DNS is replicating. Move DHCP to the other server. Make sure it is working.
  5. Move the FSMO roles to the new 2008 server.
  6. Once you are sure that all roles and services that the 2003 server is using have been moved and are working properly on 2008 then you can proceed with the DCPromo (demote) of the 2003 server.
2

Will you be keeping both servers after the domain upgrade? If so, your best bet is to leave the new box as a member server and upgrade the current DC instead. You can use the technet guide at http://technet.microsoft.com/en-us/library/cc731314.aspx for assistance.

2

you're not going to get two of the same answers for this one. So here is what I would do.

Is your Win2003 your only server?

If yes, then I would do the following,

  1. Install the new Windows 2008 on the new hardware
  2. DCPromo it to become a domain controller
  3. Assign any shares etc to it.

Carry on working.

If you only have 2 servers, make them both DC's. There is no harm in this. Since this is a small network, they can double as your file servers.

The AD domain will be at a 2003 level. Nothing wrong with that, but IF there was a feature you wanted that existed only with a 2008 AD Domain (don't confuse with a 2008 Server) you'd need to remove the 2003 DC by DCPromo it down.

Also personally I hate doing implace upgrades on servers (too risky, had too many bad things happen). Plus you wouldn't be able to if you got the Windows 2008 OEM since its fixed to the new hardware.

2

Be also careful of DNS service, as it is required for Active Directory.

You probably now have DNS up and running on your current DC, and every client or member server is pointing to it; be sure to enable DNS on the new 2008 server after you promote it.

You will then need to point all of your member computers to the new DNS server's IP address (either statically or via DHCP), or swap the IP addresses between the old server and the new one.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .