Stabilizing

Published: June 30, 2006 | Updated: November 30, 2006

During the Stabilizing Phase, the User State Migration feature team works with the Test feature team to identify and correct bugs in the USMT control files. Figure 6 illustrates the Stabilizing Phase activities.

Figure 6. User state migration activities during the Stabilizing Phase

On This Page

Roles and Responsibilities
Testing the USMT
Updating the Deployment Server
Milestone: Deployment Readiness Review

Roles and Responsibilities

All six role clusters from the MSF Team Model play a role in the Stabilizing Phase of the initiative. Table 5 lists those roles and defines the focus areas for each role cluster. For more information about MSF Role Clusters, see Microsoft Solutions Framework at https://www.microsoft.com/technet/itsolutions/msf/default.mspx.

Table 5. Roles and Responsibilities During the Stabilizing Phase

Testing the USMT

After the User State Migration feature team has updated the USMT control files, they must test the files before including them on the deployment server. The USMT developers should work with the application SMEs to test the collection and restoration of the application data files and settings.

To test each application, computers in the lab must be configured with the original application. Images of production computers are often useful as the source computers for these tests because they accurately reflect the production configurations. In addition, destination computers running Windows XP (if required by project plan) and the new Windows Vista image will be needed as the target or destination of the USMT data.

The User State Migration feature team can run the USMT process manually on the source and destination computers to speed the testing process. The team can perform the application tests individually or group them in a logical sequence, such as all tax department applications. If using a software-distribution tool, be sure to fully test running the USMT in that environment, as well. Permissions can be different. The account under which the USMT is run can also be a non-interactive account. Use the log and progress files to monitor the results.

When these tests are successful, the User State Migration feature team can transition the USMT control files to the Release Management Role Cluster for inclusion in the pilot testing. During the pilot, end-to-end USMT testing will be conducted as part of the automated deployment process.

Note   To promote the separation of development and test roles within the User State Migration feature team, consider choosing non-developers from within the team to perform the testing role.

Updating the Deployment Server

For the deployment process to use the modified control files, the User State Migration feature team must copy the updated files (MigSys.xml, MigApp.xml, and MigUser.xml) into the Tools\x86 or Tools\x64 folder on each deployment server. The USMT will then use these updated files the next time BDD 2007 executes the USMT. Locations of all USMT binaries and control files are detailed in “Appendix E: Preparing the Distribution Share.”

Milestone: Deployment Readiness Review

Milestones are synchronization points for the overall solution. For more information, see the Plan, Build, and Deploy Guide.

At this milestone, shown in Table 6, the User State Migration feature team has tested the USMT files and prepared them for deployment.

Table 6. Deliverables

Download

Get the Microsoft Solution Accelerator for Business Desktop Deployment 2007

Update Notifications

Sign up to learn about updates and new releases

Feedback

Send us your comments or suggestions