Logo
Windows XP
Windows Vista
Windows 7
Windows Azure
Windows Server
Windows Phone
PREGNANCY
 
 
Windows Server

Exchange Server 2007 : Migrating from Windows 2000 Server to Windows Server 2003 (part 2) - Upgrading a Single Member Server

2/9/2014 8:23:09 PM

3. Upgrading a Single Member Server

The direct upgrade approach from Windows 2000 to Windows Server 2003 is the most straightforward approach to migration. An upgrade simply takes any and all settings on a single server and upgrades them to Windows Server 2003. If a Windows 2000 server handles Windows Internet Naming Service (WINS), domain name system (DNS), and Dynamic Host Configuration Protocol (DHCP), the upgrade process will upgrade all WINS, DNS, and DHCP components, as well as the base operating system. This makes this type of migration very tempting, and it can be extremely effective, as long as all prerequisites described in the following sections are satisfied.

Often, upgrading a single server can be a project in itself. The standalone member servers in an environment are often the workhorses of the network, loaded with a myriad of different applications and critical tools. Performing an upgrade on these servers would be simple if they were used only for file or print duties and if their hardware systems were all up to date. Because this is not always the case, it is important to detail the specifics of each server that is marked for migration.

Verifying Hardware Compatibility

It is critical to test the hardware compatibility of any server that will be directly upgraded to Windows Server 2003. In the middle of the installation process is not the most ideal time to be notified of problems with compatibility between older system components and the drivers required for Windows Server 2003. Therefore, the hardware in a server should be verified for Windows Server 2003 on the manufacturer’s website or on the Microsoft Hardware Compatibility List (HCL), currently located at http://www.microsoft.com/whdc/hcl.

Microsoft suggests minimum hardware levels on which Windows Server 2003 will run, but it is highly recommended that you install the OS on systems of a much higher caliber because these recommendations do not take into account any application loads, domain controller duties, and so on. The following is a list of Microsoft recommended hardware levels for Windows Server 2003:

  • Intel Pentium III 550MHz CPU or equivalent

  • 256MB of RAM

  • 1.5GB free disk space

That said, it cannot be stressed enough that it is almost always recommended that you exceed these levels to provide for a robust computing environment.

Note

One of the most important features that mission-critical servers can have is redundancy. Putting the operating system on a mirrored array of disks, for example, is a simple, yet effective way of increasing redundancy of individual servers in an environment.


Verifying Application Readiness

Nothing ruins a migration process like discovering a mission-critical application will not work in the new environment; therefore, it is very important to list all applications on a server that will be required in the new environment. Applications that will not be used or whose functionality is being replaced in Windows Server 2003 can be removed from consideration or retired altogether. Likewise, applications that have been verified for Windows Server 2003 can be designated as safe for upgrade. For any other applications that might not be compatible but are necessary, you either need to delegate them to another Windows 2000 server or delay the upgrade of that specific server.

In addition to the applications, the version of the operating system that will be upgraded is an important consideration in the process. A Windows 2000 server install can be upgraded to either Windows Server 2003, Standard Edition or Windows Server 2003, Enterprise Edition; however, Windows 2000 Advanced Server can be upgraded only to Windows Server 2003, Enterprise Edition. Finally, only Windows 2000 Datacenter Edition can be upgraded to Windows Server 2003, Datacenter Edition.

Backing Up and Creating a Recovery Process

It is critical that a migration does not cause more harm than good to an environment. It cannot be stressed enough that a good backup system is essential for quick recovery in the event of upgrade failure. Often, especially with the in-place upgrade scenario, a full system backup is the only way to recover; consequently, it is very important to detail fall-back steps in the event of problems.

Upgrading a Standalone Server

After all various considerations regarding applications, the hardware compatibility has been thoroughly validated and a full backup has been completed and tested, a standalone server can be upgraded. Follow these steps to upgrade:

1.
Insert the Windows Server 2003 CD into the CD-ROM drive of the server to be upgraded.

2.
The Welcome page should appear automatically. If not, choose Start, Run, type d:\Setup, where d: is the drive letter for the CD-ROM drive.

3.
Click Install Windows Server 2003 (Enterprise Edition).

4.
Select Upgrade from the drop-down box, as indicated in Figure 1, and click Next to continue.

Figure 1. Starting the Windows Server 2003 upgrade.


5.
Select I Accept This Agreement at the License screen, and click Next to continue.

6.
The following screen prompts you to enter the 25-character product key. You can find this number on the CD case or in the license documentation from Microsoft. Enter the product key, and click Next to continue.

7.
The following screen allows for the download of updated Windows Server 2003 files. They can be downloaded as part of the upgrade or installed later. For this example, select No, Skip This Step and Continue Installing Windows. Then click Next to continue.

8.
The next prompt is crucial. It indicates which system components are not compatible with Windows Server 2003. It also indicates, for example, that Internet Information Services (IIS) will be disabled as part of the install, as you can see in Figure 2. IIS can be reenabled in the new OS but is turned off for security reasons. Click Next after reviewing these factors.

Figure 2. Checking the System Compatibility report.


9.
The system then copies files and reboots, continuing the upgrade process. After all files are copied, the system is then upgraded to a fully functional install of Windows Server 2003. If upgrading to Windows Server 2003 R2, setup then invokes the R2 upgrade process by asking to insert the second CD containing R2 information. After being inserted, the final R2 upgrade process can take place.

