Windows
Microsoft Project Guide
Upgrading NT 4.0 Member Servers to Windows 2000
Technical Staff
Table of Contents
Introduction 3
Assumptions 4
Step 1: Review Project Management Staff Document 5
Step 2: Planning Worksheets 6
Step 3: Prior to Upgrade 7
Step 4: Confirm Findings 8
Step 5: Draft Upgrade Plan 9Document Current System Configuration 9
Contingency Plan 9
Set Up Test Environment 10
Schedule Downtime 10
Step 6: Read Guide to Upgrading 11
Step 7: How to Upgrade a Windows NT Server 12
Before You Begin 12
Prepare Your System 14
Start the Upgrade 15
Step 8: Troubleshooting 16
Step 9: Post-upgrade Installation Tasks 17
Test Network Connectivity 17Test File Shares 17
Test Printer Shares 17
Test Web Server 17
Step 10: Install Latest Service Packs, Rollups and Patches 18
Additional Resources 19
Introduction
The purpose of this document is to help you gain the technical understanding needed to implement Microsoft® Windows® 2000 at your customer’s site. The information covered in this project guide can be used tosuccessfully plan for and upgrade either a Microsoft® Windows® NT 4.0 stand-alone server or a member server to a Microsoft® Windows® 2000 Server, since they are similar. Customer scenarios include upgrading a server that functions as a file and print server or a Web server. Upgrading a Windows NT 4.0 Server that is configured as a domain controller is not covered in this guide.
Please provideyour comments to Microsoft Partner Feedback to let us know how these guides helped you or how we can improve them.
Assumptions
The scope of this project guide includes the following assumptions for the upgrading of a Windows NT 4.0 stand-alone or member server to a Windows 2000 Server:
➢ This guide covers stand-alone or member server upgrades only. The Windows 2000 Server upgrade processfor a PDC or BDC is not addressed by this project guide. See the Deploying Active Directory Project Guide to learn how to upgrade a Primary or Backup Domain Controller to a Windows 2000 Server and Active Directory.
➢ The Windows NT 4.0 stand-alone or member server to be upgraded is only configured for file and print or Web services. There are no additional services such as WINS, DNS, or DHCPconfigured on the stand-alone or member server that is targeted for upgrading.
Follow the steps below to successfully plan for and upgrade to Windows 2000.
Step 1: Review Project Management Staff Document
Planning is one of the most important functions you can fulfill as a technical resource. Read the Project Management document included in this Project Guide and in the General ProjectGuide to learn how to properly plan for and upgrade a Windows NT 4.0 stand-alone or member server to Windows 2000. Launch the Project 2000 template to use as a guide to creating your own project methodology.
Step 2: Planning Worksheets
Make sure you download the Appendix A - Sample Planning Worksheets. When deploying Windows 2000, you may have several deployment projects to plan andcoordinate. This appendix provides planning worksheets that you can use to deploy Windows 2000 in the most cost-effective and efficient manner for your organization.
Step 3: Prior to Upgrade
Before running the Windows 2000 setup program, it is important to conduct a hardware and software inventory of the systems you are planning to upgrade to Windows 2000 Server. Use the following questions asguides when conducting the inventory:
➢ Who is the vendor, and what is the make and model of the server hardware?
➢ How much physical memory is installed?
➢ What type of Network Interface Card (NIC) is installed?
➢ Does your system contain non-Plug and Play ISA devices?
➢ Is there an uninterruptible power supply (UPS) connected to the server?
➢ What type...
Regístrate para leer el documento completo.