Enabling users to schedule or initiate their own Operating System deployments can significantly reduce the time and cost of IT staff to rebuild, replace or upgrade machines and also reduces user downtime as they have more control over when the process happens and can initiate it at a time when they do not need their computer.

Shopping uses Applications to publish items to users for self-service through the Shopping portal. Shopping 5.5 offers three methods to deliver self-service Operating System Deployment to your users, each using different Shopping Application types.

Each of these methods use Microsoft Configuration Manager Task Sequences to automate the OS deployment tasks, but differ in the user experience, the way that the Task Sequences are deployed to the device and the deployment scenarios that are supported. Each of these methods optionally support application migration.

Please refer to the following for more detail about ...

ConfigMgr Applications

Users shop for a task sequence in the same way as any other Shopping application, by selecting a tile or banner.

The simplest form of self-service OS deployment uses a standard ConfigMgr Application in Shopping that is configured to publish a Configuration Manager task sequence in the Shopping portal in the same way that Applications and Packages are published (this functionality has been in since Shopping 3.0). Users that have permission to view the Application will see it in the portal as a tile along with other Applications. ConfigMgr Applications that publish a task sequence can be organized in the portal in the same way as other Shopping Applications with User Categories.

The images below illustrate an example of a ConfigMgr Application in Shopping named Backup My Data that publishes the 4a - Backup My Data task sequence to the portal and how this application is presented to the user in the Shopping portal.

 Properties for the Backup my data Configuration Manager Application  Backup My Data tile displayed in the Shopping portal

When the user requests the application, any defined approval workflow will be executed, after which Shopping adds the machine from which the request was made into a Collection that is targeted with the task sequence defined in the ConfigMgr Application properties. The task sequence must be created before the ConfigMgr Application can be defined in Shopping, but the target Collection and Deployment are created by Shopping the first time a user requests the application from the portal (as is the case with ConfigMgr Applications that publish Configuration Manager Packages). Once the machine is in the targeted Collection, on the next Configuration Manager Machine Policy refresh cycle on the machine, the task sequence will start to execute. Beyond the initial request, the user has no other control over the process.

ConfigMgr Applications in Shopping that publish task sequences can be used in the following OS deployment scenarios:

  • In-place Upgrade
  • Computer Replace. In this scenario, separate Applications are published - the first to backup the data from the old PC and the second to restore data and install applications onto the new computer. A Computer Association that associates the old computer with the new computer must be defined in Configuration Manager to enable self-service Computer Replace. The user requests the 'backup' application from the portal on the old PC, then logs into the new PC (which must already have an image installed) and requests the 'restore' application.
  • Computer Refresh (reinstall the current Operating System or install a new one, migrating the data and applications using automation built into the Task Sequence)

Due to the limited user interaction, they are useful in the following situations:

  • Where user processes are well documented and the user does not need any on-screen guidance in the process
  • Where the task sequence fully automates the OS deployment process without the need for additional parameters to be defined by the user or different logic and process to be defined for users in the office compared with users working remotely
  • It doesn't matter when the task sequence starts - it will start when the approval workflow (if any) has been completed, Shopping has added the machine to the Collection and the CM client has retrieved the policy, all of which is fairly unpredictable.
  • Where the same process (e.g. computer refresh) may need to be executed multiple times on the same device over time
  • Where approval is required for self-service OS deployment requests

Publishing Task Sequences to the Shopping Portal

To publish an OS deployment Task Sequence in the Shopping portal using a ConfigMgr Application:

  1. Create and test the task sequence in Configuration Manager
  2. Create a ConfigMgr Application in Shopping following the process in Managing Configuration Manager applications, selecting the task sequence to be published in the ConfigMgr Package and Program page of the wizard.

OSD Applications

Users click on a banner to initiate an OSD Wizard, which allows the user to execute or schedule a deployment.

OSD Applications are defined in the Shopping Console along with other Application types and are presented to the user through a banner that appears at the top of the portal as shown in the screenshot below.

Self Service OSD banner

The banner is associated with a specific OSD Application and the user must have permission to view that Application in order to see it. However, there may be multiple OSD Applications published in Shopping. When the user clicks the Launch button, a web-based wizard is launched that steps the user through the options available. The first page of the wizard shows all OSD Applications that the user has permission to view and the user can select which one they want to deploy. The user is then optionally shown the applications that will be migrated during the process (if Application Migration has been implemented and the Shopping Administrator has enabled the page in the OSD Application properties) and finally invited to select a time slot to schedule the deployment (based on what restrictions the Shopping Admin defined in the OSD Application properties) or to run the deployment immediately.

