Chapter 1 - Deployment Strategy

Article
02/20/2014

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

This chapter provides information to help you define the best deployment strategy and plans for your organization. Because every organization is unique, not all of the information presented here may apply to you. We strongly recommend that you thoroughly test these guidelines in a pilot test environment before rolling out Microsoft® Windows® 98. If you are comfortable with the early planning phases of deployment, you can skip ahead to "Deciding on the Preferred Client Configuration" later in this chapter.

Overview of a Deployment Process

There is more than one way to deploy Windows 98 in an organization. This chapter describes the following deployment process for Windows 98:

Reviewing Windows 98
Preparing the Planning and Support teams
Identifying the preferred network-client configuration
Performing lab tests of the client configuration
Planning the pilot rollout
Conducting the pilot rollout
Finalizing the rollout plan
Rolling out Windows 98

For the purpose of illustrating this deployment process, this chapter uses five teams: Executive, Planning, Installation, Support, and Training. Your organization may or may not have teams that resemble the ones presented here, but the information presented here should help you come up with your own deployment process and teams.

The Executive team includes the deployment project manager (usually the head of the Information Systems department) and members of the executive committee of the corporation. This team must include one or more individuals with decision-making authority over company policies and procedures.
The Planning team includes the deployment project manager, key Installation team members, and a representative from each of the Support and Training teams.
The Installation team includes technicians and individuals who will be conducting the installation. This team must include a specialist in 32-bit applications who can evaluate the proposed Windows 98 configuration for compatibility.
The Support team includes staff of the help desk or Support department, and select individuals from the Planning team. This team develops a plan for supporting Windows 98 during and after deployment, integrating new methods and processes as needed into the existing support scheme.
The Training team includes individuals responsible for user training.

Reviewing Windows 98 Features

In the first phase of the deployment process, the Executive and Planning teams learn about Windows 98 features and benefits. Those responsible for planning and conducting the rollout learn how Windows 98 helps reduce support costs and increase business profitability. Publications available from Microsoft Press® and from independent industry analysts provide the information you need.

Preparing the Teams

The team preparation phase involves gathering the resources, including equipment, software, and staff, to properly plan for testing and evaluating Windows 98. Members of the Support team should receive training during this phase.

Acquiring Staff and Software

The deployment project manager participates in the Executive team and leads the Planning team. Although this individual is usually the head of the Information Systems department, the executive committee may find a more appropriate individual, depending on the organization.

When setting up the Planning team, it is important to include a set of individuals representing the groups involved in the deployment process. This includes people from the Corporate Support and Employee Training departments, the Corporate Standards Committee, and key Installation team members. Individuals from the Finance and Accounting group will need to take part in planning and evaluation later on, but need not be assigned to the team for the full duration of the deployment process.

Your Installation team should include an applications expert who can evaluate 32-bit applications run with Windows 98.

Obtain Windows 98 during this phase. Microsoft recommends that you purchase the compact-disc version, so that you can use the administrative software tools not provided on the floppy disks.

Conducting a Sample Inventory

You must survey a representative sample of your network to identify the hardware and software typically used on client and server computers. By doing this sample inventory of your company's active equipment, you can accurately simulate the organizational environment in the lab. Such a simulation helps you make broad decisions about your company's computing infrastructure, such as choice of protocol or the default desktop configuration as it pertains to applications.

Software management tools are available to query computers on the network for hardware and software configurations. For detailed information about a large number of computers on a network, use a system management program, such as Microsoft Systems Management Server, to conduct the inventory.

Testing Lab Setup and Equipment

To evaluate and test the Windows 98 installation process effectively, set aside enough physical space and assemble a sufficient number of computers to test everything from automated Setup to hand-tuning options for the local computer. In addition, if your network environment includes the use of portable computers that dial in to the company, or if you use additional servers or mainframe computers for business data, make sure that the lab computers have full access to the network and an analog phone line.

It is important that you test and implement all Windows 98 features comprehensively in the lab with all mission-critical and non-critical business applications before moving to the pilot installation.

Training the Teams

By reviewing specific portions of the Microsoft Windows 98 Resource Kit, the Installation and Planning teams can gain an extensive understanding of Microsoft Windows 98 features and functionality. A review of the Getting Started guide included in the box and of the chapters contained in Part 1, "Deployment and Installation" of the Microsoft Windows 98 Resource Kit, can provide the teams with the information necessary to evaluate product features for system configuration.

