Migrating to a Scalable Windows 2003 Server Environment

Migrating to a Scalable Windows 2003 Server Environment

When planning a migration to Windows Server 2003, one of the key components is to design and implement a new Windows 2003 Active Directory infrastructure and forest that is scalable and flexible enough to meet an organization's existing and future business needs.

To meet this goal, it is important for organizations to understand the current Windows NT 4.0 environment beyond their basic Windows NT operating systems. Knowing and understanding all existing hardware and third-party applications in use can assist an organization in avoiding setbacks and disruptions when planning and migrating to Windows Server 2003 and Active Directory.

Understanding these components and how they can affect a migration and Windows Server 2003 will assist administrators and planners in ensuring that a new Active Directory infrastructure is fully functional and scalable to an organization's future plans and needs.

Planning for Future Hardware Needs

Before planning a migration, it is important to know whether existing hardware currently in use in the network environment can support the various editions of Windows Server 2003 that will be implemented as part of the migration.

Begin planning your migration by assessing future hardware needs and conducting a detailed inventory of all existing server hardware that will be migrated to a new Windows 2003 Server family platform.

Planning Hardware Upgrades

Plan hardware upgrades according to server roles and installed applications that might require additional memory or faster processor speeds to ensure optimal server performance. Combine your software and hardware inventory to plan and deploy a scalable optimal performing server hardware environment.

Begin by creating a detailed and documented hardware inventory to assist in identifying existing server hardware. The inventory can be used to identify server hardware that does not meet the Microsoft Windows Server 2003 family minimum hardware requirements. Review the requirements in Table 14.1 to determine if your Windows NT 4.0 installations meet the minimum Microsoft hardware requirements for installing Windows Server 2003.

Table 14.1. Windows Server 2003 Minimum Requirements

Windows Server 2003	Processor and Speed Minimum	RAM	Required Disk Space for Installation
Web Edition	133MHz	128MB	1.5GB
Standard Edition	133MHz	128MB	1.5GB
Enterprise Edition	133MHz	128MB	1.5 GB
Data Center Edition	400MHz	512MB	1.5 GB

Using the System Compatibility Checker

Another method to determine hardware compatibility is by using the Compatibility Check Tool available on the Windows Server 2003 installation CD-ROM. This tool can be run directly from the Windows Setup on the installation CD-ROM and does not require administrators to install Windows Server 2003.

Software Compatibility List

You can also review the Windows Server 2003 Family hardware and software compatibility list on the Microsoft Web site.

Processor Compatibility

Windows 2003 Server might not upgrade Windows NT systems with multiple Pentium Pro or Pentium II processors correctly. Windows Server 2003 setup and the Compatibility Check will identify if dual processors and multiple processor servers will only run with one processor after the upgrade is complete. More information on the subject can be found on the Microsoft System Requirements Web site at www.microsoft.com/windowsserver2003.

You can use the autorun feature built into your server systems to launch the Windows Server 2003 setup screen, which will enable you to navigate to the Compatibility Check Tool. If your server hardware does not support the autorun feature, or it has been disabled in the server bios, the compatibility check utility can be run from the command prompt or Windows run option. To run the compatibility check tool, at the prompt type: D:\I386\winnt32/checkupgradeonly (where D: represents the CD-ROM drive letter of the server you are checking).

Supporting Third-Party Software Applications

One key component to a successful migration is identifying all applications currently installed and present in the existing Windows NT 4.0 environment. By identifying all applications in use as well as specific applications that might no longer be in use, administrators can have a full understanding of the application migration requirements they might be challenged with. Knowing what applications are to be migrated and what the specific requirements are for compatibility with Windows Server 2003 will assist you in avoiding any issues with application functionality after applications are migrated to Windows Server 2003 and Active Directory.

One challenge in identifying these applications is the method you should use to accomplish this large task. Organizations with Microsoft Systems Management Server (SMS) can produce a detailed inventory of applications using the collection of data obtained through the software inventory component of SMS.

Application Compatibility Tool Kit

Download the Application Compatibility Tool Kit from the Microsoft Windows Server 2003 Web site at http://www.Microsoft.com/windowsserver2003/compatible/appcompat.mspx.

For organizations that do not have Systems Management Server (SMS), another method to inventory software in a Windows NT 4.0 environment is to use the tools provided in the Application Compatibility Tool Kit for Windows Server 2003.

Using the Compatibility Tool Kit Analyzer

The Application Compatibility Tool Kit (ACT) is a deployment tool provided by Microsoft to assist IT staff in identifying and testing applications for compatibility with Windows Server 2003. There are three components to the ACT:

• Microsoft Application Compatibility Analyzer is a tool used to remotely gather all installed programs within a Windows NT network. This tool automatically creates an inventory of all installed programs without requiring a management tool such as SMS.

• Windows Application Verifier can be used to identify compatibility issues with existing and new application to be installed on Windows Server 2003.

• Compatibility Administrator is a complete tool that can determine the necessary fixes required for application support with Windows Server 2003. The compatibility administrator can also be used to create packages of fixes stored in a database that can then be distributed to application servers or computers on the network.

Migrating to a Flexible Active Directory Forest

After the discovery of hardware and software has been completed and documented, the next step is to design and implement a scalable Windows 2003 Active Directory environment. By designing and implementing a Forest Root that is scalable, organizations can leverage the flexibility and migrations options when migrating to Windows Server 2003.

Logging Tips

Use the command line tool Collector.exe to inventory systems applications and write information to a log file. By default, the Collector tool writes information and places the log file on the system desktop in which the tool is being run. Use the -o switch to specify an alternative location to write the collectors logs; for example, Collector.exe -o c:\AppInfo\Collect.log .

You can begin understanding how to implement scalability into a migration and Active Directory by understanding the different migration paths available when upgrading from Windows NT 4.0.

Advance Active Directory Design

To better understand options that can be applied to your Active Directory design, review Chapter 10, "Advanced Active Directory Design."

The first option is an in-place domain upgrade. This method is the most restrictive of the three methods ; however, it is best used for organizations that want to maintain the existing domain model.

The second option is a domain migration; this method is best implemented by organizations that want to migrate all existing domain objects to a single newly created Active Directory domain.

The most effective and flexible method is a domain consolidation. When performing a domain consolidation, a newly created Active Directory Root is implemented and connected to the existing NT domain using domain trust.

This option provides the most migration flexibility and a broader range of migration options. By leveraging all the functionality available in the first two migration paths a domain consolidation is ideal for organizations that want to implement change and maintain certain existing domain configurations (see Figure 14.1).

Figure 14.1. Consolidating Windows NT domains.