The preparation of OSD Applications differs from ConfigMgr Applications that publish Task Sequences as the administrator must create the Task Sequence, the target Collection and a Required Deployment before creating the OSD Application in Shopping. When defining the OSD Application, the administrator selects the previously created target Collection in the OSD Application properties and then selects the appropriate Deployment from the Advertisement list in the OS Deployment Properties dialog.

When the user has completed the web-based OSD wizard, if they chose to run the deployment immediately, Shopping adds the machine from which the wizard was run into the target Collection specified in the Shopping OSD Application properties. If the user selected a specific schedule, Shopping adds the machine to the target Collection at the scheduled time. The Configuration Manager client will then execute the associated task sequence when it next refreshes its machine policy (typically Shopping will initiate a CM Policy Refresh on the target machine after it has added the machine to the target Collection, depending on the Policy Refresh option selected when Shopping was installed).

OSD Applications can be used for the following deployment scenarios:

  • In-place Upgrade
  • Computer Refresh (reinstall the current Operating System or install a new one, migrating the data and applications using automation built into the Task Sequence)

They are useful in the following situations:

  • Where the user requires some guidance and may want to schedule the deployment to occur at a time that is convenient to them
  • One-off upgrades or migrations to a new OS or new OS version (e.g. an in-place upgrade from Windows 10 1703 to 1709). Note that once an OSD Application request has completed successfully on a machine, the banner is no longer available to users viewing the Shopping portal from the same machine so the same OSD Application cannot be deployed multiple times on the same PC.
  • Where Shopping Administrators wish to request OSD Applications on behalf of other users (i.e. to schedule deployment of a new OS on multiple devices through the Shopping web portal)

Publishing OSD Applications to the Shopping portal

To publish an OSD Application to the Shopping portal:

  1. Create and test the task sequence in Configuration Manager.
  2. Create an empty Collection in Configuration Manager that will become the target of a Task Sequence Deployment. Shopping will add machines to this Collection according to the schedule options selected by the user in the OSD Wizard.
  3. In Configuration Manager, deploy the task sequence created in step 1 to the Collection created in step 2. The Deployment should be Required with the schedule option As soon as possible selected
  4. Create an OSD Application in Shopping following the process in Creating OS Deployment applications

Properties in the OS deployment dialog

Windows Servicing Assistant (WSA) Deployment Applications

Users click on a banner to initiate a WSA Wizard, which supports the user through the entire deployment experience. Below are some example pictures of the WSA Wizard, for more examples please refer to The Windows Servicing Assistant user journey below.

The Start screen

The New PC screen

Notification that you will need to run the Restore deployment manually


Additional software required for Windows Servicing Assistant

The Shopping module of the 1E Client (formerly named the Tachyon Agent) also provides Windows Servicing Assistant (WSA) which guides users through the preparation and execution of an OS deployment. WSA is a client-based wizard that enables users in the office or working remotely over VPN to initiate an OS upgrade or OS refresh (wipe-and-load) or to migrate data, settings and applications from an old PC to a replacement PC at their convenience. WSA Applications are created managed through the Shopping Admin console. The task sequences used by WSA have a dependency on 1E Nomad 7.0.200 , to manage content and storage of user state using custom actions that are implemented with Nomad.

1E Client (Tachyon Agent) versions offer enhanced levels of support for WSA:

  • WSA in 1E Client 5.0 with its latest Accumulated Hotfix (Patch) or 1E Client 5.1 provides the following WSA enhancements and works with Shopping 6.0 and later:

    • Support for nested Task Sequences
    • Autofill Wi-Fi passcode on Connection page if available
    • Option to disable the Location page
  • WSA in 1E Client 4.1 or 5.0 provides the following WSA enhancements and works with Shopping 5.5.200 and later:

    • Applications page includes all installed, normalized applications

    • Allow conditional download of Windows 10 upgrade packages

    • Check Windows 10 version readiness checks before upgrading

    • Perform In-place Upgrade compatibility check in WSA readiness checks

    • Allow Windows Servicing Assistant to exclude user state migration

    • Required for environments where TLS 1.0 is disabled.

  • WSA in Tachyon Agent 3.3 (now out of support) provides the following and works with Shopping 5.5.100 and later:

    • Customization of all text strings
    • Wi-Fi support for Wipe and Load Destructive deployments
  • WSA in Tachyon Agent 3.2 (now out of support) provides basic features and works with Shopping 5.5.0

The above WSA features require a full Shopping infrastructure including 1E Client deployed with the Shopping client and Nomad client modules enabled. 1E Client 5.1 onwards also includes the PXE Everywhere client module to support PXE booting of peer computers.

WSA optionally supports migration of applications in Replace and Refresh OS deployment scenarios.  1E Application Migration 3.1 requires a full  Tachyon 5.1 infrastructure, including 1E Client with Tachyon client enabled.  Customers that have purchased the WSA are licensed to use Shopping, Nomad, and Application Migration, and can therefore take full advantage of the all WSA functionality.

