Install the Shopping receiver on the Configuration Manager site server – for Configuration Manager 2012, it is the primary site or the CAS if you are using multiple primary sites, for Configuration Manager 2007 it is the central site. Installing the Shopping receiver in these locations (as well as on all Configuration Manager 2012 primary sites) enables:

  • OSD functionality (Configuration Manger 2007 and 2012)
  • AppModel functionality (Configuration Manager 2012)
If you intend to install Shopping Central and the Shopping Receiver services on the same machine, 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 Selected ConfigMgr Sites list. This authorises the new Receiver to access the Shopping Central. The procedure for this is described in 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, and has a local installation of a Configuration Manager site.

When running the MSI, please ensure  

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

Running ShoppingReceiver.msi

  1. On the Welcome screen
    • Click Next to continue
  2. On the License Agreement screen
    • 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 continue
  3. On the Install Type screen, 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 may upgrade only, side-by-side installation is not supported.

    • Click Next to continue
  4. On the Destination Folder screen, 
    • Either click Next to accept the default
    • Or click Change to specify a new location. You would not normally change the default location.
  5. On the Receiver Service account screen
  6. On the Policy Refresh screen 
    • Configure how policy refresh is implemented, enable or disable its integration and set the delay for it. The choice determines how the Receiver initiates a policy refresh on the client, effectively enabling a software push to the user's machine. 
    • If the installer detects that 1E WakeUp Server is installed on the same server, then 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 Receiver has added the machine to a collection and wait for Configuration Manager to created the machine policy and replicate it. The delay depends on the Configuration Manger architecture – centralized or distributed
    • Click Next to continue
  7. On the Shopping URL prefix 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 continue
  8. On the Default Advanced Client Flags screen, enter the settings to use for an advertisement in Configuration Manager 2007.
    • 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 continue

  9. On the Ready to Install the Program screen, click Install
  10. After installation, click Finish

Installing the Shopping receiver in unattended mode

To install the Shopping receiver in unattended mode, you must provide the Shopping URL and the Receiver service 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.