Installer properties and configuration settings for the Shopping client module of the 1E Client supported only on Windows computers. This module supports users connecting to the Shopping Portal, and provides the Windows Servicing Assistant (WSA).

Installer properties:

Enabling the Shopping client module allows the Windows Servicing Assistant (WSA) feature to be used. There are no additional settings required to enable or configure the WSA feature.

Configuration file settings are the same as the installer properties. There are no registry settings. Configuration file settings can be managed using 1E Client reconfiguration, Tachyon Explorer configuration instructions, Tachyon Guaranteed State policies, Configuration Manager baselines or other means.

On this page:

The Shopping client module of the 1E Client replaces the Shopping Agent used by versions of Shopping before v5.5. When the 1E Client starts, if the Shopping module is enabled the 1E Client will automatically remove any previous installation of the 1E Shopping Agent.

The Shopping client module is not supported on:

  • Non-Windows devices
  • Legacy OS (that is OS which Microsoft no longer support, including XP, Vista, Server 2008 etc.)

Shopping client settings

The table below lists the settings required to enable the Shopping client required for integration with Shopping v5.5 or later. The Shopping client module must be enabled on all Windows computers that will connect to the Shopping self-service portal. 

Shopping module settingInstallation defaultDescription



Set the value to true to enable the Shopping module. The default value is false.

Shopping must be enabled so that users of a computer can use the 1E Shopping self-service portal and the Windows Servicing Assistant.

If enabled, when the 1E Client starts it will attempt to automatically remove any previous installations of the 1E Shopping Agent.



Optional. Set this value to true if users are likely to use Microsoft Edge or other Metro browsers to access the Shopping website. Default value is false.

When users connect to the Shopping web portal, Shopping needs get the latest details about the local computer. Shopping may already have details from the Configuration Manager database via ActiveEfficiency, but these need to be confirmed and updated. Browser standards only allow websites to get limited information about the user and computer, therefore the Shopping website needs to make loopback calls to the local computer via the Shopping client. The following browsers permit loopback calls by default:

  • All versions of Chrome
  • All versions of Firefox
  • Non-Metro UI based Internet Explorer browsers (including legacy Internet Explorer)

If your Shopping users are using Edge and Metro Internet Explorer browsers you must enable a Loopback Exemption to allow these browsers to make loopback calls. Exemption affects the browser as a whole and is not just restricted to the Shopping website. Before enabling this option, check your corporate security policy and be aware of the implications of allowing access between browsers and the local machine. By enabling loopback, you are only setting the Edge/Metro Internet Explorer browsers to the same level of security as other browsers which allow this setting already.

If you are running an unattended install, you can use MODULE.SHOPPING.LOOPBACKEXEMPTIONENABLED for all OS but it only works on Windows 8, 8.1, 10 and Windows Server 2012 R2 and later.

Shopping client only allows inbound connections to localhost ( which prevents remote access.


Defines the URL that the Shopping client will use to connect to the Shopping Portal website.It should be set to the URL for the Shopping website. The Shopping website uses a host header, for which a DNS Name FQDN should have been defined. The Shopping Website URL should define the full path to the Shopping web application, comprising the scheme (HTTP or HTTPS), the host header (DNS Name FQDN), the port number (you do not have to provide this if using default port 80 or 443), and the path /Shopping. For example https://shopping.acme.local/Shopping.

This setting is mandatory when Module.Shopping.Enabled=true.

The Windows Servicing Assistant uses API calls to <ShoppingCentralUrl>/WindowsServicingAssistant

The Shopping client uses the API call <ShoppingCentralUrl>/WindowsServicingAssistant/GetTachyonAgentUrl to get the loopback URL which the Shopping uses to query the device.

By default, the loopback URL is the same as WCFSERVICEURL used in the legacy Shopping Agent: http://localhost:8000/ShoppingClientAgent/MachineInfo

When the API call http://localhost:8000/ShoppingClientAgent/MachineInfo/MachineId is used in a browser, only the MachineId is displayed for security reasons. However, the 1E Client log file shows other details obtained using the loopback feature which can be used in testing to demonstrate the Shopping client is enabled. It also demonstrates that loopback exemption is working on Edge and Metro Internet Explorer browsers. This works only when the client is able to connect to the Shopping API on the Shopping Central web server.

Information provided by the Shopping client

The following details are provided by the Shopping client, when a user browses to the Shopping Web Portal, and the website uses the loopback feature to query the local computer.

HostDomainNameComputer's NetBIOS Domain Name1E
AssignedSiteConfiguration Manager client Site codeCM1
MacAddressComputer's MAC Address20-68-9D-5B-EB-73
OSVersionOS Version10.0.15063
OSArchitectureOS Architecture64-bit

The role of the OS. Values are:

  • 1 – Workstation
  • 2 – Domain controller
  • 3 – Server
SccmVersionConfiguration Manager client version5.00.8458.1005
UniqueIdConfiguration Manager client GUIDGUID:04804aed-922c-4a4b-9f41-eab6592e7d83

Checking loopback exemption on Microsoft Edge and Metro Internet Explorer browsers

The following is valid only for Windows 8.1 and Windows 10.

Open a command-prompt as administrator on the computer you want to check, then run the following command to verify that loopback exemption was enabled during installation of the 1E Client.

CheckNetIsolation LoopbackExempt -s

Output should be:

If either of these items are missing, you can manually add them by executing the following commands. Quotes may be required around the name of the app.

For IE: 

CheckNetIsolation LoopbackExempt -a -n=windows_ie_ac_001

For Edge:

CheckNetIsolation LoopbackExempt -a -n=Microsoft.MicrosoftEdge_8wekyb3d8bbwe


The exemption from loopback restrictions can also be removed for all apps installed by using the following command:

CheckNetIsolation LoopbackExempt –c

More information

For more information from Microsoft about CheckNetIsolation please refer to: