Who can do this?
Shopping administrators.
What is it used for?
To get an on-demand status (completed, in-progress, failed and not started) on all WSA orders.
Where do I run the report from?
From the Shopping menu, choose Track WSA orders under OS Migration.

Running the report


Tracking WSA ordersTrack WSA Orders is an on-demand report that enables Shopping administrators to get a view of the latest status of WSA orders. It is located on the Shopping menu under OS Migration. There is no facility to create a schedule for this report to run.

On this page:

To get the status of all WSA orders, click Track WSA Orders on the OS Migration menu. The report is presented in a tabular format and is made up of eight columns and by default, the results are ordered by the Last Modified Time column. 

Tracking WSA orders

You can narrow the recordset by clicking the filter icon on all column headers except for Last Modified Time. As you define your filter criteria, it is dynamically saved at the top of the table. As the filter builds, results matching your filters are displayed in the table.
 

If you have inadvertently created an incorrect filter, click the cross next to it to remove it. Alternatively, click Clear Filters to remove all your dynamically saved filters.

Where a user has initiated a Prepare My Old PC for Replacement (they are migrating from their existing machine to a new one) and subsequently initiated a Restore My Data and Apps to a New PC (they are moving data from the old machine to the new one), we record details of this relationship as illustrated in the expanded record below. 

Records for a Replace Restore scenario

Deleting orphaned orders

There are instances where a WSA order can remain in a running status without a corresponding running task sequence (the task sequence has failed in WinPE). You should only cancel orders that are in this state – typically, when a user notices that the task sequence has not started to run after the WSA Readiness screen (for example, if they ran the the In-place upgrade deployment) or if they are prompted that a task sequence is already running when they run the deployment and gets in touch with you to investigate.

If you cancel an order while the task sequence is running, it is likely that the status of the order will not transition to Deployment Succeeded or Deployment Failed when the existing task sequence completes.

To removed orphaned orders from the report:

  1. On the OS Migration menu, click Track WSA Orders.
  2. In the Track WSA Orders report, identify the orders with a Deployment in progress status – they have Cancel button associated with it.
  3. Locate the order to cancel and under the Cancel column, click Cancel.
  4. In the Cancel Order dialog, confirm your actions.
    Cancelling a WSA order
  5. The status columns updates to Administrator cancelled. If you select No in the Cancel Order dialog, the order is left in its original state and the status column is not update.

However, if you have installed the Tachyon 3.2 Agent, this is not likely to happen and the report will return a failed status so that you can easily identify and remove it.

What the report gives you

Column headingFilter optionsNotes
WSA Type

WSA Type sort order

Can be an in-place upgrade, replace capture, replace restore, wipe and load destructive or a wipe and load non-destrictive deployment.

Click the column header to display a list of deployment types to filter on.

  • In-Place Upgrade –this is where an in-place upgrade from Windows 7 or 8.1 to Windows 10 or any of its variants is carried out on the machine. It executes a task sequence that uses the Upgrade Operating System step to upgrade the currently installed operating system.

  • Replace Capture –this is where a user is migrated from his existing machine to a new one. Information on user data and settings is captured from the old one and restored on the new machine.

    The conditions for this particular deployment type is: 


    1. if a Replace Capture has been performed, but a restore for that deployment has not been run yet, Replace Capture is displayed as the parent row whilst Replace Restore, which has not started yet, is displayed as the child row
    2. if a Replace Restore is in-progress, Replace Restore is displayed as the parent row whilst Replace Capture is displayed as the child row
  • Replace Restore –this where the user is moving data from the old machine to the new one.

    The conditions for this particular deployment type is:


    1. if a Replace Capture has been performed, but a restore for that deployment has not yet been run, Replace Capture is displayed as the parent row with the Replace Restore (which has not started yet) as its child row
    2. if a Replace Restore is in-progress, Replace Restore is displayed as the parent row with the Replace Capture as its child row
  • Wipe and Load Non-destructive –this is where a machine is wiped as part of the OS deployment and a fresh OS is installed. Non-destructive here means that it uses the MBR2GPT step by Microsoft, so it retains all the data on the hard drive, therefore speeding up deployment times and reliability of deployment.

  • Wipe and Load Destructive –this is where a machine is wiped as part of the OS deployment and a fresh OS is installed. Destructive here means that it does not use the MBR2GPT step by Microsoft, so it destroys the data on the hard drive and then rebuilds the structure on it.

