Previous Table of Contents Next


Chapter 2
Windows NT Project Planning

Bill Camarda

This chapter is intended to serve as a reference for the many organizations planning a migration to Windows NT. It describes how to identify resources to assist in the migration process, evaluate the installed base, choose vendors to assist in the transition, and planning a test run — all of the steps necessary to prepare for a full-scale rollout.

INTRODUCTION

This chapter, intended for organizations that are planning a migration to Windows NT, covers:

  Identifying the organization’s goals for deploying NT
  Identifying resources that can assist in the migration process
  Evaluating the organization’s installed base
  Choosing vendor partners to assist in the migration
  Planning a pilot rollout
  Running a full-scale rollout

ESTABLISHING BUSINESS AND TECHNICAL GOALS FOR NT DEPLOYMENT

Before beginning a migration to Windows NT, it is important to understand what the business and technical goals are.

Business Goals for NT Deployment

Exhibit 1 lists some possible business goals for an NT project, along with the deployment issues that will need to be addressed to reach those goals.

Technical Goals for NT Deployment

Exhibit 2 lists some possible technical goals for an NT project, along with deployment issues related to each of these goals.

Exhibit 1. Business Goals and Deployment Issues

Goal Deployment Issues

Improve internal communication to shorten product delivery cycles Using Internet Information Server (IIS) to deploy an intranet; choosing the appropriate strategy for directory services (Windows NT Directory Services, Distributed File System, planning for Active Desktop, or integrating Novell Directory Services)
Improve communication with suppliers and customers to enhance organizational responsiveness Using firewalls, Windows NT name resolution tools, and PPTP tunneling to build extranets that encompass business partners
More effectively leverage the corporation’s data for decision-making Architecting the NT network to support database mirroring and query-intensive OLAP network traffic
Reduce costs Standardized hardware and software configurations, Zero Administration for Windows, NetPCs, support, training, and Help Desk issues

Exhibit 2. Technical Goals and Deployment Issues

Goal Deployment Issues

Providing a standard user environment that simplifies maintenance and training Zero Administration Windows; system profiles; standard hardware configurations
Centralizing security while giving users a single log-on to all network resources Domain planning; user account planning; Distributed File System
Making all users accessible through a single enterprisewide network directory Choosing between Windows NT Directory Services and the long-term Microsoft Active Directory strategic direction; or Novell’s robust NetWare Directory Services (NDS).
Preparing for growth by maximizing scalability Choosing multiprocessor hardware and considering new clustering options, such as Microsoft Cluster Server (formerly known as Wolfpack)
Reducing the risks of server and network failure Choosing NTFS file systems, RAID disk solutions and server mirroring, and architecting your network with adequate backup domain controllers (BDCs)

Building the Migration Team

Once the goals have been established, the next step in planning a smooth migration to NT Workstation and/or NT Server is to divide the responsibilities. Most large organizations identify several teams, each with a leader and a specific role in planning and deploying Windows NT. These teams may include:

  A planning and coordination team that includes the project leader and representatives of each other team.
  An executive team that includes the IT organization’s leader (or project manager responsible for the NT deployment); others with authority over relevant IT procedures; finance management; and executives from lines of business that will be impacted by the NT deployment.
  An installation team consisting of technicians who will actually install NT, as well as technical experts who can evaluate and test configurations for performance and compatibility.
  Training and/or support team(s) that may include help desk representatives, internal trainers, those responsible for hiring external trainers, and decision-makers responsible for providing adequate resources to frontline support staff.

In organizing these teams, it is all too common to disregard the central role of users: the people who will ultimately have to be productive with NT on a day-to-day basis. Bringing user representatives into the process early improves the likelihood of achieving wholehearted buy-in, and substantially improves a company’s chances for success.

IT Qualifications Needed for the Deployment Team

One way to identify the right internal and external resources for the NT deployment team is to work with Microsoft Certified Professionals (MCPs). In addition to hiring certified professionals, an organization may decide that certifying more of its existing IT staff as NT experts should be an important element of the deployment process. A company might consider providing training for installers, system administrators, support staff, and anyone else with day-to-day responsibilities for Windows NT systems.


Previous Table of Contents Next

Copyright © CRC Press LLC