Configuring Migration mode

This mode configures the Scout to manage data from both Configuration Manager 2007 and Configuration Manager 2012 and is intended for use when migrating between these two versions of Configuration Manager.

If you are in the process of migrating from Configuration Manager 2007 to Configuration Manager 2012, you want to be sure that the 1E solutions function as expected. For example, AppClarity should continue to provide reliable data about software usage. The solution should be able to cope with a user's machine having migrated from one version to the other. In order to ensure this, the ActiveEfficiency Scout provides a migration mode that performs an intelligent merge of the data in the two environments.

Due to the way that it merges the data from two separate Configuration Manager databases, Migration mode is not compatible with ConfigMgr mode. You must ensure that the Scout is not run in ConfigMgr mode for the duration of the migration process.

The following diagram illustrates the components responsible for retrieving information from Configuration Manager 2007 and Configuration Manager 2012:

ActiveEfficiency Migration mode

  • The Web API component is used as a central location where information coming from the Scout can be stored and retrieved for use in AppClarity.
  • The Scout communicates with the databases for the Configuration Manager system you are migrating from and the Configuration Manager system you are migrating to in order to retrieve information on software installations and software usage. The information is processed by the Scout and is then stored in the ActiveEfficiency database via the Web API component.
  • AppClarity is a consumer of the data retrieved when using the Scout in Migration mode.

Processing migrated device data

Installations on migrated devices

The installations associated with a migrated device will be those reported in the Configuration Manager 2012 environment, because that system should be considered to have the more up-to-date inventory. However, one exception is in the case where inventory has not yet been received by Configuration Manager 2012 for the device. In that case, there maybe no installations visible, so the Scout will instead defer to the installations reported in Configuration Manager 2007. Once inventory is being received by the 2012 environment, then that set of installations become preferred.

Usage data on migrated devices

Since usage data is not migrated from the old environment to the new environment, Configuration Manager 2012 has no knowledge of what software was used before the device was migrated. Configuration Manager 2007, of course, continues to hold the same usage that it always had for the device. So, the migration Scout will generate a unified set of usage data by combining the data from the two environments. For example, if Configuration Manager 2007 reports a usage of Word and Excel on a device and, for that same device, Configuration Manager 2012 reports a usage of PowerPoint, then the Scout will report usage of Word, Excel and PowerPoint to ActiveEfficiency Server.

Configuring Migration mode

The Scout can be configured to use Migration mode during installation. On the Component Selection screen of the Scout installer you select the ConfigMgr option and then select to use Configuration Manager Migration. The Scout installer will later prompt you for server and database details for both the Configuration Manager system you are migrating from and the Configuration Manager system you are migrating to. See Installing the Scout for more details.

Configuring AppClarity Integration

The AppClarity Synchronizer and ActiveEfficiency Scout components can now be configured from the ActiveEfficiency Synchronization Manager. By default, the ActiveEfficiency Synchronization Manager lets you schedule the Scout to run once per day, immediately followed by the AppClarity Synchronization. As a result the updated information retrieved by the Scout is passed on to AppClarity in the minimum configurable time.

When the Scout has been configured to run in Migration mode during installation it will be the default used during the daily scheduled mode for use with AppClarity.