Support team members must become familiar with all information in the Microsoft Windows 98 Resource Kit to prepare for their role in the deployment process. For extensive training, team members can receive instruction at a Microsoft Authorized Technical Education Center (ATEC) and participate in the Certified Professional program. Call (800) SOLPROV or (800) 765-7768 for information about authorized training offered for Windows 98 and the Certified Professional program, and for referral to a local Microsoft Solution Provider ATEC.

For additional information about Windows 98, particularly the background of its design and the history of its development, team members can read Inside Windows 98 from Microsoft Press. This book contains guidelines and tips for applications developers working with Windows 98.

For other training information, see Appendix I, "Windows 98 Resource Directory."

Deciding on the Preferred Client Configuration

Detailed analysis is required to determine your preferred client-computer configuration. Starting with the ideal configuration, which uses the most functional and best-performing client software, evaluate each feature against your organization's needs and environment to determine whether the feature is appropriate and compatible. If you are considering different configuration alternatives, repeat this evaluation for each configuration.

The following sections describe feature options and decisions to evaluate in specifying the network client configuration.

Configuration Layout

When deciding where to place Windows 98 files, consider how the computers will be used, and evaluate the benefits of each placement option. Determine whether the computers are personal workstations, portable computers that occasionally connect to the network, or computers that are shared by more than one person.

Key Features of the Ideal Configuration

This section provides detailed discussions of the features that might be included in an ideal network client configuration.

Using a 32-bit, Protected-mode Network Client

For best performance, select a network client that uses a 32-bit redirector for network access. Windows 98 includes the 32-bit Microsoft Client for NetWare Networks and the Client for Microsoft Networks; each of these has a 32-bit redirector. The benefits of using a 32-bit, protected-mode client include the following:

Provides for easy installation and configuration using built-in Windows 98 tools.
Uses no real-mode memory.
Provides faster data I/O across the network.
Offers greater stability than real-mode redirectors.
Allows more than one redirector to be run at a time, and thereby enables access to servers for multiple networks without having to reload the operating system for a new network client.
Makes networking seamless in the Windows 98 user interface; users can browse the server for multiple networks in Network Neighborhood, all within the same name space—they do not need to know which type of network they are browsing.

If you are using another type of network, contact your network vendor regarding the availability of a 32-bit, protected-mode network client.

Using a 32-bit, Protected-mode Protocol

If you select a 32-bit, protected-mode network client, by default Windows 98 also sets up a 32-bit, protected-mode protocol. Even if you are running a real-mode client such as the Novell 3.x workstation shell (NETX) with a real-mode implementation of Internet Packet Exchange/Sequenced Packet Exchange (IPX/SPX) to access NetWare servers, you can still load the 32-bit version of the Microsoft IPX/SPX-compatible protocol. The benefits of adding the protected-mode protocol are better performance and better stability for network communications to servers that are not running NetWare (for example, computers running Windows 98 or Microsoft Windows NT®).

In addition, for protocols, such as Transmission Control Protocol/Internet Protocol (TCP/IP), the Microsoft 32-bit version enables additional functionality (such as the ability to use Dynamic Host Configuration Protocol [DHCP] and Windows Internet Naming Service [WINS] servers) that dynamically set the Internet Protocol (IP) addresses and resolve computer names for client computers on the network. Each protocol has a number of benefits, as discussed in Chapter 15, "Network Adapters and Protocols."

Using the Latest Network Adapter Drivers

For best performance, use the latest network adapter drivers available. These should be network driver interface specification (NDIS) 5.0 – compatible drivers that provide Plug and Play capabilities. Such drivers take up no real-mode memory and can be loaded or unloaded dynamically as required.

The only instances in which you would not use the latest drivers are:

The newest driver is not available for your network adapter.
Your site requires Open Datalink Interface (ODI) cards and drivers.

Recommended Features for Network Clients

The following optional features are recommended for your preferred configuration. These features define how Windows 98 will be installed and administered in your organization. Some features that enable centralized and remote management of Windows 98 are much easier to install initially, than they are to roll out after Windows 98 has been installed. Microsoft recommends that you include these remote management features, whether you intend to use them or not. By doing this, the potential benefits of having them installed outweighs the cost of including them in your initial installation.

Using Group Policies

For centralized administration of client computers, you must enable Group policies. Group policies allow you to centrally edit and control individual user and computer configurations. For example, if you want to place a custom Start menu on user desktops or limit access to Control Panel options, Group policies make it easy to do so for a large number of users from a central location.