WSA Applications are similar to, but slightly different from OSD Applications in the following ways:

  • They are made available to users in the Shopping portal through a single banner rather than individual application tiles. However the banner for WSA Applications is not tied to a specific WSA application - it will be displayed if the user has permissions to any WSA Application.
  • Administrators must create a target Collection and Deployment before creating the WSA Application in Shopping, however for WSA Applications the Deployment must be Available rather than Required, and the Deployment start time must be set to a time way in the future (e.g. 10 years). This is because the WSA will convert the schedule locally on the client immediately before the deployment is to be executed. This prevents the task sequence appearing in Software Center (thereby preventing the user from starting it independently) or executing before the machine is ready.

The key differentiator from OSD Applications is that the WSA is a client-based wizard that is implemented with the Shopping module in the Tachyon 3.2 Agent  or later. Although it is invoked by the user, once launched (by clicking the Launch button on the banner in the Shopping portal) the process is managed by the Shopping module in the Tachyon Agent. This approach enables the WSA to actively prepare the machine, for example:

  • ensuring content is downloaded locally, using a USB drive if permitted for additional storage if necessary, enabling remote users with a VPN connection to complete OS upgrade, OS refresh and replacement scenarios
  • ensuring certain prereqs are met, such as the machine is connected to a power source rather than running on battery 
  • optionally enabling the user to select folders to be included in the user state capture (The WSA dynamically creates a USMT configuration file based on the user selections and stores this in the Shopping database. Custom steps in the task sequence then retrieve this file and add it to the USMT state capture command line).

The WSA implements a system tray tool that notifies the user of the current status of the process and allows the user to minimize the wizard while their machine is prepared. They will be notified when the machine is ready for the selected deployment and can choose to run it immediately or come back later to run it when they are ready,

WSA Applications can be used for the following deployment scenarios:

  • In-place Upgrade
  • Computer Refresh (aka Wipe-and-load). WSA Applications have the concept of 'destructive' and 'non-destructive' wipe-and-load deployments. A Non-destructive Wipe-and-load Application will execute a task sequence that does not repartition or reformat the local disk. In this scenario user state can be preserved on the disk using USMT with hard links, speeding up the deployment time. A Destructive Wipe-and-load Application will execute a task sequence that will repartition or reformat the local disk. In this scenario it is particularly important that all the content required to complete the deployment is available either on a local peer or on a connected USB drive. The WSA manages the acquisition of the required content and will also store the captured user data on a USB drive if no local peers are available to store the content.
  • Computer Replace. In this scenario, separate Applications are published - the first to backup the data from the old PC and the second to restore data and install applications onto the new computer. The WSA can manage computer replacements where no Computer Association exists in Configuration Manager. However, if a Computer Association does exist, the zero-touch option can be used, which automates the deployment of the restore application to the new computer once the capture of the old computer has completed and been acknowledged by the user.

    For WSA to support computer replacement, the new (replacement) computer must be provided to the user with the Operating System installed and the Nomad 6.3.200 or later and Tachyon 3.2 or later agents installed. The WSA is not currently able to build the new computer, but is instead used to transfer data and migrate applications from the old computer to the new computer.

They are particularly useful in the following situations:

  • Where users require on-screen guidance through the deployment process
  • Where users may need to deploy an OS while working remotely and connected to the corporate network via VPN
  • Where administrators want to ensure the best chance of the OS Deployment Task Sequence executing and completing successfully by ensuring everything is in place and ready before the task sequence is executed

Publishing Windows Servicing Assistant Deployment Applications to the Shopping portal

To publish Windows Servicing Assistant Deployment Applications to the Shopping portal:

  1. Create and test the task sequence in Configuration Manager.
  2. Create an empty Collection in Configuration Manager that will become the target of a Task Sequence Deployment. Shopping will add machines to this Collection as the Windows Servicing Assistant prepares the machine for the deployment.
  3. In Configuration Manager, deploy the task sequence created in step 1 to the Collection created in step 2. The Deployment should be Available with the Available time set to 10 years in the future.
  4. Create a Windows Servicing Assistant Deployment application Shopping

Refer to Creating Windows Servicing Assistant Deployment Applications for details on completing the above steps.

The Windows Servicing Assistant user journey

The In-place upgrade scenario is used to upgrade the computer you are currently using. This is a simple upgrade that retains local data and settings without needing them to be backed up. Applications may also be upgraded.

 Click here to view the In-Place Upgrade user experience...

The user experience 

There are seven phases for this deployment type if you are running the upgrade from the office:

  1. Choosing the deployment
  2. Telling us where they are
  3. Showing them the list of applications they keep or lose in the deployment
  4. Requesting additional storage
  5. Displaying a summary of their actions
  6. Running background checks
  7. The outcome of the deployment

