Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


CategoryProductNotes

Server OS


SQL Query
outputwiki
noDataMessageN/A
heading0
enableHeadingAttributesfalse
autoCommitfalse
enableSortingfalse
dataSourceReleaseMatrix
enableHighlightingfalse
tablefalse
SELECT '* ' + os + CHAR(10)
FROM [release] AS r
INNER JOIN [product] AS p ON r.product_id = p.product_id
INNER JOIN [version] AS v on r.version_id = v.version_id
INNER JOIN [status] AS s on r.status_id = s.status_id
INNER JOIN [releaseOs] AS ros on r.release_id = ros.release_id
INNER JOIN [os] AS os on os.os_id = ros.os_id
WHERE product = 'Shopping'
AND version = '6.0'
AND os_type = 'Server'
AND os_vendor_supported = 'Y'
ORDER BY os.release_date DESC


Systems running these server OS will support:

  • The Shopping services
  • Shopping Central Server and website
  • Shopping Admin console
  • Shopping Receiver
  • Shopping client module in 1E Client 4.1 or later
Info

The list in the Product column is automatically updated to show only those OS versions in mainstream support by Microsoft, and therefore supported by 1E, and by

Spacetitle
. However the following OS continue to be supported as exceptions to help customers during their migration to the latest OS:

  • Windows Server 2012 R2

Shopping's Intune integration feature is not supported on legacy OS. 

Please refer to Constraints of Legacy OS regarding end of mainstream support.

For Microsoft product lifecycle details, please refer to https://support.microsoft.com/en-us/lifecycle/search.

Please refer to https://1eportal.force.com/s/support-for-msft-rapid-release-cycle for details of which Current Branch versions are supported by 1E products, and known issues regarding specific versions.


Client OS


SQL Query
outputwiki
noDataMessageN/A
heading0
enableHeadingAttributesfalse
autoCommitfalse
enableSortingfalse
dataSourceReleaseMatrix
enableHighlightingfalse
tablefalse
SELECT '* ' + os + CHAR(10)
FROM [release] AS r
INNER JOIN [product] AS p ON r.product_id = p.product_id
INNER JOIN [version] AS v on r.version_id = v.version_id
INNER JOIN [status] AS s on r.status_id = s.status_id
INNER JOIN [releaseOs] AS ros on r.release_id = ros.release_id
INNER JOIN [os] AS os on os.os_id = ros.os_id
WHERE product = 'Shopping'
AND version = '6.0'
AND os_type = 'Client'
AND os_vendor_supported = 'Y'
ORDER BY os.release_date DESC


Systems running these client OS will support:

  • The Shopping Admin console
  • Shopping client module in 1E Client 4.1 or later
Info

The list in the Product column is automatically updated to show only those OS versions in mainstream support by Microsoft, and therefore supported by 1E, and by

Spacetitle
. However the following legacy OS continue to be supported as exceptions to help customers during their migration to the latest OS:

  • Windows 7 SP1

Shopping's Intune integration feature is not supported on any legacy OS. Please be aware that Microsoft Intune has very limited support for application deployment on Windows 8.1, especially for enterprise application types.

Please refer to Constraints of Legacy OS regarding end of mainstream support.

For Microsoft product lifecycle details, please refer to https://support.microsoft.com/en-us/lifecycle/search.

Please refer to https://1eportal.force.com/s/support-for-msft-rapid-release-cycle for details of which Current Branch versions are supported by 1E products, and known issues regarding specific versions.


SQL Server


