Previous Table of Contents Next


On the server side, Microsoft has announced especially close partnerships with Digital (DEC) and Hewlett-Packard. To varying degrees, these relationships have led these vendors to deliver more fully integrated solutions for NT deployment. For example, Digital already has 1400 engineers with NT certification from Microsoft. Digital’s service offerings for NT include:

  Legacy NOS Migration to Windows NT services, including methodologies for migrating user files, access privileges, print services, and other features of legacy NOS environments, including NetWare, Banyan VINES, DEC PATHWORKS, IBM LAN Server.
  Building NT Applications for the Enterprise, services to plan, design, and implement client/server computing built on Windows NT.
  Software Support for Windows NT, services to provide support for Windows NT environments, with a selection of response times and problem-resolution capabilities.
  Installation and Startup for Windows NT and Windows NT Clusters, services to rapidly install, configure and implement NT servers and clusters.

Hewlett-Packard’s recent partnership with Microsoft has thus far led to improvements in scalability on Intel-based servers, as well as a new family of Business Recovery Services intended to help companies prevent and recover from failures associated with NT servers.

It is important to note that while Microsoft’s NT partnerships with Digital and Hewlett-Packard have been the most prominent to date, other leading vendors now offer extensive support for Windows NT. To cite just two examples, Unisys recently established the Enterprise NT Services organization, intended to offer a full suite of services for deploying mission-critical applications on NT systems; NCR also offers substantial Windows NT consulting services.

On the workstation side, Microsoft and Intel lead the NetPC effort intended to lower the cost of administration; partners in this effort include Compaq, Dell, Digital, Gateway 2000, Hewlett-Packard, Packard Bell NEC, and Texas Instruments.

As already mentioned, standardizing on a single provider of PCs, a single provider of servers, and a single provider of network interface cards can simplify management tasks for years to come. Whether preparing a formal RFP, or requesting proposals on a less formal basis, above all it is important to be explicit about what is expected from the vendor. In addition to cost, the following items should be considered when making choices:

  A track record with your company or companies like yours
  Availability of a trustworthy single point of contact
  Ability to deliver an end-to-end solution
  Support commitments, both for hardware and for Windows NT
  Availability of specific technical resources where and when you need them
  Product delivery dates and a vendor’s track record in meeting them — especially if notebook PCs are involved
  Contract flexibility (e.g., the ability to substitute more advanced technologies for those covered in the contract)

Testing Standard Configurations

Once IS has established standard configurations of both existing and new equipment, they should run detailed tests of:

  The NT installation process and automated batch scripts
  Network connectivity
  Applications software
  The uninstall process (restoring previous operating systems on upgraded computers)
  Disk space variables (both for installation and swap files)
  Local and server-based administration tools

IS may find that it needs to make adjustments to the standard client configuration to improve performance, compatibility, stability, or user convenience.

PLANNING AND MANAGING A PILOT ROLLOUT

In most organizations, the next step is to perform a pilot rollout in a small department or division. Ideally, choose an organization that is open to new technology and not stressed by a major project deadline or recent downsizing. (Obviously, some organizations may not have this luxury.) A typical pilot rollout may include the following steps:

  Prepare a detailed logistical plan for the pilot rollout, including tested scripts for automated installation from distribution servers.
  Prepare and implement a support plan, so users have immediate access to assistance when they need it.
  Plan a schedule (e.g., how many systems can be upgraded per day, and how long the pilot rollout will take).
  Notify users well in advance of the installation.
  Develop training materials that reflect both the performance of standard NT tasks and concerns unique to your company (e.g., logons, file locations, custom applications, etc.).
  Schedule training.
  Perform a verified backup, a virus-check, and disk defragmentation on all pilot machines that will be upgraded to Windows NT.
  Virus check all pilot machines prior to installation.
  If necessary, upgrade BIOSes, memory, or other hardware prior to installation.
  Make sure NT driver software is available for installation wherever needed.
  Run the installation at a time least likely to interfere with deadlines.

Once the pilot installation has taken place, IS should:

  Follow up to ensure all systems are working properly.
  Stay in close contact with all members of the pilot group to identify problems, questions, and other issues.
  Respond to user concerns and carefully track the changes that users request or require.
  Assign technicians to check real-world performance against expectations, so adjustments can be made, if needed, before a full-scale rollout.
  Compare schedules and costs against expectations, so budgets and timeframes can be adjusted for the full-scale rollout later.

PREPARING FOR FULL-SCALE DEPLOYMENT

Now that the pilot rollout has been conducted, IS can begin to prepare for the organizationwide rollout by:

  Creating budgets and schedules that reflect the actual experience.
  Revising the company’s IT procedures to reflect the changes that NT will require, and notifying users where necessary.
  Performing a complete systems inventory and storing the information in a centralized database that can be updated to reflect changes to individual systems.
  Hiring or reassigning any additional staff needed for the full-fledged rollout.
  Rolling out Windows NT using the procedures used in the pilot rollout — adapted, of course, to reflect any necessary changes.

CONCLUSION

This chapter has discussed many of the issues involved in successfully rolling out Windows NT Workstation. But Windows NT is inherently a networked operating system, designed for use in highly distributed environments. It is important to review the critical networking issues associated with planning an NT deployment — including what is needed to architect Windows NT domains that will serve your company well for years to come.


Previous Table of Contents Next

Copyright © CRC Press LLC