If you are remote, there is an additional step where we request your connection details, just after requesting additional storage.

Walking you through the user experience

Banner on the Shopping Web
Start hereObservations

Banner on the Shopping Web

Why can't I see the banner on the Shopping web?

If you can't see the banner on the Shopping web, it is likely that:

  • you or the device you are using may not yet be associated with the groups that can do this
  • your Shopping administrator has not created a Windows Servicing Assistant banner or Windows Servicing Assistant Deployment
The Start screen

Choosing the type of deploymentObservations

The Start screen

Always displayed for the user to choose the type of deployment they want.
The Location screen

Where the deployment is initiated fromObservations

The Location screen

Displayed for the user to tell us where they are initiating the deployment.

Why can't I see the Location screen?

You will not see this screen if:


The Applications screen

Changes to applicationsObservations

Only displayed:

For an In-place upgrade, the list will show applications that will be replaced or upgraded by Application Migration rules. Any applications for which no rules are applicable will remain installed as the In-place Upgrade does not remove any applications.

If you are unable to retrieve the list of applications that are changing, click Retry.
Network issues preventing applications from being retrieved
If you are still unable to see the list, click Next to continue to the next screen.

Why can't I see the Applications screen?

You won't see the list of applications:

The USB Media screen

Requesting additional storageObservations

The USB Media screen

Only displayed:

A series of checks are made when a USB device is discovered:

  • to ensure it is of sufficient capacity
    USB device has insufficient capacity 
  • to ensure there is enough space on it
    USB device has insufficient space 
  • to ensure it is in the right format
    USB device not in the right format 

Why can't I see the USB screen?

You won't see this screen if:

  • the use of USB media is prohibited in your environment
  • we haven't asked for it
  • if there is enough storage space in the the local cache to hold for the required content

What devices are supported by WSA and why are they used?

Any peripheral device that plugs into the PC via the USB port as long as it is formatted to the NTFS file system. These devices are used to hold Packages for Task Sequences and USMT data. Whether these devices can be used or not depends on how the WSA deployment was configured.

What happens if the USB drive is full?

If the USB device does not have sufficient space during the download check process, you will need to make space or provide in a USB device with enough space.

What happens to the personal data on the USB device? Will it be deleted?

Any data outside the  1EWSA  folder is preserved.

Can I copy or move WSA data from one USB device to another?

You can copy or move the 1EWSA folder from one USB device to another as long as you ensure that the storage space on the new USB device meets the original requirements determined in the estimation process.

The Connections screen

Getting details for the remote connectionObservations

The Connection screen

Only displayed:

From Shopping 6.0, WSA will attempt to prepopulate the WiFi password field from the user's WiFi profile. If the password cannot be retrieved the field will remain blank and the user will need to enter the password manually.


I'm connecting remotely. Why can't I see this screen?

You'll only see this screen if your Shopping administrator has asked you to provide your VPN or wireless credentials and if:

The Summary screen

 

A quick summaryObservations

The Summary screen

Always displayed to show the user what is going to take place for this deployment.
The Readiness screen

Making sure you are good to goObservations

The Readiness screen

These checks are run twice – of particular interest is the Content Download Checks:

  • On the first pass, the test is to ensure that the content has been successfully downloaded
  • On the second pass, the test is to verify that the content is not corrupt, if it is, a System Error is displayed
  • All other checks are repeated – you may have left you computer for a considerable amount of time and these tests are to ensure that nothing has changed in the meantime

When readiness checks are complete without errors:
Readiness checks complete 

Errors:

  • Impediments – if any of these are discovered, the deployment can continue only if the user resolves them
    System running on battery 
  • terminal errors – if any of these are discovered during the readiness checks, the deployment cannot continue until they are resolved
    System check error 
  • task sequence fails to run – if you do not see the task sequence running in the background, we recommend you inform the administrator so that they can investigate the issue
    Task sequence not running in the background 


The Complete screen

The results of the deploymentObservations

The Complete screen

If these errors are reported, they will need to be resolved before you can rerun the deployment:

  • Unable to upgrade to Window 10
    Error reporting on the Complete screen 
  • Unable to establish remote connections (VPN or WiFi)


The Computer Refresh scenario is used to upgrade the computer you are currently using. It is also known as Wipe and Load, and differs from an In-place Upgrade because it wipes the disk clean, and only restores the data, settings, and applications that are needed.

Non-destructive means data and settings are backed up to a special area of the disk (if there is space) and automatically restored. 

 Click here to view the Wipe and Load (Non-destructive) user experience...

The user experience

This section describes what users experience when they choose to reinstall Windows on their computer which does not include steps to partition or format the disk. In each phase of the deployment, we will illustrate what is likely to happen.