SQL Query
outputwiki
noDataMessageN/A
heading0
enableHeadingAttributesfalse
autoCommitfalse
enableSortingfalse
dataSourceReleaseMatrix
enableHighlightingfalse
tablefalse
SELECT '* ' + rdbms + CHAR(10)
FROM [release] AS r
INNER JOIN [product] AS p ON r.product_id = p.product_id
INNER JOIN [version] AS v on r.version_id = v.version_id
INNER JOIN [status] AS s on r.status_id = s.status_id
INNER JOIN [releaseRdbms] AS rdb on r.release_id = rdb.release_id
INNER JOIN [rdbms] AS db on db.rdbms_id = rdb.rdbms_id
WHERE product = 'Shopping'
AND version = '6.0'
AND db.vendor_supported = 'Y'
ORDER BY db.rdbms DESC


  • You must have one of these SQL Server versions installed.
  • SQL Server must be configured to use a case-insensitive, accent-sensitive collation as the server default (the preferred collation is SQL_Latin1_General_CP1_CI_AS).
  • If TLS 1.0 is disabled on either the Web server or the SQL Server you will need to install the SQL Server Native Client on the Web server before installing Shopping. Please refer to Preparation: Installing when TLS 1.0 is disabled for more details.

Microsoft System Center Configuration Manager


SQL Query
outputwiki
noDataMessageN/A
heading0
enableHeadingAttributesfalse
autoCommitfalse
enableSortingfalse
dataSourceReleaseMatrix
enableHighlightingfalse
tablefalse
SELECT '* ' + sccm + CHAR(10)
FROM [release] AS r
INNER JOIN [product] AS p ON r.product_id = p.product_id
INNER JOIN [version] AS v on r.version_id = v.version_id
INNER JOIN [status] AS s on r.status_id = s.status_id
INNER JOIN [releaseSccm] AS rsccm on r.release_id = rsccm.release_id
INNER JOIN [sccm] AS sccm on sccm.sccm_id = rsccm.sccm_id
WHERE product = 'Shopping'
AND version = '6.0'
AND sccm.vendor_supported = 'Y'
ORDER BY sccm.release_date DESC


  • See Preparation: Configuration Manager rights for details.
  • If you are using the OS deployment feature, you must install a Shopping receiver on the Configuration Manager central site or CAS that Shopping points to.

Microsoft Intune

  • Intune Service Release 2006


  • Integration with Intune is an optional feature of Shopping. See Enabling Intune integration: Requirements.
  • Shopping has been tested with this release of Intune, there are no known issues with previous or newer Intune releases.
  • Azure Active Directory (AAD) is required, and must be in hybrid mode with seamless single sign-on (SSO) enabled, and either pass-through authentication or federation enabled.
  • See Preparation: Configuration Manager rights for details.

Web Server


SQL Query
outputwiki
noDataMessageN/A
heading0
enableHeadingAttributesfalse
autoCommitfalse
enableSortingfalse
dataSourceReleaseMatrix
enableHighlightingfalse
tablefalse
SELECT '* ' + iis + CHAR(10)
FROM [release] AS r
INNER JOIN [product] AS p ON r.product_id = p.product_id
INNER JOIN [version] AS v on r.version_id = v.version_id
INNER JOIN [status] AS s on r.status_id = s.status_id
INNER JOIN [releaseIis] AS ri on r.release_id = ri.release_id
INNER JOIN [iis] AS i on i.iis_id = ri.iis_id
WHERE product = 'Shopping'
AND version = '6.0'
AND i.vendor_supported = 'Y'
ORDER BY i.release_date DESC


Runtime libraries


SQL Query
outputwiki
noDataMessageN/A
heading0
enableHeadingAttributesfalse
autoCommitfalse
enableSortingfalse
dataSourceReleaseMatrix
enableHighlightingfalse
tablefalse
SELECT '* ' + framework + CHAR(10)
FROM [release] AS r
INNER JOIN [product] AS p ON r.product_id = p.product_id
INNER JOIN [version] AS v on r.version_id = v.version_id
INNER JOIN [status] AS s on r.status_id = s.status_id
INNER JOIN [releaseFramework] AS rf on r.release_id = rf.release_id
INNER JOIN [framework] AS f on f.framework_id = rf.framework_id
WHERE product = 'Shopping'
AND version = '6.0'
AND f.vendor_supported = 'Y'
ORDER BY framework DESC


  • Shopping server components use .NET Framework 4.5 or later
  • The legacy Shopping Agent uses one of these versions of .NET Framework
  • The Shopping module in Tachyon Agent 3.2 and later, and 1E Client 4.1 and later contains the following:
    • Replacement of the legacy Shopping Agent (which provides the loopback feature) has been re-written so it does not require .NET Framework
    • WSA - the WSA executable requires one of these versions of .NET Framework

