
Microsoft
®
Windows Server
™
2003 White Paper
Windows NT 4.0 Server Upgrade Guide 65
HGFPORTAL Intranet server running Microsoft SharePoint
™
Windows 2000
SP3
HGFWEB Web server (IIS) providing internal application Windows NT
4.0 SP6
HGFFILE2 File and print services Windows NT
4.0 SP6
HGFEXCHANGE Exchange 5.5 Server Windows NT
4.0 SP6
HGFSQLSERVER2 SQL Server 2000 database due to replace SQL Server 6.5
database for internal application
Windows 2000
SP3
IRVBDC BDC for HGFPROPERTIES domain providing local validation
to Irvine Branch
Windows NT
4.0 SP4
IRVFILE Local file and print server for Irvine branch Windows NT
4.0 SP4
HAYBDC BDC for HGFPROPERTIES domain providing local validation
to Hayward branch
Windows NT
4.0 SP5
HAYFILE Local file and print server for Hayward branch Windows NT
4.0 SP5
ANABDC BDC for HGFPROPERTIES domain providing local validation
to Anaheim branch
Windows NT
4.0 SP6
ANAFILE Local file and print server for Anaheim branch Windows NT
4.0 SP6
Upgrade Methodology
One of the first steps in upgrading a Windows NT 4.0 domain is to make a decision about the type
of upgrade to perform. Should the current domain be upgraded in place to Active Directory? Or
maybe to a parallel Active Directory domain where you use the Active Directory Migration Tool
(ADMT) to upgrade users, servers, printers, and so on, to the new Active Directory domain? HGF
Properties decided to perform an in-place upgrade of the current domain, a decision that means
the PDC must be upgraded.
This upgrade can happen in a couple of different ways. One way to upgrade would be to start with
the member servers and upgrade all of them to Windows Server 2003. After upgrading the
member servers, the domain controllers can be upgraded to install Active Directory. This
approach allows administrators to get familiar with the upgrade process before upgrading the
actual accounts database.
Another method is to upgrade the domain controllers first. After the domain has been moved to
Active Directory, all the member servers can be upgraded. This approach is more useful if an
organization is looking to gain the benefits of Active Directory as soon as possible. It also is useful
when the need to upgrade to Active Directory is driven by an application. For example, an
organization may need to upgrade a certain application, but its latest version requires Active
Directory.
Komentarze do niniejszej Instrukcji