For information on the types of restrictions available and for details on how to implement system policies, see Chapter 8, "System Policies."

Using User Profiles

There are two reasons for enabling User Profiles. First, User Profiles must be enabled for Group Policies to work. Second, with user profiles, users can use personalized desktop settings each time they log on to a computer. This is especially useful for multiple users sharing a single computer who want to customize their desktops and have those custom settings loaded at logon. Conversely, a single user can move between computers using the same profile if the administrator stores that profile on the server. An administrator can also take advantage of profiles to require that a mandatory desktop configuration be loaded each time a user logs on. The ability to change profile settings can be controlled by the administrator. For information on how to use user profiles, see Chapter 7, "User Profiles."

Using the Windows Script Host

The Windows Script Host provides a low-memory scripting host that is ideal for non-interactive scripting needs, such as logon scripting or administrative scripting. In combination with Group Policies the Windows Script Host enables comprehensive configuration management of the Windows 98 desktop.

Enabling Remote Administration

To administer a computer's registry remotely, first install the network service called Microsoft Remote Registry Service, enable user-level security, and enable the Remote Administration feature. Remote administration capabilities allow you to conduct a variety of tasks remotely over the network such as administering the file system, sharing or restricting directories, and querying and making changes to the registry. If you plan to do any of these tasks, be sure to enable this feature during Windows 98 installation. For information on adding the Microsoft Remote Registry Service and other network services using Microsoft Batch 98 and INF Installer (Infinst.exe), see Chapter 3, "Custom Installations."

You should not enable Remote Administration if you do not need these services, because doing so causes unnecessary, extra processes to run on the client computer and on the network. These extra remote services could theoretically* *be used by individuals on the network—provided they knew the appropriate password—to access information on client computers. However, Windows 98 comes with security capabilities to protect against unauthorized use of the Remote Registry Service. For more information, see Chapter 23, "System and Remote Administration Tools."

Using User-level Security

User-level security is based on user account lists stored on Windows NT or Novell NetWare servers. The user accounts specify which users have access rights on the network. Windows 98 passes a user's request for access to the servers for validation. Pass-through user-level security protects shared network resources by requiring that a security provider authenticate a user's request to access resources.

User-level security is required for remote administration of the registry and for network access to full user profiles. For more information about implementing security in Windows 98, see Chapter 9, "Security."

Performing the Lab Test

This phase involves four significant efforts: preparing the site, conducting the installation, testing the installation, and restoring the system.

Preparing the Test Site and Equipment

Preparing the site involves ensuring that the location of each computer, the computer itself, and the hard disk in particular are all ready for Windows 98 to be installed. In terms of the physical site, make sure that you have the appropriate jacks for connecting to the network.

For the computer itself, make sure that it has the appropriate hard disk space, RAM (16 MB minimum), and processor (486DX/66 MHz minimum) to run Windows 98.

In addition, run virus detection, disk scanning, and defragmentation programs on the computer to correct any problems before installation. Although the computer may appear to be operating properly, software upgrades often uncover hardware or software problems because of the way they read and write data to the hard disk. Correct any such problems before installing Windows 98.

When preparing the site, be sure to back up critical data, the registry, and configuration files for the system, in case the installation fails or you need to revert to the previous operating system for some reason. This includes backing up INI files (such as System.ini), GRP files, Autoexec.bat, Config.sys, and all key data files. As an added precaution, create a system startup disk and back up the Windows and MS-DOS® directories and all the files in the root directory.

If you need to automate the restoration, consider using a commercial backup program instead of copying the files by hand.

Caution Replacing configuration files alone, such as INI files, is not sufficient to restore your system.

For more information on system requirements, backup procedures, and other preparation steps for installing Windows 98, see Chapter 2, "Setting Up Windows 98."

Installing Windows 98 on Test Computers

Before setting up Windows 98 for the first time, verify that the computer's existing network is working properly. Then use Part 1, "Deployment and Installation," in the Microsoft Windows 98 Resource Kit to help you install and configure Windows 98 correctly Chapter 3, "Custom Installations," includes instructions on how to customize the installations using setup scripts. Take note of which options you want to predefine as entries for the Msbatch.inf file used for the setup script.

Testing the Installation

After you have set up a computer with Windows 98, you must run a variety of tests to make sure that it runs correctly on your network and that you can still perform all your usual tasks. Use your own testing methodology, or test the following to verify correct system operation:

