IIS Redirect

It is a typical configuration to enable an IIS Redirect for Shopping because without an IIS Redirect in place end-users must remember the base WebURL (example: http://appstore.mydomain.com or simply CNAME of http://appstore) and then manually append /Shopping to the end of that, which is extremely undesirable  This configuration has proven difficult create and to maintain during installation/re-installation or upgrade as the windows installer MSI does not put this in place by default with this in mind. the following powershell script is provided as our recommended method to consistently put this IIS redirect in place. 

# 1E Ltd Copyright 2016
# 
# Disclaimer:
# Your use of this script is at your sole risk. This script is provided "as-is", without any warranty, whether express 
# or implied, of accuracy, completeness, fitness for a particular purpose, title or non-infringement, and is not
# supported or guaranteed by 1E. 1E shall not be liable for any damages you may sustain by using this script, whether
# direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages.

#>

$isElevated = ([Security.Principal.WindowsPrincipal] `
[Security.Principal.WindowsIdentity]::GetCurrent() `
).IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)
if (!$isElevated){write-host "you MUST run this script in elevated mode!" 
exit
}

# set the redirect for the Shopping website using the proper relative path (ie ../Shopping) this way it doesn't matter what the Host Header is
# this would be run post install for Shopping as this is not configured by default during an upgrade or new install
Import-Module WebAdministration
Set-WebConfiguration system.webServer/httpRedirect "IIS:\sites\Shopping" -Value @{enabled="true";destination="../shopping";childOnly="true"}
Set-WebConfiguration system.webServer/httpRedirect "IIS:\sites\Shopping\Shopping" -Value @{enabled="false";}
Set-WebConfiguration system.webServer/httpRedirect "IIS:\sites\Shopping\ShoppingAPI" -Value @{enabled="false";}

Policy refresh

Shopping can use its internal implementation or 1E WakeUp to initiate a policy refresh on the client, enabling applications to be pushed to the user's machine. You have to specify a delay in initiating the policy refresh on the client because Configuration Manager takes a while to digest a new Direct Membership rule created by the Shopping Receiver services. The delay depends on the supporting Configuration Manager architecture, i.e. centralized or distributed.

This delay is set during the Shopping receiver installation or from the PolicyRefreshDelay parameter in the Shopping.Receiver.exe.config file.

For Shopping to work in centralised mode, the Shopping Receiver service on all primary sites must be stopped except on the Configuration Manager 2007 Central Site or Configuration Manager 2012 CAS.

If you need to modify the delay at a later date, edit the Shopping.Receiver.exe.config file (located by default in Program Files\1E\Shopping\Shopping.Receiver on 32-bit systems and Program Files (x86)\1E\Shopping\Shopping.Receiveron 64-bit systems) and update:

<add key="PolicyRefreshDelay" value="DelayInSeconds" />

where DelayInSeconds is the delay to impose for initiating a policy refresh on the client. For example, if you want the delay to be 120 seconds, edit the PolicyRefreshDelay parameter in the Shopping.Receiver.exe.config file to read:

<add key="PolicyRefreshDelay" value="120" />

Relicensing Shopping

If your evaluation license has expired you can re-license Shopping once you have obtained a full or new evaluation license from us without re-installing the product. To do this, run the ShoppingCentral executable with the command-line:

ShoppingCentral.exe -relicense=CustID-1234-5678-8765-4321

where CustID-1234-5678-8765-4321 is your new license key.

Relicensing Windows Servicing Assistant

You can re-license Windows Servicing Assistant once you have obtained a full license from us without re-installing the product. To do this, run the ShoppingCentral executable with the command-line:

ShoppingCentral.exe -relicenseWsa=CustID-1234-5678-8765-4321

where CustID-1234-5678-8765-4321 is your new Windows Servicing Assistant license key.

Checking whether Windows Servicing Assistant is licensed or not

To check whether Windows Servicing Assistant is licensed or not, open a browser and in the address bar, type http://<shoppingBaseUrl>/shopping/WindowsServicingAssistant/IsLicensed

If the web browser displays True then the license is valid.

The Tachyon Agent

The Tachyon 3.2 Agent has now replaced the functionality previously provided by the Shopping Agent. It provides details on the local computer to determine the visibility of Shopping applications to the user and ensure that any software requested through Shopping is delivered correctly. The Windows Servicing Assistant is also provided by the Tachyon 3.2 Agent. For information on installing the Tachyon 3.2 Agent refer to Installing the Shopping client.