Self-service Windows Migration

Shopping can be used to allow users to request to have their computer migrated to the latest version of Windows. Enabling a user to choose to install the latest operating system from an AppStore type interface can be very beneficial to accelerating adoption of the latest supported release of Windows – it's an experience they're familiar with in their personal lives with phones and tablets and personal computers. 

This feature of Shopping uses the Operating System Deployment (OSD) feature of ConfigMgr and the OS Deployment Application type in Shopping. In this lab, you will configure Shopping to offer a Windows 10 migration option to users and then run through the process from the user's perspective.

Configuring an OS Deployment Application

In this exercise, we will prepare the objects in ConfigMgr and Shopping necessary to enable self-service of an operating system refresh. An OSD Task Sequence has already been prepared in ConfigMgr and deployed to the Windows 10 Shopping Deployment Collection. In this exercise, we will create and configure the OSD Application in Shopping.

Create an OS Deployment Application in Shopping

You will now create an OS Deployment application in Shopping to enable users to request a rebuild of their workstation.

759. Log on to 1ETRNAP as ShoppingAdmin and open the Shopping Administration Console
760. Right-click the Applications node and select New OS Deployment to launch the New OS Deployment Wizard. Click Next on the welcome page
761. Complete the General Details page with the following properties and click Next
Name          Windows 10 Enterprise
Description Install the latest Microsoft desktop operating system
Cost            0.00
Icon            choose an icon
762. On the SMS/ConfigMgr Collection page, select the Windows 10 Shopping Deployment Collection then select SimpleWindows10Ent_PS100041_Windows10ShoppingDeployment from the Advertisement drop-down. Click Next




Advertisement is a legacy ConfigMgr 2007 term for Deployment. We are selecting the deployment here.
763. On the Permissions page, click Next
The Permissions page is used to restrict availability of this particular OS Deployment Application to specific users and/or computers. Administrators can use this to enforce some level of staging while allowing users to self-serve their OS migration. For example, if an AD user group is added to the User Permissions list, an administrator can simply add users into that group when they become eligible for the migration. Similar controls can be applied to computers, with the additional ability to define OUs (so an administrator can add new OUs from time to time according to the migration schedule). If no restrictions are defined here, the Application will be available to all users and to all computers.
764. Click Finish to close the wizard

Configure the Windows Deployment Application

765. From the Shopping console double-click the Windows 10 Enterprise Application to open the Application's properties dialog box
766. Select the CoreApplications tab




Core Applications is simply a free-form list of software that is included in the core OS image or installed as part of the Task Sequence. It has no correlation to Applications already defined in Shopping and is presented to the user for information purposes only in the OS Migration Wizard when they request an OS migration. This helps them determine which applications they should select in the Wizard to be reinstalled after the build completes.
Items can only be added or removed from the Core Applications list. You cannot edit existing items or change the order in which the items appear in the list (new items are added to the bottom of the list).
767. Add one or two items to the list (e.g. Microsoft Office 365) so you can see how they appear to the end user later on
768. Select the Schedule tab and note the available settings
769. Check the Enable Scheduling Restriction box, and leave the time range default
When a user runs the OS Migration Wizard in the Shopping Portal, they schedule the migration to occur at a time suitable to them by selecting a time slot on a specific date. The Schedule tab in the OS Deployment Application properties allows the administrator to impose some constraints on the timeslots that are available to the user. These constraints include limiting the number of deployments that can be scheduled on any given day, preventing users from scheduling their deployment before or after specific dates, excluding certain timeslots every weekday and/or weekend or excluding whole days, either specific dates or one or more specific days every week (e.g. exclude all Mondays).
If changes are made to the schedule while there are OS Deployment requests already scheduled, the changes may result in some of these requests being cancelled (for example if they were scheduled during a time that has now been excluded). The user will receive email notification that the deployment has been cancelled, and they will need to reschedule according to the latest restrictions. Be sure to manage the time constraints ahead of making the OSD application available to the end users.
770. Click OK to close the Windows 10 Enterprise – OS Deployment Properties dialog box
771. Click YES in the warning that appears indicating that you have changed the schedule

Create an OSD banner to display the application

OSD Applications are not displayed in the Shopping portal in the same way as other Applications. They use the Banner feature of the Shopping v5 user interface, which requires a banner to be defined that will be used for all OSD Applications. In this task, you will create that banner so the users can request the new Operating System.

