Solution Accelerator for Business Desktop Deployment Enterprise Edition > Zero Touch Installation Deployment Feature Team Guide

Zero Touch Installation Deployment Feature Team Guide

Transitioning to Operations

Published: August 27, 2005

After the initial deployment is complete and proper workstation operation has been verified, the process is transitioned from a deployment initiative to an operating initiative. The information technology (IT) operations group is then responsible for the ongoing workstation maintenance and support. This process is typically well structured and formal, where documentation, knowledge, and other materials are formally transferred from one group to another.

Roles and Responsibilities

In addition to the tasks defined in the following process description, take note of the responsibilities that are allocated to the role clusters. Table 44 defines these focus areas for the different role clusters during this phase.

Table 44. Team Roles and Their Responsibilities During the Transition to Operations

Role	Focus
Product management	Communications plan execution; deployment launch planning
Program management	Project tracking; bug management
Development	Bug resolution; code optimization
User experience	Training materials
Test	Testing and bug reporting
Release management	Pilot management and support; deployment planning; operations and support training, executing the deployments

Top of page

Milestones in the Transition to Operations

Table 45 lists the project milestones and deliverables that you need to complete during the Transition to Operations. The project plan you create needs to include these milestones, the resources required for each milestone, and the length of time to complete each milestone.

Table 45. Transition to Operations Project Milestones and Deliverable Description

Transition to Operations Milestone	Deliverable Description	Owner
Transition preparations complete	The operations and deployment teams have been notified of the transition date. Users are now aware of the change in contact information for support.	Deployment
Current deployment status communicated	The current status of all workstation being transitioned is communicated. Any updates to troubleshooting procedures and diagnostic tools are also communicated.	Deployment

Top of page

Preparing for the Transition

After the deployment of a batch of workstations is complete, you are ready to transition the support of those workstations to operations. In preparation for that transition, you need to:

•	Notify the Deployment and Operations feature teams of the transition date. Ensure that the Deployment and Operations feature teams are aware of when the support for the workstations will be transitioned. The Operations feature team must be ready for users to call with support questions, and the Deployment feature team must know to direct users to the Operations feature team for future support.
•	Notify users of changes in contacts for support (deployment to operations). Users need to know when they should stop contacting the Deployment feature team for support. Supply users with the numbers and contact information for the Operations feature team.

Top of page

Communicating the Current Deployment Status

Just before you make the transition from the deployment team to the operations team, you need to inform the Operations feature team of the current status of the deployment. Communicate the current deployment status each time a group of workstations is migrated.

Communicate the current deployment status by identifying the workstations that:

•	Have been successfully deployed. You need to make certain the Operations feature team has an accurate list of workstations that have been successfully deployed. This list will provide them with an estimate of how many deployed workstations they are taking responsibility for after the transition. Also, the list will give them an idea of the location for the transitioned workstations.
•	Failed during the deployment process and were rolled back. The Operations feature team needs to know the workstations in the group that are in their original state. In this way, the team will know that those workstations should operate as before and should not initiate support calls based on the deployment.
•	Are pending deployment. The Operations feature team needs to know if workstations in the group are still pending deployment. For those workstations, they will forward support issues back to the Deployment feature team.

In addition, you need to communicate any updates to troubleshooting procedures and diagnostic tools since the last group of workstations was transitioned.

Note For more information about troubleshooting procedures and diagnostic tools, see Appendix H: Resolving Common ZTI Deployment Problems, later in this guide.

Top of page

10 of 25

•	Using This Guide
•	Quick-Start Guide and Checklist
•	Introduction
•	ZTI Deployment Process Overview
•	Envisioning
•	Planning
•	Developing
•	Stabilizing
•	Deploying
•	Transitioning to Operations
•	Additional Resources
•	Appendix A: Sample Customsettings.ini Files
•	Appendix B: Customsettings.ini Reference
•	Appendix C: AdminDB Database Schema
•	Appendix D: AdminDB .csv File Format Reference
•	Appendix E: ZTI Scenario Process Flowcharts
•	Appendix F: Sample User Exit Function
•	Appendix G: Training Resources
•	Appendix H: Resolving Common ZTI Deployment Problems
•	Appendix I: Deploying Windows XP Using Windows Product Activation
•	Appendix J: Sample Stored Procedure Calls
•	Appendix K: Automating Application Deployment Scenarios
•	Appendix L: Operating BDD Enterprise Without WINS
•	Appendix M: Locating Regional SQL Servers
•	Appendix N: Reserving Space for Future Migrations

Zero Touch Installation Deployment Feature Team Guide

Transitioning to Operations

On This Page

Roles and Responsibilities

Milestones in the Transition to Operations

Preparing for the Transition

Communicating the Current Deployment Status

In This Article