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.6 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.6 release. 

What's new in this release?

This release introduces the following improvements, all relating to customer concerns:

  • Performance enhancements
    • Shopping database cleanup
      If the Shopping Records Purge Days setting is set to a non-default value, such as 180, the EmailRetry and OrderHistory tables will be purged of records older than that number of days. Organizations with large Shopping databases will find that this improves Shopping performance, especially including report generation, please refer to Shopping Admin Console settings: Records Purge Days for more details.
    • Order history
      Order history records for computers are deleted when computers are deleted from Shopping.
    • Configuration Manager
      Targeted computers are removed from the relevant Shopping collection after an order is completed. For successful orders, collection rule for the computer is removed from the collection instantly (and the computer itself is removed when the collection is reevaluated), but for failed orders Shopping will wait for the Retry Status Update For Failed Installations for Time Interval value to elapse, please refer to the Shopping Admin Console settings: Retry Status Update For Failed Installations for Time Interval for more details. When upgrading Shopping to version 5.6, computers with completed orders that have previously been added to Configuration Manager device collections are removed.
      When a Shopping Application is deleted from the Shopping Administrator Console (or has been in disabled state for more than 90 days), the corresponding deployments and collections are now also deleted from Microsoft System Center Configuration Manager (ConfigMgr). The disabled state period can be adjusted by changing the Clean Collections or Deployments for Disabled Applications after days setting, please refer to Shopping Admin Console settings: Clean Collections or Deployments for Disabled Applications after days for more details.
    • Order processing for simultaneous order requests
      If you anticipate that Shopping will commonly receive multiple orders at once, you can enable multithreaded processing so that several can be processed concurrently, reducing delays. This can be done by setting the Number of Receiver Order Processing Threads setting to a value between 2 and 5 (inclusive), please refer to Shopping Admin Console settings: Number of Receiver Order Processing Threads for more details. To further optimize the processing, you can increase the Receiver Processing Batch Size value from its default value of 10 to as much as 100, please refer to Shopping Admin Console settings: Receiver Processing Batch Size for more details.
      In either case, you will need to restart the Shopping website and Shopping Receiver service.
    • Workflow Integration for simultaneous order requests
      If you use Shopping's workflow integration and process large numbers of orders concurrently, you can improve its efficiency by increasing the Number of Workflow Threads setting to a value between 2 and 5 (inclusive), please refer to Shopping Admin Console settings: Number of Workflow Threads for more details.
      Restart the ShoppingCentral service for this change to take effect.
  • Security improvements
    • Shopping Receiver does not require administrator privileges on clients
      The Shopping Receiver service account no longer has to have administrator privileges on client computers. Configuration Manager policy refreshes for new requests and re-shopping are now done using the Client Notification feature of Configuration Manager.
  • Easier upgrades
    Shopping Central Installer audits all files in the in the Shopping installation directory tree for modifications done to any files (either manually or through hot fix) other than .dll and .exe files. The modified files are backed up to the Backup_<PREVIOUS_VERSION> folder in the installation directory. This backup allows you to identify all customizations and to re-implement them as needed. Please refer to Upgrading to Shopping 5.6 for more details.
  • Improved status
    Shopping can now update the status of failed requests for up to 3 days. This allows Shopping to accurately reflect Configuration Manager deployment status for deployments that initially failed but succeed on a later retry. Adjust the Retry Status Update For Failed Installations for Time Interval setting in the Shopping Console to change the interval. The default value is 1 day (24 hours). Please refer to Shopping Admin Console settings: Retry Status Update For Failed Installations for Time Interval for more details.

 

 

www.1e.com | Copyright © 1E 2020 All Rights Reserved | Terms and Conditions | Privacy Policy

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.

Trademarks

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.