Skip to main content

1E 8.1 (on-premises)

In-place upgrade of ActiveEfficiency Server for Shopping

This scenario is for upgrading a server that has ActiveEfficiency Server installed and used by 1E Shopping versions prior to Shopping 6.1. If ActiveEfficiency is also being used for Nomad then please also read In-place upgrade of ActiveEfficiency Server for Nomad.

If your installation of ActiveEfficiency is being used by 1E Shopping, then before you replace ActiveEfficiency with Content Distribution, you will need to do one of the following:

  • upgrade to Shopping 6.1 - this version does not use ActiveEfficiency

  • reconfigure your existing Shopping 6.0 server to synchronize directly with Configuration Manager - this method of synchronization is provided out-of-the-box in Shopping 6.1 onwards - to do this, please refer to the steps below

  • install another instance of ActiveEfficiency Server and Scout, and reconfigure your existing Shopping server to use that - this process is not described here

Shopping is not a Tachyon Platform application, and has no direct dependency on it, therefore it is not affected by Tachyon Setup, other than ActiveEfficiency being removed. Whilst Shopping has no direct dependency on Tachyon Platform, it can optionally integrate with Introducing Application Migration which is a Tachyon application. The Shopping/WSA client is a module of the 1E Client. If this is interesting to you please refer to Shopping - Integrating with Application Migration.

Reconfigure Shopping to synchronize directly with Configuration Manager

The process is for Shopping 6.0 only.

Execute the following SQL script on the Shopping database, then restart the Shopping Central service. A few minutes later, the Central service will perform its usual synchronization processes with AD, and also synchronize with CM. You can monitor this process in C:\ProgramData\1E\ShoppingCentral\ShoppingCentral.log

The script changes preference settings for Shopping 6.0 - Shopping Admin Console settings: Central Serviceas shown in the table opposite. It changes the description of the sync interval, it does not change its value, which is 1 day by default. If you change the value later it should be set to longer than the time it takes to complete all the syncs. You should not need to change the value of the sync interval because the SCCM sync should be approximately the same as your current ActiveEfficiency Scout sync.

Click here to download - ReplaceActiveEfficiencySyncWithConfigMgrSync.sql


Click Read more... to view source for ReplaceActiveEfficiencySyncWithConfigMgrSync.sql

Preference name

Change made by the SQL script

Users and Machines, AD Sync Interval

Change description

Users and Machines, AD Sync Units

Change description

Sync Machines and Users From Active Efficiency

Set to 'False' (enables sync from SCCM instead)

Sync Machines From Old Sccm

Hide as no longer required

ActiveEfficiency ServerName

Hide as no longer required