There are eight phases you can have for this deployment type:

  1. Choosing the deployment
  2. Telling us where they are 
  3. Showing them the list of applications they keep or lose in the deployment
  4. Files and folders they can choose to backup
  5. Requesting additional storage
  6. Displaying a summary of their actions
  7. Running background checks
  8. The outcome of the deployment


Walking your through the user experience

Banner on the Shopping Web

Start hereObservations

Banner on the Shopping Web

Why can't I see the banner on the Shopping web?

If you can't see the banner on the Shopping web, it is likely that:

  • you or the device you are using may not yet be associated with the groups that can do this
  • your Shopping administrator has not created a Windows Servicing Assistant banner or Windows Servicing Assistant Deployment
The Start screen

Choosing the type of deploymentObservations

The Summary screen

Always displayed for you to choose the type of deployment you want.
The Location screen

Where the deployment is initiated fromObservations

The Location screen

Displayed for you to tell us where you are initiating the deployment from.

Why can't I see the Location screen?

You will not see this screen if:

The Applications screen

Changes to applicationsObservations

Only displayed:

The list will show applications that will be retained, replaced or upgraded by Application Migration rules. Installed applications that are normalized in the catalog for which no Application Migration rule exists will show the New state to be Removed. Applications excluded in the Application Migration admin UI will not be included in this list.

Why can't I see the Applications screen?

You won't see the list of applications:

The User Backup screen

Files and folders to be backed-upObservations

The User Backup screen

Only displayed:


When you have made your selection, a prompt is displayed.

The User Backup

The deployment cannot continue unless this is resolved.

Prompt that a service may be down
The USB Media screen

Requesting additional storageObservations

The USB Media screen

Only displayed:


A series of checks are made when a USB device is discovered:

  • to ensure it is of sufficient capacity
    USB device has insufficient capacity
  • to ensure that there is enough space on it
    USB device has insufficient space
  • to ensure it is in the right format
    USB device not in the right format

Why can't I see the USB screen?

You won't see this screen if:

  • the use of USB media is prohibited in your environment
  • we haven't asked for it
  • if there is enough storage space in the the local cache to hold for the required content

What devices are supported by WSA and why are they used?

Any peripheral device that plugs into the PC via the USB port as long as it is formatted to the NTFS file system. These devices are used to hold Packages for Task Sequences and USMT data. Whether these devices can be used or not depends on how the WSA deployment was configured.

What happens if the USB drive is full?

If the USB device does not have sufficient space during the download check process, you will need to make space or provide in a USB device with enough space.

What happens to the personal data on the USB device? Will it be deleted?

Any data outside the  1EWSA  folder is preserved.

Can I copy or move WSA data from one USB device to another?

You can copy or move the 1EWSA folder from one USB device to another as long as you ensure that the storage space on the new USB device meets the original requirements determined in the estimation process.




The Summary screen

A quick summaryObservations

The Summary screen

Always displayed to show you what is going to take place for this deployment.
The Readiness screen

Making sure you are good to goObservations


The Readiness screen


These checks are run twice – of particular interest is the Content Download Checks:

  • On the first pass, the test is to ensure that the content has been successfully downloaded
  • On the second pass, the test is to verify that the content is not corrupt, if it is, a System Error is displayed
  • All other checks are repeated – you may have left you computer for a considerable amount of time and these tests are to ensure that nothing has changed in the meantime

When readiness checks are complete and no errors are encountered:
Readiness checks complete 


Errors:

  • impediments – if any of these are discovered, the deploy can continue only if the user resolves them:
    • System running on battery – use mains power
      System running on battery 
    • System running on WiFi – use a wired connection
    • USB device not connected or properly connected – check USB device
    • terminal errors – if any of these are discovered, the deployment cannot continue until they are resolved:
    • System check errors
      Readiness check system error 
    • task sequence fails to run – if you do not see the task sequence running in the background, we recommend you inform the administrator so that they can investigate the issue
      Task sequence running in the background


The Complete screen

The results of the deploymentObservations


The Complete screen

If these errors are reported, they will need to be resolved before you can rerun the deployment.

If you are running this remotely and do not see the complete screen after a considerable time, reestablish your remote connection manually to see the outcome of the deployment.

  • Unable to reinstall Windows
    Unable to reinstall Windows 
  • Unable to establish remote connections (VPN or WiFi)


Destructive means the computer disk needs to be reformatted, requiring data and settings to be backed up (captured) elsewhere and later restored. 

 Click here to view the Wipe and Load (Destructive) user experience...

The user experience

This section describes what users experience when they choose to reinstall Windows on their computer which involves partitioning or formatting a disk. In each phase of the deployment, we will illustrate what is likely to happen and how to mitigate errors when they arise.