772. On 1ETRNAP logged in as ShoppingAdmin, open the Shopping portal (website)
773. Select the Administration tab in the navigation panel and select Manage Banners
774. On the Banners List page click the Create New link to open the Create Banner page
775. Select OSD for the application type
776. In the Application Name field, input Windows 10 Enterprise application is suggested. Select this




If you named your OSD Application something else, you will need to reference that title. The wizard references OSD Applications created in the Shopping console to populate this.
777. The Title and Abstract fields are automatically populated with the Application Name and Description respectively




These fields are superimposed on the banner image when viewed by the user in the Shopping portal. You can change these if you like, but Title field cannot be blank.
778. From the Skytap Shared Drive folder on the desktop navigate to 1E Shopping - Course Content\Shopping 5.6 Course Content\ and download the ShoppingIcons.zip to C:\Temp and extract the folder
779. Click the Browse button to the right of the unlabelled box and browse to C:\Temp\ShoppingIcons\Win10-Lite.png




This field defines the graphic image that will be used as the background for the banner.
780. Click CREATE to create the new banner and return to the Banners list page
781. Close the Shopping portal

Performing an Operating System Refresh

In this exercise, you will request an Operating System Refresh from the Shopping portal to migrate 1ETRNW73 to Windows 10.

Schedule the OS Refresh

You will now launch the Windows Migration Wizard from the Shopping portal to initiate the migration of 1ETRNW73 to Windows 10.

782. Log onto 1ETRNW73 as user and open the Shopping portal. If the portal is already open, click on Home to get to the home page
783. Note there is now a Windows 10 Enterprise banner on the home page. Click the Launch button to start the Windows Migration Wizard
784. On the Introduction page, click Next
785. On the Select OS page note there is only one OS option available as there is only one OS Deployment Application defined. Click Next
786. The Re-install Apps page shows the Core Applications you entered previously on the left and the applications that have been installed by Shopping on the right. By default, all applications previously installed by Shopping will be reinstalled by Shopping as part of the migration. The user can optionally uncheck applications they no longer require
787. Uncheck Pro Photo Tools and click Next
788. On the Schedule page, click on the field labelled Schedule migration date to open the calendar control. Any dates excluded through the Schedule properties for this OS Deployment Application in the previous exercise will be greyed out and unavailable for the user to select. Ensure today's date is selected
789. Click the field labelled Schedule migration time to open the timeslot control. Again, any timeslots excluded in the Schedule properties will not be available. Note that the earliest time you can schedule the deployment is at the top of the hour. Select the next available timeslot and click Next
790. Note that the user must acknowledge that they have backed up their system before continuing with the deployment. This message can be customized, but there should always be some confirmation before the user can finish the wizard
791. Check the confirmation box and click Finish
792. Note the banner on the Shopping home page now has three buttons (EDIT, CANCEL and CALENDAR)
793. Click the EDIT button. This runs the wizard again allowing the user to select a different OS (if available), change the Applications to be re-installed after deployment and, perhaps more importantly, change the schedule
794. The CANCEL button allows the user to cancel the OS deployment entirely. Close the wizard by clicking on the X in the top right
795. Click the CALENDAR button. This allows the user to download an OS Upgrade.ics file that can be added to their Outlook calendar (Outlook is not installed on the workstations in this lab). The appointment is for 3 hours, starting at the time slot selected by the user in the OS Migration Wizard. The user can also set a reminder




Other users who log on to the Shopping portal from this computer will see the same banner, but will not have the option to edit the deployment. They can however cancel it or add it to their own Outlook Calendar.
796. Click Edit, click through to the Schedule page, and check the Schedule Immediately box and click through to the end of the wizard
797. Within approximately 10 minutes, the Simple Windows 10 Deployment Task Sequence should start to execute
Due to a bug in ConfigMgr, a 'required' TS fails on the first try. You can validate this in the execmgr.log file.It will take an additional 10 minutes for the TS to begin. Take a quick bathroom break.
The TS will run for approximately an hour. Once it starts, you have validated Shopping's role in the process. Move on to the next lab.

Observe the process in Shopping

While 1ETRNW73 rebuilds, you can trace the process through the Shopping log files.

798. On 1ETRNAP, open the Shopping log file (C:\ProgramData\1E\Shopping\Shopping.log) and note the Osd.Controller messages that are logged when the OSD migration wizard is run

