Friday, December 18, 2009

The Best Way to Move Your Nt 4.0 to Active Directory 2003

The Best Way to Move Your Nt 4.0 to Active Directory 2003
There are many ways to approach the task of performing an upgrade from Microsoft® Windows NT® Server 4.0 operating system environments to a Microsoft Windows ServerTM 2003 environment. Each upgrade has to be analyzed and planned to determine the best possible approach for a specified scenario. This document provides upgrade scenarios to help us plan and execute an upgrade process in our organization.

Why Upgrade?
There are many reasons to upgrade. One reason is to keep pace with new technology. The return on investment must be evaluated. Windows Server 2003 provides many advantages over earlier Windows NT 4.0 Server version. Many of these benefits fall under the umbrella of enhancing system security. Other significant new features help make this version of Windows the most reliable, scaleable, and dependable operating system that Microsoft has delivered. As a result, the return on investment of moving to Windows Server 2003 can be quickly realized.
MCTS Training, MCTS Certification

Upgrading Windows NT 4.0 Domains to Active Directory
Upgrading corporate Windows NT 4.0 domains (JKT) to Windows Server 2003 Active Directory (JKT.corp.int) involves first completing the necessary preparation tasks and then following the steps to complete the upgrade.

Preparing to Upgrade
Before beginning an upgrade from Windows NT Server 4.0 to Windows Server 2003, we need a plan that details the many tasks to be performed. This upgrade plan assists in establishing the order in which to upgrade servers and domains, assessing available resources, and obtaining the information necessary to upgrade the systems in the most efficient way. The upgrade plan also includes all components to be upgraded and the proper upgrade order. Dependencies among servers and applications need to be carefully examined. Hardware needs to be inspected as well.

Step by step to Migrate

Migration Process
We introduce a temporary Windows NT 4.0 Server act as BDC, named TESTINGDC, promote it to a PDC, and perform the in-place Windows 2003 upgrade on it. That approach is more convenient because we will not interrupt the corporate users, and they will be able to connect to PDC as usual during the upgrade. It is a safer approach too. We will keep a BDC shut down, and use it to switch back to the original configuration, in case the upgrade fails.

As the name suggests, TESTINGDC is going to be used temporary as a Domain Controller. We also have a clean installed Windows Server 2003 as a main Domain Controller in XXX forest. Therefore we will add a clean installed Windows Server 2003 named DC1, in the domain, run DCPROMO on it and transfer the FSMO roles to it.

Demoting and removing TESTINGDC will follow, then moving the resources and services from PDC. Last, we will delete PDC and BDC, and raise Domain and Forest functional levels.

Step by step to migrate
1. Add a new server -TESTINGDC, as a BDC to the NT 4.0 Domain “certkingdom.com”.

In this step, we install and prepare a Windows NT Server as BDC

2. Promote TESTINGDC to a primary domain controller and shutdown the existing server BDC.
a. Start Server Manager at the PDC and open Start à Programs à Administrative Tools à Server Manager
b. Highlight the entry for the BDC and choose Computer à Promote to Primary Domain Controller
c. Click Yes to the dialog box, so that the BDC can be promoted.
d. Once the promotion has taken place, which may take a couple of minutes, refresh the server manager screen [F5].
e. Promote the current BDC to a PDC [this will restore the original PDC]

If the PDC for the domain goes off-line, users will still be able to logon to the domain if there is a BDC available. However, if there is no PDC, no changes to the domain accounts database is possible till the PDC is restored.

3. Perform in place upgrade of DCTEST to Windows 2003 server.
4. Promote DCTEST and check the status of Active Directory
5. Add a clean installed Windows 2003 server
6. Promote DC1 as Additional Domain Controller and move all FSMO roles to it
7. Move DNS roles and convert databases to the new server
8. Demote DCTEST
9. Raise Domain and Forest functional levels
10. Finish

No comments: