One other thing you also need to run the /gpprep switch since you are coming from Windows 2000
http://technet.microso
"If this domain controller is the first Windows Server 2008 or Windows Server 2008 R2 domain controller in a Windows 2000 Server domain, you must first prepare the domain by running adprep /domainprep /gpprep on the infrastructure master "
The only other suggestion I would make is to think about going with the x64 version of Windows 2008. It won't be a big deal now but next year when Windows 2008 R2 is released it will only be released in a x64 version so it will be easy for you to add that if you are already at 2008 x64.
Thanks
Mike
by: AmericomPosted on 2009-03-05 at 12:24:47ID: 23810137
I would leave the existing 2000 DC and just add your win2k8 DC.
Step to add a Windows Server 2008 DC in a Windows 2000 Domain:
Part I--Adrep to extend the AD schema
1. Identify the FSMO roles in your DCs
2. Run adprep with the /ForestPrep switch on the DC w/ schema master operations role [Forest specific]
3. Wait for the schema changes to be replciated to all the DCs that hold the infrastructure operations master roles in all domains
4. Run adprep with the /domainprep switch on the infrastructure master domain controller role in that domain. [Domain Specific]
5. After the changes made by adprep /domainprep have been successfully replicated to all DC in that domain,
you can proceed w/ installation of a first Win2k8 DC in that domain in Part II below.
Note: The forest preparation step must be performed only once for the entire forest. The domain preprations step mustt be performed only once in a domain
before a first Windows Server 2008 Domain controller in that domain is installed. You do not have to run adprep /domainprep in the same domain
again before installing any subsequent domian controllers. You do not have to prepare those domains where you are not planning to install
Window Server 2008 domain controllers. Finally, first win2k8 DC must be a GC and cannot be RODC.
Part II--Promoting your new Win2k8 to DC.
1 NSLOOKUP and ping your existing DC by hostname, IP, FQDN and vice versa.
2 Add DNS and DHCP roles(if it will be used) before dcpromo. You should point the preferred DNS of your new server to one of your existing DCs
3 Add the Active Directory DS role and configure it as an additional domain controller in an existing domain.
4 Verify functionality and DNS gets replicated. Then point the preferred DNS itself.
5 Transfer the FSMO from old to new and verify if it is also a GC.
6 If needed, Import DHCP database from old to new(see Part III below), Update DHCP's DNS Scope to new DC IP address. [if you have DHCP and plan to move it as well]
7 Wait a day or two , the shut it off(or unplug the NIC) temporarily and see if anyone complain or anything there that you are not aware of.
8, If everything is fine then put the old DC online and wait or force replicaiton
9 DRPROMO to remove this old DC,raise the domain and forest functional level to win2k8, you're done
Part IIIa---Moving your DHCP
You can move the DHCP before and after your AD migration or upgrade. It's relatively easy to move the scope from a windows server 2000 to 2003.
Just follow the step here: http://support.microsoft.c
This way you can retain all the scope settings including the type of scopes, customized scopes, as well as exclusing and reservation range etc.
This DHCP migration approach is what I usually use as it wll take us more time to create it manually with our DHCP scopes..
Part IIIb---Moving your DHCP
If your dhcp is very simple and can be created manaully, here's the other alternative:
1. create the new scope in new 2003 server, authorize it(this meand you are doing this after the migration)
2. Up the conflict detection to "2", you can do this by right-click on your new DHCP server and click on the advanced tap. This will prevent the change of having duplicate IP address.
3. Before you enable the scopy in the new server, disable the scope in the old dhcp server
4. Enable the scope in the new DHCP server