Note

Many previously enabled components such as IIS are turned off by default in Windows Server 2003. Ensure that one of the postupgrade tasks performed is an audit of all services so that those disabled components can be reenabled.

Other -----------------
- Microsoft Systems Management Server 2003 : Understanding Status Summarizers (part 3) - Configuring Status Summarizers - Site System Status Summarizer
- Microsoft Systems Management Server 2003 : Understanding Status Summarizers (part 2) - Configuring Status Summarizers - Component Status Summarizer
- Microsoft Systems Management Server 2003 : Understanding Status Summarizers (part 1) - Display Interval , Status Message Thresholds
- Microsoft Systems Management Server 2003 : Analysis and Troubleshooting Tools - Working with Status Messages (part 2) - Setting Status Message Viewer Options
- Microsoft Systems Management Server 2003 : Analysis and Troubleshooting Tools - Working with Status Messages (part 1) - Viewing Site Status Messages
- Microsoft Dynamic CRM 4 : Data Migration (part 4) - Creating a Data Migration
- Microsoft Dynamic CRM 4 : Data Migration (part 3) - Creating a CRM Adapter Publisher
- Microsoft Dynamic CRM 4 : Data Migration (part 2) - Scribe Workbench - Target Configuration
- Microsoft Dynamic CRM 4 : Data Migration (part 1) - Scribe Workbench - Source and Target Definitions, Source Configuration
- BizTalk 2006 : Using BizTalk Framework 2.0 Reliable Messaging (part 2) - Acknowledgement Verification
- BizTalk 2006 : Using BizTalk Framework 2.0 Reliable Messaging (part 1)
- Microsoft Exchange Server 2010 : Managing Transport and Journaling Rules - Setting Up Message Classifications (part 2)
- Microsoft Exchange Server 2010 : Managing Transport and Journaling Rules - Setting Up Message Classifications (part 1)
- Windows Server 2012 : Managing Users with Local Security and Group Policies (part 3) - Troubleshooting Group Policy Applications
- Windows Server 2012 : Managing Users with Local Security and Group Policies (part 2) - Configuring and Optimizing Group Policy
- Windows Server 2012 : Managing Users with Local Security and Group Policies (part 1) - Viewing Policies with the Group Policy Management Console, Creating New Group Policies
- Windows Server 2012 Administration : Creating Groups (part 2) - Populating Groups, Group Management
- Windows Server 2012 Administration : Creating Groups (part 1) - Domain Functional Level and Groups , Creating AD Groups
- Windows Server 2012 Administration : Windows Server 2012 Active Directory Groups
- Microsoft Exchange Server 2010 : Managing Connectivity with Hub Transport Servers - Messages in Flight
 
 
Most view of day
- Using Wireless Bluetooth Devices : Adding Bluetooth-Enabled Devices
- System Center Configuration Manager 2007 : Creating and Modifying Configurations (part 3) - Console Authoring - Settings
- Maintaining Security : Monitoring Your Security Settings, Configuring the Windows Firewall
- Sharepoint 2013 : Understanding Service Applications - A History of Service Applications in SharePoint
- Microsoft Project 2010 : Fine-Tuning Task Details (part 5) - Changing Task Types
- Designing and Configuring Unified Messaging in Exchange Server 2007 : Monitoring and Troubleshooting Unified Messaging (part 1) - Active Calls , Connectivity
- Microsoft Exchange Server 2010 : Getting Started with Email Archiving - Exchange Server 2010 Email Archiving - Policies
- Sharepoint 2013 : The Office JavaScript Object Model (part 2) - Functional Capabilities by Office Client,Mailbox-based Apps
- Windows Phone 8 : Orientation and the PhoneApplicationPage Class - Setting Page Orientation at Runtime
- Windows 7 Mobility Features : Other Mobile Features
Top 10
- Microsoft Project 2010 : Linking Tasks (part 8) - Auditing Task Links,Using the Task Inspector
- Microsoft Project 2010 : Linking Tasks (part 7) - Creating Links by Using the Mouse,Working with Automatic Linking Options
- Microsoft Project 2010 : Linking Tasks (part 6) - Creating Links by Using the Entry Table
- Microsoft Project 2010 : Linking Tasks (part 5) - Creating Links by Using the Task Information Dialog Box
- Microsoft Project 2010 : Linking Tasks (part 4) - Entering Leads and Lags, Creating Links by Using the Menu or Toolbar
- Microsoft Project 2010 : Linking Tasks (part 3) - Using the Start-to-Start Relationship,Using the Finish-to-Finish Relationship
- Microsoft Project 2010 : Linking Tasks (part 2) - Using the Start-to-Start Relationship,Using the Finish-to-Finish Relationship
- Microsoft Project 2010 : Linking Tasks (part 1) - Defining Dependency Links
- Microsoft Project 2010 : Defining Task Logic - Manipulating Your Schedule
- Microsoft Lync Server 2013 : Director Troubleshooting (part 3) - Synthetic Transactions,Telnet
 
 
Windows XP
Windows Vista
Windows 7
Windows Azure
Windows Server
Windows Phone
2015 Camaro