
Microsoft
®
Windows Server
™
2003 White Paper
Windows NT 4.0 Server Upgrade Guide 67
upgraded to Windows Server 2003 and Exchange 2003. The hardware for the Exchange 5.5
server is still sufficient for other tasks and can be reassigned after Exchange is upgraded to the
new server.
HGFWEB is tackled next. The current Web-based application is tested on a Windows Server
2003 server running IIS 6.0 in a lab environment. After any problems are solved, the server is
upgraded to Windows Server 2003. HGFSQLSERVER2 is then upgraded from Windows 2000 to
Windows Server 2003. HGFREMOTE runs Terminal Services on Windows 2000, so it becomes
the next candidate for an upgrade. Finally, the portal server, HGFPORTAL, is upgraded from
Windows 2000 to Windows Server 2003.
Active Directory Upgrade
Now that all the member servers have been upgraded, it is time to upgrade to Active Directory. To
do this, the PDC must be upgraded first. One recommended approach is to use a new computer.
By using a new computer, some of the risk of upgrading to Active Directory can be mitigated.
The administrators at HGF Properties first install the new server, called HGFDC1, as a
Windows NT 4.0 BDC in the HGFPROPERTIES domain. Next, this new server is promoted to the
PDC, a step that allows the original domain controller—now a BDC—to be promoted back to PDC
status if something goes wrong during the upgrade. As an added precaution, the original PDC can
be taken completely offline and reinstated after a successful upgrade.
This process affords the administrators a certain level of comfort knowing they can return the
domain back to its original configuration in the event of an unsuccessful upgrade. The
administrators would have performed normal backups of these computers before the upgrade
process, so they actually have a couple of ways to get back to the original setup.
HGFDC1 is upgraded by inserting the Windows Server 2003 installation CD. The upgrade wizard
automatically starts and the upgrade process is underway. The administrator must answer
questions regarding the installation along the way as the operating system is upgraded to
Windows Server 2003. Upon finishing the upgrade the server is rebooted and the administrator
logs on to the new Windows Server 2003 system.
After the underlying operating system is upgraded, the Active Directory Wizard automatically
starts. At this point Active Directory is still not installed but that is about to change. During the
upgrade the administrators have to name the new Active Directory domain.
The name corp.hgfproperties.com is chosen as the internal domain name for Active Directory.
Externally, HGF Properties is known as hgfproperties.com. This decision forces HGF Properties
to run what is known as a split-brain DNS structure. Externally, they expose necessary computers
and services using their external domain name. Internally, they maintain a completely different
domain name. When the Active Directory wizard is complete and the computer is rebooted, Active
Directory is installed and running.
What follows are some of the issues that HGF Properties administrators considered during their
upgrade:
Comentários a estes Manuais