Shopping Central installer properties

Name of the AD server. This parameter can also be set to the fully qualified domain name for the server. Information on which Domain Controller you should nominate is here. See Active Directory Server.

The Shopping Admin account. This is either set as Domain\User or Domain\Group.

This account, or members of this group, can view the Shopping Admin pages. Once set it cannot be changed, therefore we recommend using a domain group so that access to the Shopping Admin pages can be determined using AD group membership.

During installation, this account/group is also used for the following which can be changed later in the Shopping Admin Console settings section. Each setting requires that the Admin account or group and its members are email enabled:

• Admin email setting, Shopping will forward alerts to the Administrator email account set in this parameter

• Deputy Default setting, which Shopping uses as a deputy approver in the event that an approval times out, and the approver does not have a deputy defined

For further guidance see Active Directory security groups.

This is an old installer property that is no longer supported.

Your Azure Active Directory tenant ID. Use in conjunction with ENABLEINTUNESUPPORT and its associated installer properties.

The Application ID for your Azure Active Directory Enterprise app for console authentication set up as per the Microsoft Intune integration documentation.

The timeout (in seconds) and denotes how long the installer waits for SQL commands to execute before reporting an error. Can be used to facilitate the upgrading of large Shopping databases. The default is 1 hour.

The timeout (in seconds) and denotes how long the installer waits for the SQL connection before reporting an error. Can be used to facilitate the upgrading of large Shopping databases.

Database usage mode. It may be set to one of the following values:

• SingleUser - Sets the upgrade scripts to run in single user mode

• MultiUser - Sets the upgrade scripts to run in multi-user mode

The default value sets the upgrade scripts to run in single-user mode to avoid multiple connections during upgrade (Only for SQL 2005).

Enabling MultiUser mode, by setting the following property on the installer command-line, may be necessary for larger databases to help to smooth the upgrade process:

DATABASE_MODE="MultiUser"

Enables the name for the database to be changed from the default. Changing this will create a new database on installation with the value you have chosen.

Any existing Shopping database with a different name will not be upgraded, will be left unchanged by the installation and the new database will be installed alongside it.

If set to 1 on the command-line this will drop the current Shopping database on install. If you do not want to drop any existing data, do not include this property on the command-line.

The default behavior for this property is to not drop the old database.

Enable Intune integration. 1 to enable it, 0 otherwise. Other required installer properties are:

• AZURETENANTID

• SERVICECLIENTAPPID

• CONSOLECLIENTAPPID

Enable the 1E Platform integration. 1 to enable it, 0 otherwise. Other required installer properties are:

• PLATFORMURL

• PLATFORMUSERNAME

• PLATFORMPASSWORD

IIS Host Header for the Shopping Website.

This value is used to create theHTTPS binding for theShopping Website, and Console settings for the Web URL and API URL.

See DNS Alias for design considerations of what this should be. Typically it will be the DNS Alias FQDN of the Shopping Central server.

Shopping 6.1 onwards only supports HTTPS connections to the Shopping Website, because supported browsers block Cross-Origin Resource Sharing (CORS) in non-secure contexts such as HTTP.

IISHOSTHEADER, SHOPPINGURLPREFIX, and THUMBPRINT are mandatory properties, used to configure the Website HTTPS binding.

Custom IP address for the Shopping Website, if you want to be non-specific about the IP address, set it to *.

This value is used to create theHTTP binding for theShopping Website.

IIS port for the Shopping Website.

This value is used to create theHTTP binding for theShopping Website, and Console settings for the Web URL and API URL.

Installation directory for all components.

Governs the components that are installed. Values are:

• COMPLETE – installs all components

• WEBONLY – installs only the Shopping website

• CONSOLEONLY – installs only the Shopping Admin console

Shopping license manager account – must be a domain user of group.

For further guidance see Active Directory security groups.

License key for Shopping. A valid license key must be purchased from 1E.

The URL for the 1E Platform server. For example, https://tachyon.acme.local:443/

