The following diagram shows a schematic of the ActiveEfficiency components involved in retrieving information from Configuration Manager related to AppV.

AppClarity AppV Feature Map

  • The Web API component is used as a central location where information coming from the Scout and scripts can be stored and retrieved for use in AppClarity. The Scout communicates with the Configuration Manager database to retrieve information on virtual applications and devices.
  • The VirtualAppExporter component retrieves AppV information from the Virtual Packages source directory, an XML file with this information is then returned to a local directory for the Scout to pick up. The information is processed by the Scout along with the information retrieved from Configuration Manager and is then stored in the ActiveEfficiency database via the Web API component.
  • AppClarity is a consumer of the AppV information retrieved by the Configuration Manager scout.

AppV Data Capture Requirements

The following AppV requirements apply:

  • The Scout must be installed with Configuration Manager mode enabled
  • The AppV packages must have been sequenced in AppV 4.5, 4.6 or 5.0
  • The Configuration Manager client must be installed on all the systems where the AppV packages are deployed
  • The Configuration Manager Scout is used to query the Central Site or CAS if using multiple CM2012 Primary Sites
  • The Scout needs a Data Capture Account with Configuration Manager access

Configuring AppClarity Integration

You will need to schedule the running of the VirtualAppExporter with the Scout and AppClarity Sync components. The following table shows the recommended schedules for the components:

ComponentSchedule
VirtualAppExporterThe VirtualAppExporter component should be configured to run on a schedule using Windows Task Scheduler once a week
Scout and AppClarity SyncThe 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.

VirtualAppExporter

By default the Scout.msi installer installs the VirtualAppExporter to the following directory:

C:\Program Files (x86)\1E\ActiveEfficiency\Scout\Exporter

Running the VirtualAppExporter

The VirtualAppExporter should be run with the following command-line:

C:\Program Files (x86)\1E\ActiveEfficiency\Scout\Exporter\N1E.ActiveEfficiency.VirtualAppExporter.exe scanonly packagefolder=<VirtualPackageLocation>

where <VirtualPackageLocation> should be replaced with the root location where AppV packages are stored. This folder is searched recursively for AppV packages. In the basic scenario where all the ActiveEfficiency components are installed on the same server this will be a UNC path that points to a server, NAS or other network storage device containing the AppV packages.

The account running the VirtualAppExporter will need read access permissions to the AppV packages location.

Running this command will generate an XML file containing information on the AppV packages and place the file in the following location:

C:\ProgramData\1E\ActiveEfficiency\PackageXml\Packages.xml

Scanning multiple root folders

If there is more than one root folder containing AppV packages, i.e. the packages are spread over different NAS, then the Package Exporter should be run once for each root folder required.  When run like this you must ensure that each package metadata file created by the Package Exporter has a unique name so as not to overwrite the output from a different root folder scan.  To do this you need to set the optional PackageXml parameter on the Package Exporter command-line:

N1E.ActiveEfficiency.VirtualAppExporter ScanOnly PackageFolder=<RootFolderToScan> PackageXml=<UniqueFileName>

where <RootFolderToScan> should be set to the AppV packages root folder you want to scan and <UniqueFileName> should be set to a name unique from all other Package Exporter scans. After creating the package metadata file you will then need to copy it to the package XML folder on the server where the Scout will be run, the default folder path was shown earlier under the Running the VirtualAppExporter heading.