NT4-> Win2003srv

[MrOnline]

I'm working on a test where i gone upgrade a nt4 domain to win2k3srv. When i did this on 2k srv ms had some great tut's on how to do this. For how to do this on win2k3srv i havent found any good information. So far i just have papers on how to move dns and catalog server to the new server.

The way this upgrade gone be done is, i install a new nt4.0 to the old domain, promote it to pdc, remove an updated bdc from the network, then upgrade the PDC to win2k3srv. When this is done i gone install a new server to be "domain first server" but i havent found any information about what i have to remove/move from the server i upgrade from nt4 to 2k3 before i can remove it.

Hoping for a quick answer...

MrOnline....

[Marsden]

Upgrading from a Windows NT Domain

The Active Directory Installation Wizard simplifies upgrading a Windows NT domain to Windows Server 2003 Active Directory. Active Directory Installation Wizard installs and configures domain controllers, which provide network users and computers access to the Active Directory service. Any member server (except those with restrictive license agreements) can be promoted to domain controllers using the Active Directory Installation Wizard. When promoting member servers to domain controllers, you will define one of the following roles for the new domain controller:

• New forest (also a new domain)

• New child domain

• New domain tree in an existing forest

• An additional domain controller in an existing domain

For additional information on using the Active Directory Installation Wizard, see the Windows Server 2003 on-screen Help and Support Center.

The upgrade process involves the following steps:

• Planning and implementing a namespace and DNS infrastructure

• Determining forest functionality

• Upgrading the server running Windows NT Server 4.0 or earlier primary domain controller

• Upgrading any remaining backup domain controllers

• Converting groups

• Completing the upgrade of the domain

• Installing Active Directory client software on older client computers

Planning and Implementing a Namespace and DNS Infrastructure

Namespace refers to the naming convention that defines a set of unique names for resources in a network, such as Domain Name System (DNS), a hierarchical naming structure that identifies each network resource and its place in the hierarchy of the namespace, and Windows Internet Name Service (WINS), a flat naming structure that identifies each network resource using a single, unique name.

DNS is required for Active Directory. DNS is a hierarchical, distributed database that contains mappings of DNS domain names to various types of data, such as IP addresses. DNS enables the location of computers and services by user-friendly names, and it also enables the discovery of other information stored in the database.

When setting up a namespace, it is recommended that you first choose and register a unique parent DNS domain name that can be used for hosting your organization on the Internet, for example, microsoft.com. Once you have chosen your parent domain name, you can combine this name with a location or organizational name used within your organization to form other subdomain names. For example, if a subdomain were added, such as itg.example.mydomain.com domain tree (for resources used by the information technology group at your organization), additional subdomain names could be formed using this name. For instance, a group of programmers working on electronic data interchange (EDI) in this division could have a subdomain named edi.itg.example.mydomain.com. Likewise, another group of workers providing support in this division might use support.itg.example.mydomain.com.

Prior to beginning the upgrade from Windows NT Server 4.0 to the Windows Server 2003 Active Directory service, ensure that you have designed a DNS and Active Directory namespace and have either configured DNS servers or are planning to have the Active Directory Installation Wizard automatically install the DNS service on the domain controller.

Active Directory is integrated with DNS in the following ways:

• Active Directory and DNS have the same hierarchical structure. Although separate and implemented differently for different purposes, an organization's namespace for DNS and Active Directory have an identical structure. For example, mydomain.com is both a DNS domain and an Active Directory domain.

• DNS zones can be stored in Active Directory. If you are using the Windows Server DNS service, primary zone files can be stored in Active Directory for replication to other Active Directory domain controllers.

• Active Directory uses DNS as a locator service, resolving Active Directory domain, site, and service names to an IP address. To log on to an Active Directory domain, an Active Directory client queries its configured DNS server for the IP address of the Lightweight Directory Access Protocol (LDAP) service running on a domain controller for a specified domain.

For more information on how Active Directory clients rely on DNS, see “Locating a Domain Controller” in the Windows Server 2003 on-screen Help and Support Center.

While Active Directory is integrated with DNS and they share the same namespace structure, it is important to distinguish the basic difference between them:

• DNS is a name resolution service. DNS clients send DNS name queries to their configured DNS server. The DNS server receives the name query and either resolves the name query through locally stored files or consults another DNS server for resolution. DNS does not require Active Directory to function.

• Active Directory is a directory service. Active Directory provides an information repository and services to make information available to users and applications. Active Directory clients send queries to Active Directory servers using LDAP. In order to locate an Active Directory server, an Active Directory client queries DNS. Active Directory requires DNS to function.

For more information on DNS configuration, see the Windows Server 2003 on-screen Help and Support Center.

Determining Forest Functionality

Forest functionality determines the type of Active Directory features that can be enabled within the scope of a single forest. Each forest functional level has a set of specific minimum requirements for the version of operating system that domain controllers throughout the forest can run. For example, the Windows forest functional level requires that all domain controllers be running Windows Server 2003 operating systems.

In the scenario where you are upgrading your first Windows NT domain so that it becomes the first domain in a new Windows Server 2003 forest, it is recommended that you set the forest functional level to “Windows interim.” (You will be prompted during the upgrade.) This level contains all the features used in the Windows 2000 forest functional level and also includes two important advanced Active Directory features:

• Improved replication algorithms made to the intersite topology generator

• Replication improvements made to group memberships

The Windows interim functional level is an option when upgrading the first Windows NT domain to a new forest and can be manually configured after the upgrade.

For more information about how to manually set this functional level, see the Microsoft Windows Resource Kits Web site at

http://www.microsoft.com/windows/reskits/.

The Windows interim forest functional level only supports domain controllers running Windows and Windows NT, not domain controllers running Windows 2000. Servers running Windows 2000 cannot be promoted to a domain controller in a forest where the forest functional level has been set to Windows interim.