Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Windows 7 Migration: Step 7 - Measure and Report

Created: 01 Mar 2010 • Updated: 01 Nov 2010
Language Translations
CondorMan's picture
+3 3 Votes
Login to vote

Step 7: Measure and Report

After a successful roll out of the automated migration, there's one last important step: post-migration reporting and analysis. Good reporting will enable your executive team to track the migration from a distance and will help you analyze aspects of migration such as:

  • Total systems successfully migrated
  • Problems encountered during migration
  • Missing patches
  • License verification

Total Systems Successfully Migrated

When a client system is successfully migrated it will report in the Deployment Server console as having completed the job with no errors. This is very easy to see visually in the Deployment Console as a green check mark next to the schedule status. You can select either an individual computer and see its job status, or you can select a job and see all clients that have been assigned that job and see their status.

This only shows the status of the overall job completion and not the status of each task individually. By default when any one task in a job fails the job will halt at that point and report back the error code or message of that failed task as the job status. This can be configured where certain error codes or messages can continue the job. Even with a failure at one point, the rest of the tasks can complete and the migration process can finish. If this is done the individual computer and tasks need to be drilled down to in the console to see these details.

The data of completed jobs is stored in the Deployment Solution database and can be queried to generate reports that can be either printed or saved to a spreadsheet. Most of the data that will be needed will be contained in the event_schedule table which contains data for all scheduled job. This data will need to be joined with the computer table to associate it with a specific computer record, and the event table to join it with a specific job name. The table status_log contains details about each individual task that was run as well. That data is very detailed and might be useful, but will increase the size of the report by a large factor.

SQL Report of completed migrations -

SELECT c.[name], s.[status], s.[end_time]
FROM [computer] c, [event_schedule] s, [event] e
WHERE c.[computer_id] = s.[computer_id] AND e.[event_id] = s.[event_id]
AND e.[name] = 'Migration Job' AND s.[exit_code] = 0

The above query will need to have the job name of 'Migration Job' replaced with the name of the job in your Deployment console. Keep the single quotes around the name of the job in the SQL query however. Additional columns can be added to the query output such as when the job was scheduled, or when the job was started. The above query is meant as a basic report that can be expanded and modified to meet your needs. See Appendix A for more information.

Problems Encountered During Migration

The above report can be modified slightly to give a list of client systems that have run the migration job and have failed. However, in a failed job it is important to see the individual tasks to determine where it failed. The following SQL query incorporates the status_log table to gather that additional information.

SELECT c.[name], l.[status], l.[return_code_result] , l.[complete_time]
FROM [computer] c, [event_schedule] s, [event] e, [status_log] l
WHERE c.[computer_id] = s.[computer_id] AND e.[event_id] = s.[event_id]
AND l.[schedule_id] = s.[schedule_id]
AND e.[name] = 'Migration Job' AND s.[exit_code] <> 0

Once again the above query will need to be modified to contain the name of the migration job. You will also notice that the result of the first query has one result for each client where the report of failed migrations might have multiple results for a single computer record. This is because an entry is made in the status_log table each time the computer status changes. This will show every successful task and every failed task that might have modified the computer status at any time during the job execution.

Additional Windows 7 Migration Information

Listed below are some helpful places you can go to get more information about Windows 7 Migration:

The Windows 7 Resource Center has everything you need to successfully plan and execute an enterprise-wise Windows 7 migration including best practices, white papers, events, downloads, and more at http://www.symantec.com/windows7.

Symantec Connect, an online community where you can collaborate, learn and share ideas about Symantec solutions at http://www.symantec.com/community.

Return to: Windows 7 Migration: Introduction