Content area
Full text
Windows NT to Windows Server 2003 migration is a major IT infrastructure project. Start by scoping out the costs and benefits of the migration project for your preliminary scope and budget statement.
Windows NT is near the end of its days. Windows 2003 is beckoning. This is a major IT infrastructure project that is going to require understanding and buy-in across the enterprise. Start by scoping out the costs and benefits of the migration project so that you can start work on a preliminary scope and budget statement.
The Move Is On
With Microsoft ending support for Windows NT at the end of 2004, Gartner Group estimates that as many as 70 percent of Windows 2003 deployments will be for migrations from Windows NT.
Scoping the Costs and the Benefits
The costs of your Windows 2003 implementation will become readily apparent as you scope out the requirements of the migration. You will start by auditing your current hardware and network services, and then figure out what upgrades will be necessary to get your infrastructure Windows 2003-ready. You will also need to consider licensing, training, and support issues to determine costs.
Benefits may be more difficult to quantify; however, the benefits side is critical. In stating the goals of your migration project, you will want to state how money will be saved and efficiency increased. The end of Windows NT is an impetus to change, but not a value-based argument for moving to Windows 2003.
Migrating From
Windows NT to Windows 2003
This article is the second in a series that will look at issues in planning a migration from Windows NT 4.0 to Windows 2003.
Last issue, we looked at the (http://www.infotechadvisor.com/ search/sub_search.cfm?documentID=4957) migration alternatives for moving off Windows NT. Topics to be covered in future articles will include (but are not limited to):
New Active Directory features.
Fallback...