Upgrading to Windows 2003

 < Day Day Up > 

Upgrading to Windows 2003

This section covers the various aspects of the upgrade process.

Planning an Upgrade

To effectively plan for the change, you need to understand the differences between your current configuration and your Windows Server 2003 configuration. Moving from Windows NT 4.0, DNS becomes the primary method of name resolution, and your network administration becomes much more granular and localized. It might seem extremely complex at first, but good planning eliminates much of the difficulty. To effectively plan for these changes, find and update your network map to determine how and why your network looks as it does.

Along with assessing your network, review the applications that you plan to use after the upgrade. Use the review processes outlined in the next two sections.

Network Assessment

The following series of questions will give you an idea of how to conduct your assessment. Keep in mind that each environment is unique and may require additional considerations.

  • What domains do you have and why?

  • Does the structure work internally?

  • What changes could make network use easier?

  • Will certain changes make your network Administrators more efficient?

  • What are your security needs?

  • What are your bandwidth needs?

  • How do you use or plan to use the Internet within your organization?

Look at the entire network infrastructure to establish what improvements should be made before the upgrade begins.

Application Assessment

Look at your current applications and determine whether they will operate in a Windows Server 2003 environment or whether you need an upgrade or replacement. Ask yourself the following questions:

  • How are the applications used?

  • Which groups use them?

  • Will this make a difference in your network structure?

Are there similar applications in use elsewhere in your organization that are more likely to be compatible with Windows Server 2003? Take time to investigate Windows Server 2003, your hardware, and your applications.

note

Microsoft developed the Application Compatibility Toolkit to help users determine which applications in their environments support Windows Server 2003. You can obtain the associated whitepaper and download the utility from the Microsoft Web site at www.microsoft.com/windowsserver2003/compatible/appcompat.mspx.


Project Plan

The planning process for a project of this scope is a critical piece in its success. Make sure you take the following steps before embarking on the project:

  • Establish functional teams with experts in directory services; administration and management; and core OS, networking, applications, and hardware compatibility.

  • Have teams evaluate Windows Server 2003. Plan on four to six months to correctly plan your upgrade strategy, make clear assignments, and verify progress along the way.

  • Fix any problems in your Windows NT 4.0 and/or Windows 2000 environment and verify that your Windows Internet Naming Service (WINS) works properly.

  • Ensure that WINS is on your system until all clients are Active Directory (AD) aware.

  • Identify the resource domains to be collapsed into the AD domain structure, and check for duplicate names across the entire network.

  • Audit your security environment and determine how global groups can help with the upgrade process.

Upgrade Paths

It's also important that you understand the Microsoft supported upgrade paths for Windows Server 2003, as listed in Table 7.10.

Table 7.10. Supported Upgrade Paths to Windows Server 2003

Current Server OS

Upgraded Server OS

Windows 2000 Server

Windows Server 2003, Standard Edition

Windows 2000 Advanced Server

Windows Server 2003, Enterprise Edition

Windows 2000 Datacenter Server

Windows Server 2003, Datacenter Edition

Windows NT 4.0 Server

Windows Server 2003, Standard Edition

Windows NT 4.0 Enterprise Server

Windows Server 2003, Enterprise Edition


After you decide where you are, how you got there, and what is available, determine where you want to be and how to get there by asking these questions:

  • Who will upgrade first?

  • How will you determine when the next group is ready to upgrade?

  • What security issues are most important?

  • How long can you allow for the full upgrade?

After you know the answers to all these questions, develop a roadmap with clearly defined action programs to make sure you have a strategy that can work. Your strategy should include checking the HP Windows Server 2003 Web site on a regular basis for new information. HP Services can help you plan your upgrade to Windows Server 2003.

Decide the Correct Path for System Migration

Reasons to upgrade or to perform a new installation and other useful planning resources are available at the following areas of the Microsoft Web site:

  • For existing Windows 2000 environments : http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/win2k/w2ktows03-2.mspx .

  • For existing Windows NT 4.0 environments : http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/default.mspx .

Preparing for the Upgrade

To prepare for a successful upgrade, ensure that your server meets the system configuration and supported platform requirements and that you have all of the software and tools necessary to complete the tasks at hand. The following sections provide guidelines to help prepare you for this endeavor.

Supported Configurations

Windows Server 2003 should load and run on any ProLiant server that meets the recommended hardware configuration established by Microsoft. Carefully review the recommended system configuration and possible issues you might encounter. Performing due diligence optimizes your resources and testing scenarios.

ProLiant Installation and Upgrade Checklist

Before you begin the upgrade, ensure that you have access to the support software and other tools detailed in Table 7.11.

Table 7.11. ProLiant Server Windows 2003 Upgrade Checklist

Description

Comments

Location

Options ROMPaq

By option

http://h18007.www1.hp.com/support/files/server/us/index.html

SmartStart CD

Release 6.30 or later

http://h18023.www1.hp.com/support/files/server/us/smartstartinfo.html

PSP for Windows 2000

Release 6.30A

http://h18023.www1.hp.com/support/files/server/us/locate/1989.html

System Configuration Utility

Provided on the SmartStart for Servers CD release 5.50 (or earlier) and on the HP Web site

http://h18023.www1.hp.com/support/files/server/us/locate/1950.html

System ROMPaq

By server

http://h18023.www1.hp.com/support/files/server/us/romtabl.html

HP Smart Array Multipath Software v2.0

For customers with multipath hardware

http://www.hp.com/products/sharedstorage

HP Windows Server 2003Web site

For the latest information

http://h18001.www1.hp.com/ partners /microsoft/windowsserver2003/support.html

Internet access

For system updates

 

Minimum requirements met

 

See the "Recommended System Configuration" section earlier in this chapter.

Platforms supported

 

See Table 7.2 earlier in this chapter.

Sufficient backup media

Enough for a full backup and in excellent condition

 

Windows 2000 Primer Utility

Erases noncompatible ProLiant utilities

http://h18023.www1.hp.com/support/files/server/us/download/10776.html

Windows Server 2003 CD

 

See the "Planning an Upgrade" section earlier in this chapter for the upgrade path requirements before trying to upgrade to Windows Server 2003.

Windows 2003 support on third-party hardware

For hardware supported

http://www.microsoft.com/hcl/default.asp


 < Day Day Up > 


Windows Server 2003 on Proliants. Deployment Techniques and Management Tools for System Administrators
Windows Server 2003 on Proliants. Deployment Techniques and Management Tools for System Administrators
ISBN: B004C77T6A
EAN: N/A
Year: 2004
Pages: 214

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net