There are eight phases you can have for this deployment type:

  1. Choosing the deployment
  2. Telling us where they are 
  3. Showing them the list of applications they keep or lose in the deployment
  4. Files and folders they can choose to backup
  5. Requesting additional storage
  6. Displaying a summary of their actions
  7. Running background checks
  8. The outcome of the deployment

Walking your through the user experience

Banner on the Shopping Web

Start hereObservations

Banner on the Shopping Web

Why can't I see the banner on the Shopping web?

If you can't see the banner on the Shopping web, it is likely that:

  • you or the device you are using may not yet be associated with the groups that can do this
  • your Shopping administrator has not created a Windows Servicing Assistant banner or Windows Servicing Assistant Deployment
The Start screen

Choosing the type of deploymentObservations

The Start screen

Always displayed for you to choose the type of deployment you want.

The Location screen

Where the deployment is initiated fromObservations

The Location screen

Displayed for you to tell us where you are initiating the deployment from.

Why can't I see the Location screen?

You will not see this screen if:

The Applications screen

Changes to applicationsObservations

Only displayed:

The list will show applications that will be retained, replaced or upgraded by Application Migration rules. Installed applications that are normalized in the catalog for which no Application Migration rule exists will show the New state to be Removed. Applications excluded in the Application Migration admin UI will not be included in this list.

Why can't I see the Applications screen?

You won't see the list of applications:

The User Backup screen

Files and folders to be backed-upObservations

The User Backup screen

Only displayed:

When you have made your selection, a prompt is displayed. 

The User Backup

The deployment cannot continue unless this is resolved.

Prompt that a service may be down

Why can't I see the User Backup screen to backup my files up?

You can only see this screen if you asked us to:

  • migrate you from your existing PC to a new one
  • wipe your existing PC as part of the OS deployment and install a fresh one whilst maintaining all your data on the hard drive
  • wipe your existing PC as part of the OS deployment and install a fresh one without maintaining any of your existing data on the hard drive

Why can't I back up any files or folders even though I can see the User Backup screen?

Your Shopping administrator hasn't allowed you to do so even though the screen is displayed when you asked us to :

Why can't I select some folders?

Your Shopping administrator hasn't allowed you to do so.


The USB Media screen

Requesting additional storageObservations

The USB Media screen

Only displayed:

A series of checks are made when a USB device is discovered:

  • to ensure it is of sufficient capacity
    USB device has insufficient capacity
  • to ensure that there is enough space on it
    USB device has insufficient space
  • to ensure it is in the right format
    USB device not in the right format

Why can't I see the USB screen?

You won't see this screen if:

  • the use of USB media is prohibited in your environment
  • we haven't asked for it
  • if there is enough storage space in the the local cache to hold for the required content

What devices are supported by WSA and why are they used?

Any peripheral device that plugs into the PC via the USB port as long as it is formatted to the NTFS file system. These devices are used to hold Packages for Task Sequences and USMT data. Whether these devices can be used or not depends on how the WSA deployment was configured.

What happens if the USB drive is full?

If the USB device does not have sufficient space during the download check process, you will need to make space or provide in a USB device with enough space.

What happens to the personal data on the USB device? Will it be deleted?

Any data outside the  1EWSA  folder is preserved.

Can I copy or move WSA data from one USB device to another?

You can copy or move the 1EWSA folder from one USB device to another as long as you ensure that the storage space on the new USB device meets the original requirements determined in the estimation process.




The Connection screen

Getting details for the remote connectionObservations

The Connections screen

Connection credentials are mandatory:
Connection credentials are mandatory 

I'm connecting remotely. Why can't I see this screen?

You'll only see this screen if your Shopping administrator has asked you to provide your VPN or wireless credentials and if:


The Summary screen

A quick summaryObservations

The Summary screen

Always displayed to show you what is going to take place for this deployment.
The Readiness screen

Making sure you are good to goObservations

The Readiness screen

These checks are run twice – of particular interest is the Content Download Checks:

  • On the first pass, the test is to ensure that the content has been successfully downloaded
  • On the second pass, the test is to verify that the content is not corrupt, if it is, a System Error is displayed
  • All other checks are repeated – you may have left you computer for a considerable amount of time and these tests are to ensure that nothing has changed in the meantime

When readiness checks are complete and no errors are encountered:
Completed readiness checks 

Errors:

  • impediments – if any of these are discovered, the deploy can continue only if the user resolves them:
    • System running on battery – use mains power
      System running on battry 
    • System running on WiFi – use a wired connection
    • USB device not connected or properly connected – check USB device
  • terminal errors – if any of these are discovered, the deployment cannot continue until they are resolved:
    • System check errors
      Readiness check system error 
    • task sequence fails to run – if you do not see the task sequence running in the background, we recommend you inform the administrator so that they can investigate the issue
      Task sequence running in the background