Set this to the base URL for your 1E Platform implementation.

For example: https://tachyon.acme.local:443/

Username given in domain\username format for the 1E Platform account with the Shopping administrator role added.

Set this to the user name for the account you want to use for running the 1E Platform Instruction that implements the client-side Order Tracking feature and any 1E Platform Instructions you are making available as Shopping applications. The user name must be provided in the form Domain\User. You could even set this to the account details you used for the Shopping Service account to save having to provision another account. The installer will:

• Create the Shopping Administrators role in the 1E Platform

• Create an instruction set called 1E Shopping and add the client-side Order Tracking instruction to it

• Give the Shopping Administrators role permission to run the instruction

• Add the specified user account to the 1E Platform

• Assign the user account to the Shopping Administrators role

• Save the name as 1E username in the Shopping Console settings (also saves its password encrypted).

Password for the 1E Platform account with the Shopping administrator role added. Set this to the password of the 1E Platform user account you want to use for running Shopping instructions.

Name for the account or security group used for the Shopping Receiver accounts.

Must be a group and contain the Configuration Manager Network Access account if calling Shopping OSD APIs in OSD task sequences.

Must be a group if Shopping Receivers are configured to use Network Service or have different service accounts.

For further guidance, see Active Directory security groups.

Shopping reports access account – must be a domain user or group. For further guidance, see Active Directory security groups .

The Application ID for your Azure Active Directory Enterprise app for service authentication set up as per the Microsoft Intune integration documentation.

The Shopping AD security group for Full Database Access. Provides access to the following nodes in the Shopping Console.

• Sites

• Applications

• Settings

• Node Security

During installation, this group is granted various rights to the Shopping SQL database.

For further guidance see Active Directory security groups.

For further information about Shopping Console node security, see Node Security.

The Shopping AD security group for ConfigMgr access in the Shopping Admin Console. Provides access to the following nodes in the Shopping Console

• Sites

• Applications

During installation, this group is granted various rights to the Configuration Manager SQL database.

For further guidance see Active Directory security groups.

For further information about Shopping Console node security, see Node Security.

The Shopping AD security group for partial Shopping Admin Console access. Provides access to the following nodes in the Shopping Console

• Approvers

• User Categories

• Computer Categories

• Event Log

During installation, this group is granted various limited rights to the Shopping SQL database.

For further guidance see Active Directory security groups.

For further information about Shopping Console node security, see Node Security.

Prefix for the URL of the Shopping Website and defined in one of the following formats depending on your IIS configuration:

https://<ServerName>
https://<ServerName>:<PortNumber>

Shopping 6.1 onwards only supports HTTPS connections to the Shopping Website, because supported browsers block Cross-Origin Resource Sharing (CORS) in non-secure contexts such as HTTP.

IISHOSTHEADER, SHOPPINGURLPREFIX, and THUMBPRINT are mandatory properties, used to configure the Website HTTPS binding.

The Configuration Manager database port if it is using the non-default port.

Name of the Configuration Manager server or its FQDN.

Name of the SMTP server or its FQDN.

Name for the Shopping SQL Server instance. This can be set in one of the following formats depending on your database setup:

<ServerName>
<ServerName>\<InstanceName>
<ServerName>,<PortNumber>

It may also use a local SQL Alias.

Password for the Shopping Service account.

Username (in for format domain\username) for the Shopping Central service account.

The thumbprint of the Web Server certificate used for the Shopping Website. Please refer to Shopping Server certificate.

Shopping 6.1 onwards only supports HTTPS connections to the Shopping Website, because supported browsers block Cross-Origin Resource Sharing (CORS) in non-secure contexts such as HTTP.

IISHOSTHEADER, SHOPPINGURLPREFIX, and THUMBPRINT are mandatory properties, used to configure the Website HTTPS binding.

Configures use of the Global Catalog for searches in AD. Values are:

• 0 – Disable Global Catalog

• 1 – Enable Global Catalog