Connect to and browse the network.
Set up a printer and test printing to local and network printers.
Open, run, and close applications on both the client computer and the server.
Shut down completely.

Make sure to test all mission-critical applications for proper function. If you encounter problems, try removing related features from the proposed configuration as a solution. Document any changes made to the original configuration.

If the preferred client configuration works as expected, you may also want to conduct additional testing of the optional software features and components in Windows 98. This can help you determine whether you are running Windows 98 optimally. For this kind of testing, conduct side-by-side evaluations on two computers, changing individual features on each one, to determine the following:

Performance in terms of responsiveness and throughput
Ease of use
Stability
Compatibility
Functionality

To evaluate network client software for Novell NetWare, run your network performance tests in the following configurations:

Windows 98 as a new installation using all protected-mode components, Microsoft Client for NetWare Networks (included with Windows 98), and the Microsoft Service for NetWare Directory Services client, if you are connecting to Novell 4.x servers that do not have bindery-emulation enabled.
Windows 98 added to an existing installation of Windows 3.x and NetWare, using Client for NetWare Networks and protected-mode networking support components (NDIS adapter drivers).
Windows 98 using Novell Client for Windows 95/98 and protected-mode drivers.

Perform several common tasks such as connecting to the network, administering a remote NetWare server, and so on, to test for ease of use. Similarly, run any business-specific NetWare applications under Microsoft Client for NetWare Networks to make sure that they are compatible. Any stability issues should become apparent during this testing.

When you have identified a configuration that performs well during testing, test the same configuration using other hardware from your company.

See Part 3, "Networking and Intranets," in the Microsoft Windows 98 Resource Kit to understand the differences in functionality between network clients.

Testing the Restoration Process

After thorough testing of the preferred client configuration, completely restore one of the test computers to the previous client configuration, and document the process. The degree to which you need to test and restore the computer depends on the tools available. Chapter 5, "Setup Technical Discussion," documents how to remove Windows 98 and restore the previous operating system manually.

Planning the Pilot Rollout

This phase involves three major efforts: automating the installation, documenting the logistics of the pilot installation, and preparing the user training plan. These efforts are a combination of planning and lab-testing work.

Installing the Source Files for Setup

Designate a network server that will be used as the source file for installing Windows 98 over the network using custom setup scripts, and install the Windows 98 source files on a server.

For more information on installing Windows 98 over the network using custom scripts, see Chapter 3, "Custom Installations." Document any changes to this process.

Automating the Installation

Automating the installation is a key step in reducing the cost of migration. By creating a setup script with predetermined answers for installation questions, the installation process can run from start to finish without user intervention. It is also possible to "push" the installation from the server, so that you can install Windows 98 on an individual personal computer without ever touching the computer. This automation work is done in the lab, prior to conducting the pilot rollout.

Automating the installation consists of creating a setup script, setting up Windows 98 on the server, and creating a push installation process. With a setup script you can perform a hands-free installation, so that the user need not respond to any prompts or even touch the computer during Windows 98 Setup.

Installing Windows 98 over the network requires that you install the Windows 98 source files on an installation point in a network server. Installing Windows 98 source files on the server is the simple process of copying the Windows 98 folder from your Windows 98 compact disk to an installation point in a network server.

Depending on the common network configuration at your site, you may determine that you need to remove a line from one or more configuration files as a global procedure before starting Windows 98 Setup. For example, you may want to use a protected-mode protocol such as Microsoft TCP/IP during Setup instead of the real-mode version of TCP/IP currently used on the target computers. In addition, users may be running certain terminate-and-stay-resident (TSR) programs or applications that should be closed before running Windows 98 Setup. In these cases, you can modify Netdet.ini on NetWare networks as described in Chapter 17, "Windows 98 on Third-Party Networks." On other networks, including Microsoft networks, modify the [Install] section of your setup script to automate these changes. For more information, see Appendix D, "Msbatch.inf Parameters for Setup Scripts."

In addition, you may want to manually add other files to the installation point on the server, such as custom bitmaps for screens or a predefined Wrkgrp.ini file for workgroup organization, so that client computers are fully configured when Windows 98 is installed.

Creating a push installation process involves doing some final work on the server, such as editing the logon script for the user. System management software such as Microsoft Systems Management Server can also be used to start the installation centrally. If you plan to use system management software in automating the installation, make sure it has been acquired and tested.

