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.
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 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. "
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:
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.
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.
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:
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.
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.