A speed bump on the information super highway.
I’m getting ready this weekend to replace one of my windows 2003 domain controllers. This DC is a DNS,DHCP, and WINS server.
Moving DHCP from windows 2000 to 2003 was a royal pain if both machines where already DC’s
Microsoft has much improved this process for 2003 to 2008
Here’s the steps to follow from a MS KB Article
Image via CrunchBase
There are quite a few ways to tell. Here are a few I found.
The correct version of the ADPrep.exe tool for Windows Server 2003 R2 is 5.2.3790.2075.
You can verify the operating system support level of the schema by looking at the value of the Schema Version registry subkey on a domain controller. You can find this subkey in the following location:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters
You can also verify the operating system support level of the schema by using the Adsiedit.exe utility or the Ldp.exe utility to view the objectVersion attribute in the properties of the cn=schema,cn=configuration,dc=<domain> partition. The value of the Schema Version registry subkey and the objectVersion attribute are in decimal.
Schema Version ObjectVersion values and corresponding operating system support level
******OR*********
adfind -sc schver. It gets objectVersion code and translates into Win2003 version.
******OR*********
Win2003 http://technet.microsoft.com/en-us/library/cc783495.aspx
To verify that the Active Directory Preparation tool has completed all operations successfully
Category : Daily Links
Image via Wikipedia
If you run dcdiag and get a failure on the systemlog, it means you have errors in the system event log. You can clear the system event log (make sure you save it) and then your dcdiag should show success for the systemlog.
I ran into that issue today, thanks to petri.co I found the answer and I thought I’d share.
