Installing the Shopping Receiver on the Microsoft System Center Configuration Manager (ConfigMgr or SCCM) primary site servers enables:

  • Application deployments, using legacy or application model applications
  • Operating system deployments
If you intend to install Shopping Central and the Shopping Receiver services on the same server, install Shopping Central first.

Prior to installation of each Receiver, complete the Preparation steps. 

After installation of each Receiver, you must use the Shopping Admin Console to add the Configuration Manager site to the Sites list. This authorizes the new Receiver to access the Shopping Central server. The procedure for this is described in Setting up Configuration Manager sites.

Installing the Shopping receiver with the wizard

The installer MSI file for the Shopping Receiver is ShoppingReceiver.msi and will run only on a server using a supported server operating system with a local installation of a Configuration Manager site.

When running the MSI, ensure you:

The installer will terminate if a local installation of Configuration Manager site is not detected.

Running ShoppingReceiver.msi

On this page:


This screen provides the version number for the Shopping Receiver and outlines what the wizard will do.

Click Next to go to the next screen.

License Agreement

You must read and then accept this license information by clicking the I accept the terms in the license agreement option before you can continue with the installation.

Click Next to go to the next screen.

Install Type

On the Install Type screen, if displayed, choose:

  • Upgrade – upgrades existing Shopping Receivers to the latest versions
  • Side-by-side installation – installs the latest version of the Shopping Receiver alongside existing ones. Use this option if you intend to run the older versions of the Shopping Receiver in parallel with the latest versions.

    This screen is displayed only if a previous version of the Shopping Receiver is detected.

    If the existing version is Shopping version 4.7 or earlier, you can only upgrade. Side-by-side installation is not supported in that case.

Click Next to go to the next screen.

Destination Folder

On this screen:

  • The default destination folder will be suitable for most installations. Click  Change...  if you want to specify a new location for the installation.

Click Next to go to the next screen.

Receiver Service Account

On this screen:

Click Next to go to the next screen.

Policy Refresh

On this screen:

  • Configure how policy refresh is implemented. Enable or disable its integration and set the refresh delay. The choices determines how the Receiver initiates a policy refresh on the client, effectively enabling a rapid software push to the user's machine 
  • If the installer detects that 1E WakeUp Server is installed on the same server, WakeUp will be the default option. Otherwise Native is the default
  • Selecting WakeUp or Native allows you to specify the Policy Refresh delay in seconds. The default is 10 seconds, which causes WakeUp or Shopping to send a policy refresh 10 seconds after the Shopping Receiver has added the machine to a collection and wait for Configuration Manager to create the machine policy and replicate it. The delay depends on the responsiveness of the Configuration Manger architecture.

Click Next to go to the next screen.

Shopping URL Prefix

On this screen:

  • Set the base URL for the Shopping Central Website so that the Shopping Receiver service can communicate with the Shopping API. You will need to modify the URL prefix and replace the default <ShoppingCentralServer> with the host header for the Shopping website. See the Shopping URL Prefix screen for the Shopping Central installer.

Click Next to go to the next screen.

Default Advanced Client Flags

On this screen enter the settings to use for a default deployment:

  • Default – uses the default advertisement options
  • Always download from DP – the package is always downloaded from the distribution point. This should be used when integrating with Nomad Branch from 1E.
  • Always run from DP – the package is always run from the distribution point.

    These settings affect only packages and not app-model applications whose settings are controlled with Configuration Manager.

    If you have used the installer property DPFLAG on the command-line and given it a value that does not match any of the 3 options on the screen, then none of the options will be selected. In this case, do not select an option, and just click Next to continue to configure the command-line option.

Click Next to go to the next screen.

Configuration Manager Database Connection

On this screen:

  • Check the TLS 1.0 disabled - install using TLS 1.1/1.2 checkbox if TLS 1.0 is disabled in your environment.

Click Next to go to the next screen.

Ready to Install the Program

On this screen:

  • Click Install to start the installation, or use the < Back button to go back and review your settings prior to installation.


On this screen:

  • After installation has completed click Finish to close the wizard.

Installing the Shopping Receiver in unattended mode

To install the Shopping receiver in unattended mode, you must provide the Shopping URL Prefix and the Shopping Receiver service user account and password. Other settings are optional. In the example below the policy refresh setting is confgured to use Native mode even if there is a WakeUp Server already installed, and sets DPLAG to use an option 'Always download from DP' for both Packages and Task Sequences, as decribed in Default and recommended Configuration Manager 2007 advertisement settings.

msiexec /i ShoppingReceiver.msi 
/l*v %temp%\ShoppingReceiver-install.log /qn

The command-line example is separated onto different lines for clarity and is entered on a single line in practice. These and other command-line switches are described in Shopping Receiver installer properties.