The Complete screen

The results of the deploymentObservations

The Complete screen

If these errors are reported, they will need to be resolved before you can rerun the deployment.

If you are running this remotely and do not see the complete screen after a considerable time, reestablish your remote connection manually to see the outcome of the deployment.

  • Unable to reinstall Windows
    Unable to reinstall Windows
  • Unable to establish remote connections (VPN or WiFi)


The Computer Replace scenario is used to replace your computer. You run the WSA wizard once on your old computer to back up (capture) data and settings, and again on your new computer to restore them.

 Click here to view the Capture Data and Settings user experience...

The user experience

This section describes what users experience when they choose to prepare their old computer for replacement. In each phase of the deployment, we will illustrate what is likely to happen and how to mitigate errors when they arise. 

There are eleven phases you can have for this deployment type:

  1. Choosing the deployment
  2. Telling us where they are
  3. Showing them the list of applications they keep or lose in the deployment
  4. Getting details of the new computer
  5. Discovering the new computer on the network
  6. Files and folders they can choose to backup
  7. Requesting additional storage
  8. Connecting remotely
  9. Displaying a summary of their actions
  10. Running background checks
  11. The outcome of the deployment

Walking you through the user experience

Banner on the Shopping Web
Start hereObservations

Banner on the Shopping Web

Why can't I see the banner on the Shopping web?

If you can't see the banner on the Shopping web, it is likely that:

  • you or the device you are using may not yet be associated with the groups that can do this
  • your Shopping administrator has not created a Windows Servicing Assistant banner or Windows Servicing Assistant Deployment
The Start screen

Choosing the type of deploymentObservations

The Start screen

Always displayed for you to choose the type of deployment you want.

The Location screen

The Location screen

Where the deployment is initiated fromObservations

Displayed for you to tell us where you are initiating the deployment from.

Why can't I see the Location screen?

You will not see this screen if:

The Applications screen

Changes to applicationsObservations

Only displayed:

The list will show applications that will be retained, replaced or upgraded by Application Migration rules. Installed applications that are normalized in the catalog for which no Application Migration rule exists will show the New state to be Removed. Applications excluded in the Application Migration admin UI will not be included in this list.


The New PC screen

Getting information on the new computerObservations

The New PC screen

Only displayed:

Tip for discovering the name of the new computer.

Tip for discovering new PC name

Why can't I see the New PC screen?

You will only see this screen if you asked for your existing PC to be migrated to a new one and chose the Prepare My Old PC for Replacement option on the Start screen and either of the following is true:

  • your Shopping administrator has configured a new PC name for you
  • your Shopping administrator has allowed you to enter a new PC name

The Network screen

Discovering the computer on the networkObservations

The Network screen

Only displayed:

Why can't I see the Network screen?

You will only see this screen if you asked for your existing PC to be migrated to a new one and chose the Prepare My Old PC for Replacement option on the Start screen.

What do I do if it can't find my PC on the network?

You can continue by choosing the No option. The restore will not happen automatically. You will have to login to New PC and initiate the Restore deployment.


The User Backup screen

Files and folders to be backup-upObservations

Only displayed:

If the user elects to back up their files and folders, it will take several minutes to determine the storage requirements for the backup.

Prompt to ensure items to backup are correctly selected

Why can't I see the User Backup screen to backup my files up?

You can only see this screen if you asked us to:

  • migrate you from your existing PC to a new one
  • wipe your existing PC as part of the OS deployment and install a fresh one whilst maintaining all your data on the hard drive
  • wipe your existing PC as part of the OS deployment and install a fresh one without maintaining any of your existing data on the hard drive

Why can't I back up any files or folders even though I can see the User Backup screen?

Your Shopping administrator hasn't allowed you to do so even though the screen is displayed when you asked us to :

Why can't I select some folders?

Your Shopping administrator hasn't allowed you to do so.

The USB Media screen

Requesting additional storageObservations

Only displayed:

A series of checks are made when a USB device is discovered:

  • to ensure it is of sufficient capacity
    USB device too small for backing up data
  • to ensure there is enough space on it
    Insufficient space on the USB device
  • to ensure it is in the right format
    USB device not in the right format

Why can't I see the USB screen?

You won't see this screen if:

  • the use of USB media is prohibited in your environment
  • we haven't asked for it
  • if there is enough storage space in the the local cache to hold for the required content

What devices are supported by WSA and why are they used?

Any peripheral device that plugs into the PC via the USB port as long as it is formatted to the NTFS file system. These devices are used to hold Packages for Task Sequences and USMT data. Whether these devices can be used or not depends on how the WSA deployment was configured.

What happens if the USB drive is full?

