Upgrading W2K domain
controllers to WS2003 is trivial
since no modification of the namespace is required. Make sure all
your W2K domain controllers have the latest service pack installed,
adprep to prepare the forest by extending the
schema, and then run Setup on each domain controller to upgrade to
If you are upgrading an NT domain, you need to upgrade the PDC first:
Synchronize all BDCs with PDC → take one BDC offline in case something goes wrong → insert WS2003 product CD into PDC → select Upgrade
Test your new mixed-mode domain, then upgrade the remaining BDCs, test, and once you’re sure everything works, you can upgrade or decommission the BDC you set aside for an emergency.
There’s very little to configure on a domain controller:
Active Directory Users and Computers → Select domain → select OU → right-click on a domain controller → Properties
The “Trust computer for delegation” setting on the General tab enables services on the local machine running under the LocalSystem account to request services from other servers on behalf of clients. Since this can be a security concern, enable this only if you know it will be needed—for example, to allow the Message Queuing Service to run on the machine. None of the other settings on the properties sheet are really important, though a few—such as displaying the latest service pack installed on the machine—are informative.