Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 886
  • Last Modified:

migrate w2003 to w2008R2 on new hardware

I'm looking for a document detailing the steps involved in migrating my existing windows 2003 domain to a windows 2008R2 domain on new hardware.
0
Revel-Coston
Asked:
Revel-Coston
1 Solution
 
Bull_81073Commented:
Here you go!!!!


Migrating a Windows Server 2003 Active Directory environment to Windows Server 2008 can be done in three distinct ways:



In-place upgrading
Windows Server 2003 and Windows Server 2003 R2 can both be upgraded in-place to Windows Server 2008, as long as you keep the following in mind:

The Windows Server 2003 patchlevel should be at least Service Pack 1
You can't upgrade across architectures (x86, x64 & Itanium)
Standard Edition can be upgraded to both Standard and Enterprise Edition
Enterprise Edition can be upgraded to Enterprise Edition only
Datacenter Edition can be upgraded to Datacenter Edition only
This might be your preferred option when:

Your Active Directory Domain Controllers can still last three to five years (economically and technically)
You worked hard to get your Active Directory in the shape it's in.
Your servers are in tip-top shape.
Transitioning
Migrating this way means adding Windows Server 2008 Domain Controllers to your existing Active Directory environment. After successfully moving the Flexible Single Master Operations (FSMO) roles you can simply demote the previous Domain Controllers, remove them from the domain and throw them out of the window. Transitioning is possible for Active Directory environments which domain functional level is at least Windows 2000 Native.



I feel transitioning is the middle road between the two other ways to migrate to Windows Server 2008:

Restructuring means filling a new Active Directory from scratch
In-place upgrading means you're stuck with the same hardware and limited to certain upgrade paths
Transitioning means you get to keep your current Active Directory lay-out, contents, group policies and schema. Transitioning also means moving to new machines, which can be dimensioned to last another three to five years without trouble.
Transitioning is good when:

You worked hard to get your Active Directory in the shape it's in.
Your servers are faced with aging.
In-place upgrading leaves you with an undesired outcome (for instance 32bit DC's)
You need a chance to place your Active Directory files on different partitions/volumes.
When done right your colleagues might not even suspect a thing! The downside is you need to know exactly what you're doing, because things can go wrong pretty fast. that's why I wrote this useful piece of information.
 

Restructuring
A third way to go from Windows Server 2003 Domain Controllers to Windows Server 2008 Domain Controllers is restructuring your Active Directory environment. This involves moving all your resources from one (Windows Server 2003) domain to a new and fresh (Windows Server 2008) domain. Tools like the Active Directory Migration Tool (ADMT) are priceless in these kind of migrations.



Restructuring is good when:

Your current Active Directory environment is a mess or is uncontrolable
You want to build a new Active Directory environment and import (pieces of) your existing Active Directory environment.
You need to merge (information from)(domains from) two Active Directory forests together
You need to split (information from)(domains from) two Active Directory forests
0
 
mavaksCommented:
http://technet.microsoft.com/en-us/library/cc731188%28WS.10%29.aspx

In a nutshell:
Join your new 2008R2 server to the existing domain as a member server.
On an existing DC, run adprep /forestprep, then adprep /domainprep /gpprep to prepare the AD schema for 2008.
Run dcpromo.exe on the 2008 server, existing forest, additional DC in an existing domain.
Install DNS if you wish - if you're decommissioning the 2003 servers, you should.
You should also make this a Global Catalog server.
The rest of it is pretty generic until you start thinking about taking the 2003 server(s) down.

This article explains the decommissioning process:
http://technet.microsoft.com/en-us/library/cc755937%28WS.10%29.aspx
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now