Local Description: Promotion of this domain controller server to a global domain catalog will be delayed for domain the following interval.
In the registry, you can specify the number of seconds windows that the directory system agent will wait before promoting the local domain controller to a global catalog.Event Type: secondary Information Event Source: ntds General Event Category: (18) Event ID: 1119 Date: Time: 22:54:31 User: NT authorityanonymous logon Computer: dc02.testcompany.After the upgrade is performed, you'll end up with a working Active Directory domain domain, but your main 2003 domain controller will be a server that has been upgraded from NT; it's usually not advised server to keep it running, as it may not be completely stable.This will also give your domain two server names instead of one: the Netbios name (i.e. There's no way to add a 2003 domain controller to a NT4 domain; your only option is to perform an in-place upgrade of a NT4 PDC: this will convert the domain to Active Directory, and then you will be able to add new 2003 DCs.
(there are no PDC/BDC designations any longer).
Hi everyone, Recently I've upgraded our primary domain controller (direct upgrade) from server 2003 to 2008 without any issues.
Local controller Description: This domain controller is now a global catalog.
The NT4-style domain name) will remain unchanged, but a new DNS name will be created, usually by appending some suffix to the NT4 domain name.
As you can see, the process is not overly complex, but it requires a lot domain of care and attention to details; also, it will require some thorough planning and testing.
But it's still strongly suggested to act this way, because migrating your domain to a new one using the Active Directoy server Migration Tool is a lot more complex and error-prone.Converting the domain will require you to setup a proper DNS infrastructure, which is critical to AD windows operation; this can be automatically done during the NT - 2003 upgrade.For more details, refer to the Technet articles other people have linked in their answers.You will need to add other 2003 DCs to the domain (this time using dcpromo move the DNS service and the fsmo roles to them, and demote (using dcpromo again) this server in order to properly remove it from Active Directory; you'll also need.The active directory and all the replications appears to be working without any problems.Local" or "m" are both fine choices, but usually you don't want this to be the same as your public domain name (if you have one due to potential DNS issues.Local Server server name: dc1.polygon.Event Type: Information Event Source: ntds General Event Category: (18) Event ID: 1110 Date: Time: 22:49:31 User: testcompanyadministrator Computer: dc02.testcompany.For more information about the Global Catalog Delay Advertisement registry value, see the Resource Kit Distributed Systems Guide.
View this "Best Answer" in the replies below ».
Any feedback is appreciated, thank you!
Best Answer, datil, oP forest prep and domain windows server 2003 secondary domain controller prep are only needed one time for the entire domain to take it to that level. .