For more information on customizing and automating installations, see Chapter 3, "Custom Installations" and Chapter 4, "Automated Installations."

Documenting Rollout Logistics

To document your rollout logistics, determine the timing and the process for pilot installation, and choose the pilot user group.

Although it is a test, the first pilot rollout sets the tone for and presents an example of the final rollout, so it is important to be completely prepared in all aspects of the rollout. This requires that you determine the time it will take for installation, the personnel and tools needed to facilitate the process, and the overall schedule.

Start by identifying the target computers and their location. Then use the following list as the basis of your checklist for rollout logistics:

Has a verified backup been performed for each of the target computers?
Have passwords been reset for CMOS, the network, and applications?
Have virus checking and disk defragmentation been performed?
How many systems will be installed per day? Start with a conservative estimate and then increase or decrease the number, based on your experiences with the initial installations.
At what time of day should the installations occur? You may want to schedule installations to occur on weekdays after normal business hours or on weekends.
Who are the pilot users? Choose a pilot user group or department that is willing and able to accommodate the rollout. This group, ranging from 15 to 50 persons, should be representative of your overall user base. Try not to select a department that is attempting to meet a schedule deadline during the rollout or a group that is traditionally slow in adopting new technology.
What is the schedule for pilot installations? When determining the installation time for the pilot rollout, base the projections on how long it takes for installation of an individual computer; remember to schedule the downtime for each user.
Who will participate in the installations? In addition to the Installation team members, be sure to assign a system administrator with full rights on the server, including the right to administer mail or database server passwords.
Is the deployment methodology as automated as possible?

As you develop the checklist of logistics, consider your goals for the pilot rollout and the factors that define its success. For example, you might set a percentage for successful upgrades or for automated installations that, if achieved, would indicate that the rollout had been successful. Document these goals and criteria, so that teams can monitor performance against them during the rollout.

Notifying Users of the Rollout

Another step at this stage is informing users about the pilot rollout plan. You can use a videotape presentation, an interoffice memo, or a company meeting as the means for communicating with users about the rollout. Regardless of the form used, the message must explain to users the benefits of moving to Windows 98 and describe the overall plan and process by which each group or department will make the move. This makes it easier for your users to plan for and accept the migration to Windows 98 as part of their schedules.

Developing User Training

The first steps in developing a training plan are to acquire a training lab, set up computers in the lab, and appoint a team member as instructor. (If in-house resources are not available, use a vendor to develop and conduct the training.) The instructor will be responsible for creating and testing the training program.

There are a number of training approaches and a variety of tools you can use. A recommended approach is to divide the training into sessions corresponding to three distinct topics: The Basics, Corporate-Specific Applications, and Customization.

The session entitled "The Basics" includes the top eight functions any user needs to know to accomplish daily work. Table 1.1 lists these functions.

Table 1.1 Top eight basic functions in using Windows 98

Function	To perform the function, use this
Run programs, load documents, find a file	Start button
Change settings	Control Panel
Get help on a specific topic	F1 or Help command
Switch between applications	Taskbar
Minimize, maximize, and close windows	Window buttons
Browse your hard disk	My Computer and Windows Explorer
Connect to a network drive	Network Neighborhood
Print a document	Point and Print

Windows 98 Help and the Getting Started book provide the information you need to train users in the basics. You can access the online version of the Getting Started book by clicking Start, pointing to Help, clicking the Contents tab, and selecting the Getting Started Book. Schedule training sessions of no more than 30 minutes each; in each session, users receive just enough information to be productive using Windows 98.

The "Corporate-Specific Applications" session varies by the environment and the types of applications run on the network. This session should focus on the top five to ten functions that will change because of the upgrade to Windows 98.

The "Customization" session is intended for more experienced users. The purpose of this session is to provide information and guidance that will help these users learn on their own after the training, and teach them how to work more productively with Windows 98. These topics could include:

Adding items to the Start button.
Adding items to the desktop (move, copy, shortcut).
Using options controlled by the right mouse button.
Adding a new device (for example, a printer).
Changing the desktop (for example, screen saver settings).

After creating and testing the program, schedule training sessions to occur immediately before the rollout so that the instruction is just in time, ensuring that users retain most of what they learn by putting it to use right away.

Developing the Support Plan

Similar to the training plan, the support plan must be ready to go online the first day you begin performing Windows 98 installations. Because the quality of support available during the pilot rollout will be seen as an indicator of the quality of the rollout as a whole, it is important that you plan carefully to make sure effective support is available.