799. Log on to 1ETRNCM as SCCMAdmin and launch the ConfigMgr console
800. From the Assets and Compliance workspace, navigate to Device Collections
801. Double click the Windows 10 Shopping Deployment and confirm 1ETRNW73 has been added to the collection
802. Open the Shopping Receiver log file (C:\ProgramData\1E\Shopping.Receiver\v5.6.0\Shopping.Receiver.log)

Review the post-deployment process

In this task, you will observe what happens after the computer is rebuilt.

804. Log on to 1ETRNW71 as User and open Windows Live Mail
805. Note that the user has received an email from Shopping confirming the OS Deployment on 1ETRNW73 has been successful
This is useful if the user has left their computer rebuilding but may still be receiving their email on a mobile device.

806. On 1ETRNCM logged on as SCCMAdmin, open the Shopping Receiver log (C:\ProgramData\1E\Shopping.Receiver\v5.6.0\Shopping.Receiver.log)
807. Locate the time when the Task Sequence completed and returned a success status. Following this, the Receiver adds the rebuilt computer to the Collections that correspond to the Applications that the user selected in the Re-install Apps page of the Shopping Migration Wizard

OS Deployment on Behalf of Others

As a Shopping administrator, you can now schedule an OS deployment for multiple machines – previously, you had to log in to each machine to schedule the migration. Email notifications are not sent to end-users, as OS deployments are targeted at machines rather than end-users. However, when they login to the Shopping portal, they will be able to see the message in the banner but will not be able to cancel the scheduled migration, as there are no links to alter it – they can only modify self-scheduled OS migrations.

Schedule an OS Deployment for a Group of Computers

In this task, we will schedule an OS Deployment for a small group of machines and observe the results on the Shopping portal on those computers.

808. Open the Shopping portal as 1ETRN\ShoppingAdmin




Note that there is an OSD Banner displayed. This is because we specified no groups in the Permissions section when the OSD Application was created. Do not schedule an OS Deployment on the server!
809. Expand OS Migration on the Administration tab and select Schedule Legacy OSD
810. On the Introduction page, a list of available operating systems would be displayed. In our environment, there is only Windows 10 Enterprise as an available operating system, so click Next to proceed
811. On the Search Machines page, type 1ETRNW7 in the Search field and hit Enter




Note that only two of the Windows 7 machines are displayed here. Know why? Because we already started an OSD migration on 1ETRNW73.
812. Move both 1ETRNW71 and 1ETRNW72 to the Machines To Target field by clicking the > button for each one. Click Next to continue
813. On the Re-install Apps page, click on 1ETRNW71 and observe the Application Post-Migration column, then click on 1ETRNW72 and see how the list is slightly different. Click Next
814. On the Select New Apps page, enter the letter A in the Search field and hit Enter. Observe the Available applications, but do not select any. Click Next
815. On the Schedule page, select a time at least an hour in the future and click Next




We will eventually be cancelling the OS Migration, but we want to have a little time to see what happens.
816. Enter Lab OS Deployment as the OSD Batch Name, check the back-up confirmation box and click Submit

Observe the Results of Scheduling an OS Deployment for Others

817. In the Shopping portal, select the Administration tab, expand OS Migration and select Track Legacy OSD orders
818. Show the details of the Lab OS Deployment OSD Batch Name. Leave the web page open

819. Log out as the currently logged in user and log in as 1ETRN\User
820. Open the Shopping portal
821. Observe the banner and note that it states there is a scheduled OS Deployment by an administrator and that there are no options to edit or cancel it

822. Click Cancel on the scheduled OS deployment for 1ETRNW71
823. Click Yes to confirm the cancellation

824. Refresh the browser on 1ETRNW71 and note how the OSD Banner now appears as normal with an option to launch it
825. Repeat the steps to cancel the scheduled OS Deployment on 1ETRNW72

Lab Summary

In this lab, you have seen how Shopping can be configured and used to enable users to initiate an Operating System refresh on their workstation, selecting the time they would like the migration to occur and the applications they would like reinstalled after the build completes.
We have also observed how a Shopping Administrator can schedule an OS Deployment for a group of machines and set a schedule for it to execute. The end-user can see that there is an OS Deployment scheduled, but is unable to do anything about it. A Shopping Administrator is able to cancel a scheduled OS Deployment for a particular machine.

Next Page
Ex 10 - Shopping 5.6 - Reporting