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.
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:
Due to the limited user interaction, they are useful in the following situations:
To publish an OS deployment Task Sequence in the Shopping portal using a ConfigMgr Application:
Wizard-based self-service OS Deployment was first introduced in Shopping 4.0 using OSD Applications. 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.
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:
They are useful in the following situations:
To publish an OSD Application to the Shopping portal:
New to Shopping 5.5 is the Windows Servicing Assistant (WSA) Deployment Application.
WSA Applications are similar to, but slightly different from OSD Applications in the following ways:
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:
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:
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:
To publish Windows Servicing Assistant Deployment Applications to the Shopping portal:
Refer to Creating Windows Servicing Assistant Deployment Applications for details on completing the above steps.
To understand the Windows Servicing Assistant user experience, see:
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.