Staff the Support team for your pilot rollout with some of your best technicians dedicated solely to the pilot group for the first few weeks. The assigned technicians should carry pagers or be available by telephone at all times, to give immediate assistance to users. Help users help themselves by editing Windows 98 Help with company-specific information on applications or features. Doing so requires placing an Oem.cnt file and your custom Help file in the user's \Windows directory. For more information about Oem.cnt and the format of Windows 98 Help files, see the Microsoft Windows Platform Software Development Kit.

Conducting the Pilot Rollout

In conducting the pilot rollout, you simulate the final installation process, test the capabilities and performance of the system, survey user feedback, and make adjustments as needed. Repeat this process for 32-bit applications.

Simulating the Installation Process

The schedule for the pilot rollout should simulate — on a smaller scale — the schedule of the final rollout. As you conduct the pilot rollout, you may find that certain tasks take more or less time than expected, that some tasks need to be added, or that some tasks can be left out. Modify the pilot rollout schedule to account for such changes, and use the pilot schedule for projecting the final rollout timetable.

Testing Windows 98 Performance and Capabilities

In addition to the technicians responsible for conducting the pilot installation, extra technicians should be assigned to measure, observe, and test the installation. By tracking the time per installation, handling problems that arise, and identifying areas for improvement or automation, these individuals help ensure the success of both the pilot and final rollouts by making the installation more efficient.

In addition, after Windows 98 has been installed, these technicians test system capabilities, such as remote administration, for proper operation and monitor the client computers for performance, stability, and functionality, highlighting any inconsistencies with the lab configuration.

Surveying Users for Feedback

The final part of the pilot rollout involves surveying the users to gauge their satisfaction and proficiency with the new installation and to evaluate the level of training and support provided. Test users' proficiency by having them perform a few common tasks or use several of the new features in Windows 98 ; for example, have them register their survey results on the server.

When the survey results have been collected, combine them with the ideas for improvements identified during the pilot rollout. Use this information to prepare a checklist of open issues that must be resolved prior to the final rollout. Then assign team members to take the actions necessary to solve problems or make improvements. Indicate on the checklist how and when each item was resolved, adjusting the deployment plan if appropriate.

Finalizing the Rollout Plan

The final rollout plan is an extension of the pilot planning process, with the added steps of documenting, budgeting, and carrying out the final logistics. As you perform these steps, you should also update the policies and practices guidelines governing network and computer use in your company, and create a template for a central database that tracks specific configurations and uses of each network computer.

Completing the Rollout Logistics and Budget

As you prepare for final rollout, estimate the length and scope of the overall installation process. Also plan for all tools needed to complete the process within the stated time frame. If necessary, propose a formal budget for the company-wide implementation and present it to management for approval. Your budget should include the costs for personnel and resources, such as system management software.

After obtaining any necessary approval, purchase the resources required to facilitate the installation. If you need additional staff, be sure to hire experienced and qualified individuals for the team, and train them extensively before starting.

Complete your training, communication, and staffing plans for the final rollout at this time.

Updating the Policies and Practices Guidelines

Prior to final rollout, update all company policies regarding employees' use of the network and computer. Make sure to cover items such as password length and expiration requirements, and the level of approval needed to obtain remote dial-up privileges.

In addition, update the corporate standards lists for hardware and software usage; use these as a reference for bringing all computers into compliance during the rollout process.

Because Windows 98 makes possible the use of many new 32-bit applications and of Plug and Play–compliant hardware, these new products should be added to the list, and their older counterparts should be deleted.

Creating a Template for the Rollout Database

Use a template to create a central database for monitoring the progress of the rollout and to document any areas requiring further action. During preparations for the final rollout, create the template, using appropriate database management software. Complete the template with configuration information for every computer and user in the company, and place the template on the server. Then, during company-wide installation, the Installation team fills in the template for each computer and user, indicating whether any additional upgrading is needed. The team can then use the template to track open items following the rollout and to measure actual progress against original objectives.

Rolling Out Windows 98

Following the weeks of planning, organization, testing, communication, and training, the deployment teams and your organization as a whole should be ready for a full-scale rollout of Windows 98. The extensive preparation for this event may make deployment seem almost routine for the teams involved; however, that is exactly the kind of uncomplicated rollout a systems administrator dreams of. After completing the installations, users may not know how they got their work done without Windows 98.