If the USB device does not have sufficient space during the download check process, you will need to make space or provide in a USB device with enough space.

What happens to the personal data on the USB device? Will it be deleted?

Any data outside the  1EWSA  folder is preserved.

Can I copy or move WSA data from one USB device to another?

You can copy or move the 1EWSA folder from one USB device to another as long as you ensure that the storage space on the new USB device meets the original requirements determined in the estimation process.

The Summary screen

A quick summaryObservations

The Summary screen

Always displayed to show you what is going to take place for this deployment.

The Readiness screen

Making sure you are good to goObservations

These checks are run twice – of particular interest is the Content Download Checks:

  • On the first pass, the test is to ensure that the content has been successfully downloaded
  • On the second pass, the test is to verify that the content is not corrupt, if it is, a System Error is displayed
  • All other checks are repeated – you may have left you computer for a considerable amount of time and these tests are to ensure that nothing has changed in the meantime

When readiness checks are completed and no errors are encountered:
 

  • Errors:
    • impediments – if any of these are discovered, the deployment can continue only if the user resolves them 
      • System running on battery – use mains power
      • System running on WiFi – use a wired connection
      • USB device not connected or properly connected – check connected USB device
    • terminal errors – if any of these are discovered, the deployment cannot continue until they are resolved.
      System check error 
    • task sequence fails to run – if you do not see the task sequence running in the background, we recommend you inform the administrator so that they can investigate the issue
      Task sequence running in the background


The Complete screen

The results of the deploymentObservations

You must login to your new computer and run the Restore deployment so that we can restore your data and applications to it to complete the migration.

The Restore My Data and Apps to a New PC Start screen

If these errors are reported, they will need to be resolved before you can rerun the deployment:

  • Unable to prepare you old PC for replacement
     
  • Unable to establish remote connections (VPN or WiFi)


 Click here to view the Restore User Data and Applications user experience...

The user experience

This section describes what users experience when they choose to restore their data and applications to a new computer. In each phase of the deployment, we will illustrate what is likely to happen and how to mitigate errors when they arise.

There are five phases you can have for this deployment type:

  1. Choosing the deployment
  2. Getting the name of the machine to restore data from
  3. Displaying a summary of their actions
  4. Running background checks
  5. The outcome of the deployment

Walking you through the user experience

Banner on the Shopping Web
Start hereObservations

Banner on the Shopping Web

Why can't I see the banner on the Shopping web?

If you can't see the banner on the Shopping web, it is likely that:

  • you or the device you are using may not yet be associated with the groups that can do this
  • your Shopping administrator has not created a Windows Servicing Assistant banner or Windows Servicing Assistant Deployment
The Start screen

Choosing the type of deploymentObservations

The Start screen

Always displayed for you to choose the type of deployment you want.
The Old PC screen

Locating the old computerObservations

The Old PC screen

You won't see the Location screen as you are restoring data and applications from a previous machine to this one. You made the computer association when you ran the Replace Capture deployment and you told us about your new PC.

Unable to locate your old PC

The USB Media screen

Requesting additional storageObservations

Only displayed if a USB device was required when you ran the Replace Capture deployment.

The Summary screen

A quick summaryObservations

The Summary screen

Always displayed to show you what is going to take place for this deployment.
The Readiness screen

A quick summaryObservations

The Readiness screen

These checks are run twice – of particular interest is the Content Download Checks:

  • On the first pass, the test is to ensure that the content has been successfully downloaded
  • On the second pass, the test is to verify that the content is not corrupt, if it is, a System Error is displayed
  • All other checks are repeated – you may have left you computer for a considerable amount of time and these tests are to ensure that nothing has changed in the meantime

When readiness checks are completed and no errors are encountered:

Readiness checks done

  • Errors
  • impediments – if any of these are discovered, the deployment can continue only if the user resolves them:
    • System running on battery – use mains power
      System running on battery 
    • System running on WiFi – use a wired connection
    • USB device not connected or properly connected – check connected USB device
  • terminal errors – if any of these are discovered during the readiness checks, the deployment cannot continue until they are resolved:
  • task sequence fails to run – if you do not see the task sequence running in the background, we recommend you inform the administrator so that they can investigate the issue
    Task sequence running in the background


The Complete screen

The results of the deploymentObservations

The Complete screen

If these issues are reported, they must be resolved before you can rerun the deployment:

  • Unable to restore data and apps to a new computer
    Unable to restore your data and applicatoins
  • Unable to establish remote connections (VPN or WiFi) 


Reporting on Windows Servicing Assistant Deployments

The Windows Servicing Assistant sends status updates to Shopping. The status of all active Windows Servicing Assistant deployments can be viewed from the Shopping Web Administration interface by selecting the Track WSA Order option from the OS Migration menu.