لطفا منتظر باشید ...
Preparing for the Rollout
The rollout is the final phase of your deployment, when Windows 2000 Professional is implemented throughout your organization. Rollout is a production activity, which means any potential problems encountered during the rollout can adversely affect productivity and subsequently profitability. A well-designed rollout plan is essential for making your deployment a positive experience for all users.Your pilot process will have simulated on a smaller scale the process for rolling out Windows 20000 Professional to your entire organization. The results of the pilot installation provide the basis for developing a final plan for rollout. Your preparation for the production rollout begins with the evaluation of the pilot results.
Evaluating the Pilot Results
The final part of the pilot rollout involves collecting and summarizing the data and feedback from the users to help plan for the production rollout. The project team needs to use this data to make any necessary adjustments to the planning and installation process. Tasks to perform during this phase include:
- Survey members of the pilot user group about their satisfaction with the installation process
and ask for their suggestions on what might have been done better. Ask them to also evaluate the level of training and support provided. Survey the pilot implementation team to collect ideas for improvement to the planning and installation
process. Compare your installation results against goals and evaluation criteria for this process. Create a checklist of open issues that must be resolved prior to the final rollout. Assign to individual team members the actions for solving problems or making improvements.
If the pilot program did not run smoothly or if user feedback was poor, you might find it necessary to conduct additional pilot installations. As necessary, modify and retest the configuration and installation procedures. Document any changes made to the installation process that address improvements, problems, or other support requirements.
Finalizing the Rollout Plan
Using information about the actual time and resource requirements of the pilot rollout, the project team can make projections scaled to the organizationwide scope of the final rollout. You can then create the deployment schedule and budget the resources in terms of personnel and tools required to meet the rollout schedule. If additional resources are required, they need to be identified and acquired at this time. Include in your rollout plan a support plan and training plan.When finalizing your rollout plan perform the following tasks:Determine the number of computers involved in the final deployment and the time required to
upgrade or install Windows 2000 Professional on each.
List the resources needed to complete the process within the schedule.
Identify any additional personnel needed for the deployment processes, and associated training requirements.
Present a formal budget for the organizationwide implementation.
When deploying Windows 2000 Professional in an enterprise organization, you will want to employ automated installation methods. Include in your rollout plan a description of your enterprisewide automated installation methodology. Microsoft® Systems Management Server (SMS) can help you perform the following tasks:
Selecting computers that are equipped for Windows 2000 and that you are ready to support. Distributing Windows 2000 source files to all sites, including remote sites and sites without technical support staff. Monitoring the distribution to all sites. Securely providing enough operating system rights to do the upgrade. Automatically initiating the installation of the software package with the possibility of allowing the user to control the timing. Resolving problems related to the distributions or installations. Reporting on the rate and success of deployment.
SMS provides tools for upgrading your current computers but not for the installation of new computers that do not have an operating system already installed.
