To help you get up and running quickly, we've organized the documentation into the following sections:

  1. Introducing Shopping – if you're new to Shopping 5.5.200 or just want a quick refresh, we recommend you read this section
  2. Implementation – everything you need to know to get Shopping running in your environment. We talk about:
    • Preparation – the accounts and permissions you need and things you should be aware of
    • Prerequisites – a definitive list of prerequisites and dependencies for Shopping
    • Installation – how to install or upgrade Shopping
  3. Working with Shopping:
  4. Reference – a list of registry values, installer properties, application properties
  5. Release notes – late breaking news for the Shopping 5.5.200 release. 

What's new in this release?

This release introduces the following enhancements, all relating to Windows Servicing Assistant:

  • Applications page in Windows Servicing Assistant includes all installed, normalized applications
    In previous versions of Shopping, the Applications page in the Windows Servicing Assistant showed only applications that would be upgraded or replaced. It did not show applications that would be retained, or applications that would not be migrated because there were no applicable migration rules. The Applications page now shows all installed applications that have been normalized in the 1E Catalog and have not been excluded in Application Migration. For an In-place Upgrade, applications that have no applicable migration rule will be retained and the current version of the application will be shown in the ‘New’ column. For Wipe and load or Replace, applications that have no applicable migration rule will indicate ‘Removed’ in the ‘New’ column. In addition to this change, if the Applications in OS Image list in the Applications tab of the WSA application settings is empty, it will not be displayed on the WSA applications page, leaving more space for the list of installed applications.
  • Allow conditional download of Windows 10 upgrade packages with Windows Servicing Assistant
    An In-place Upgrade task sequence may include multiple Upgrade Operating System steps that use different OS upgrade packages (e.g. when using a single task sequence to support multiple OS locales). In previous versions, WSA would download all OS upgrade packages. It is now possible to have WSA selectively download the upgrade package that matches the architecture and locale of the current OS. This is implemented on the Storage tab of the In-place Upgrade WSA Application settings.
  • Check Windows 10 version in Windows Servicing Assistant readiness checks before upgrading
    The Windows Servicing Assistant now includes a check to prevent an In-place Upgrade task sequence from executing on a device if the upgrade package in the task sequence is for the same or an older version of Windows 10 to that already installed. This is implemented as an additional checkbox in the Readiness tab of the In-place Upgrade WSA Application settings.
  • Perform In-place Upgrade compatibility check in Windows Servicing Assistant readiness checks
    You can now include Windows 10 upgrade compatibility check in the readiness checks for an In-place Upgrade WSA Application. This feature is implemented as an additional check box in the Readiness tab of the In-place Upgrade WSA Application settings. When enabled, during the readiness checks, WSA will download the upgrade package and execute setup.exe /Auto Upgrade /Quiet /NoReboot /DynamicUpdate Disable /Compat ScanOnly. Optionally, an administrator can choose to ignore any warnings generated during the compatibility check by checking the Ignore any dismissible compatibility messages checkbox, which adds /Compat IgnoreWarning to the setup/.exe command line. If the compatibility checks fail, WSA will report the issue to the user and through the WSA Order Tracking, and will not attempt to run the task sequence.
  • Improve hash-check efficiency in Windows Servicing Assistant
    The Windows Servicing Assistant performs readiness checks when the user reaches the Readiness stage of the wizard. If the user selects ‘I want to continue working…’ from this page, the user is notified when the checks have completed, but by design they will run again when the user re-opens the wizard and selects ‘I’m done. Go ahead…’. This is by design, as things may have changed between the user receiving the notification and actually starting the deployment. However the readiness checks include hash-checking the content that has been downloaded, which can be time consuming and confusing to the user. Now, although the readiness checks will be rerun, content hash checking will not be repeated if it has been completed in the last 30 minutes. This period is configurable (between 0 and 480 minutes, where 0 means always rerun the hash checks) and the feature is implemented on the Storage tab in each of the WSA Application settings pages.
  • Allow Windows Servicing Assistant to exclude user state migration
    In previous versions, the Windows Servicing Assistant expected to find steps in the task sequence for migrating user data and settings with the User State Migration Tool. Some customers requested the ability to exclude user data and settings migration. This has now been implemented as an additional check-box labelled ‘Do not capture user files and settings’ in the Data Capture tab in the Wipe and Load and Replace Capture WSA Application settings. When this option is enabled, all other settings on the Data Capture tab are disabled and WSA will not attempt to calculate space required for user data migration or locate peer storage. When the task sequence executes, the WSA Actions – Initialize step will set a variable named 1ESkipUserStateCapture will be created and set to True. If the task sequence includes groups or steps to capture or restore data, these groups or steps should be conditioned to only execute if 1ESkipUserStateCapture is not equal to true.

    This feature requires Nomad hotfix Q20391 (Nomad Branch client), which updates the WSA Actions - Initialize step to create and set the 1ESkipUserStateCapture variable based on the 'Do not capture user files and settings' setting.



Copyright and trademark notices

All rights reserved. No part of this document or of the software (“the software”) to which it relates shall be reproduced, adapted, stored in a retrieval system, or transmitted by any means, electronic, mechanical, photocopying, recording, or otherwise, without permission from 1E Ltd. It is the responsibility of the user to use the software in accordance with this document and 1E Ltd shall not be responsible if the user fails to do so. Although every precaution has been taken in the preparation of this document, 1E Ltd and the authors assume no responsibility for errors or omissions, nor shall they be liable for damages resulting from any information in it.


1E, the 1E device, TACHYON, APPCLARITY, ACTIVEEFFICIENCY, NIGHTWATCHMAN, NOMAD BRANCH, NOMAD ENTERPRISE, PXE EVERYWHERE, DROWSY and DROWSY SERVER are trademarks belonging to 1E Ltd. 1E is registered in the UK, EU and the US. The 1E device is registered in the UK, EU, Australia and the US. NIGHTWATCHMAN is registered in the EU and the US. Nomad is registered in the EU and the US. DROWSY is registered in the UK. DROWSY SERVER is registered in the US.

MICROSOFT, WINDOWS, WINDOWS 7, WINDOWS VISTA, WINDOWS XP, SMS, CONFIGURATION MANAGER, INTERNET EXPLORER are all trademarks of Microsoft Corporation in the United States and other countries.

Mac is a trademark of Apple Inc., registered in the U.S. and other countries.