Browsers


SQL Query
outputwiki
noDataMessageN/A
heading0
enableHeadingAttributesfalse
autoCommitfalse
enableSortingfalse
dataSourceReleaseMatrix
enableHighlightingfalse
tablefalse
SELECT '* ' + browser + CHAR(10)
FROM [release] AS r
INNER JOIN [product] AS p ON r.product_id = p.product_id
INNER JOIN [version] AS v on r.version_id = v.version_id
INNER JOIN [status] AS s on r.status_id = s.status_id
INNER JOIN [releaseBrowser] AS rb on r.release_id = rb.release_id
INNER JOIN [browser] AS b on b.browser_id = rb.browser_id
WHERE product = 'Shopping'
AND version = '6.0'
AND b.vendor_supported = 'Y'
ORDER BY browser ASC


  • Computers running these browsers support access to the Shopping self-service portal
  • Where localization for Portuguese is enabled, the language-code is pt-BR (Portuguese-Brazil)
  • Firefox is not supported when the Shopping self-service portal is accessed via HTTPS

Companion products

  1. ActiveEfficiency
  2. Tachyon Agent or 1E Client
  3. Application Migration (optional)
  4. Nomad (optional)
  5. WakeUp (optional)
  1. You must have ActiveEfficiency 1.10 or later. The Shopping Central service account relies on ActiveEfficiency Scout to retrieve user and machine information from the Configuration Manager site server database. See ActiveEfficiency Server 1.10 - Data capture accounts and the ActiveEfficiency Server 1.10 - ActiveEfficiency Synchronization Manager for details on how to install and configure the Scout component.
  2. Shopping client is available in 1E Client 4.1 or 5.0 as described in Preparation: 1E Client. 1E Client 4.1 or later must be used if TLS 1.0 is disabled in your environment, or if you wish to use the WSA enhancements introduced in Shopping 5.5.200. 1E Client 5.0 with the latest hotfix applied must be used if you are using the Microsoft Intune integration.
  3. If Shopping uses Application Migration then you will require one of the following:
  4. Nomad 6.3.201 or later is required by WSA to manage content and storage of user state using custom task sequence steps that are implemented with it
  5. You must have WakeUp Server 7.2 or later installed if you want to the Shopping Receivers policy refresh feature to use 1E WakeUp.
Note

If you are implementing self-service OS deployment through Shopping using either the Windows Servicing Assistant or the OS Deployment Wizard, you will need to install Tachyon and Application Migration to support migration of applications during the OS deployment.

Application Migration supersedes the App Mapping feature in earlier versions of Shopping that required AppClarity 5.2 to provide application usage information to Shopping. Shopping integration with AppClarity 5.2 is no longer available and supported so you will need to move to using Application Migration.


Others

  1. SMTP/Exchange server
  2. Active Directory
  1. Access to an SMTP or Exchange server.
  2. Access to Active Directory. Where AD groups are specified for accounts with an associated group email address, you must have Exchange server for email notifications to be sent to all members of the group.


Constraints of Legacy OS

Multiexcerpt include
SpaceWithExcerptcom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@117cc
MultiExcerptNameLimitedSupportStatement
PageWithExcerptHLP:Legacy OS

Digital Signing Certificates

Multiexcerpt include
SpaceWithExcerptcom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@117cc
MultiExcerptNameExpiredRootCertificates
PageWithExcerptHLP:Legacy OS

Multiexcerpt include
SpaceWithExcerptcom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@117cc
MultiExcerptNameSigningCertificatesMissing
PageWithExcerptHLP:Legacy OS

Multiexcerpt include
SpaceWithExcerptcom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@117cc
MultiExcerptNameSigningCerts2020
PageWithExcerptHLP:Legacy OS