WSA Name

Name of the deployment as it is defined in the Shopping Admin console

Click the column header to display a search box for you to enter your search criteria. As you type in the search box, the smart search feature for Filtered results will show the number of records matching your search string. You cannot use wildcards in your filter.

To see configuration of a particular deployment, click its name in the WSA Name column. For example, if we clicked Upgrade to Windows 1703, the following is displayed.
Getting the details of a particular deployment 

Machine

Name of the machine associated with the user who initiated the deployment which can either be the name of the machine being replaced or the new machine replacing the old one depending on the type of deployment the user initiated.

  • If the deployment type is Replace Capture, it refers to the name of the old machine that is being replaced
  • If the deployment type is Replace Restore, it refers to the name of the new machine that is replacing the old one

Click the column header to display a search box for you to enter your search criteria. As you type in the search box, the smart search feature for Filtered results will show the number of records matching your search string. You cannot use wildcards in your filter.

User

The user who initiated the deployment.

Click the column header to display a search box for you to enter your search criteria. As you type in the search box, the smart search feature for Filtered results will show the number of records matching your search string. You cannot use wildcards in your filter.

Location

Where the user initiated the deployment from.

Click the column header to display a list of locations to filter on.

USB

Indicates if a USB device was used in the deployment and what it was used for.

Click the column header to display a list of USB usage types to filter on.

  • Disallowed  – the use of USB devices was not permitted
  • No – a USB device was not used for any content or data transfer
  • Content – a USB device was used to store and retrieve content such as content for the Windows image or from Application Migration
  • User Data – a USB device was used to store and retrieve user data backed-up from WSA using Microsoft USMT
  • Content and User Data – a USB device was used to store system/application content as well as for storing and retrieving backed-up user data from WSA with Microsoft USMT
Last Modified TimeN/ALogs when an action in the deployment was carried out in Shopping. This could mean different things based on the status column of that deployment. For example,
  • if the status for a deployment type is Task Sequence Completed, it is the date and time when the task sequence finished execution
  • if the status for a deployment is User In-Progress, it is the date and time when the WSA wizard was launched by the user
  • if the status for a deployment is Checks In-Progress, it is the date and time when the WSA wizard transitioned into the readiness checks stage
Status

Indicates the current status of a particular deployment type.

Click the column header to display a list of statuses to filter on.

  • Checks in-progress – readiness checks are in-progress.
  • Checks failed, waiting for user – readiness checks failed and waiting on user to take action.
  • User cancelled – user cancelled the deployment either during the readiness checks stage or after the checks have been successfully completed.
  • Checks Failed, user cancelled – user cancelled the deployment when a readiness check fails.
  • Checks complete, waiting for user – readiness checks were completed successfully and waiting on the user to determine when they want to start the deployment.
  • Deployment in-progress – deployment is in progress and a series of prompts are displayed to indicate progress.
  • Deployment succeeded – the deployment has completed.
  • Deployment failed – the deployment has failed.
  • Deployment Succeeded, Acknowledged – deployment has succeeded and the user closes the WSA wizard.
  • Deployment Failed, Acknowledged – deployment has failed and the user closes the WSA wizard.
  • Capture Expired – This status has not been implemented, so selecting this filter will not display any results.

To see the status of a particular deployment, click its name in the Status column. For example, if we clicked Checks failed, user cancelled, the following is displayed:
Getting the details of a particular status 

A primer on tracking WSA orders