You only require the ActiveEfficiency Scout if you are using Shopping or AppClarity 5.2.
To install the Scout, you will need:
In most configurations, ActiveEfficiency and its Scout require read access to the Configuration Manager site database. For a single-site hierarchy this is a standalone Primary Site, and for a multi-site hierarchy this is the CAS. When using the Scout to collect data for AppClarity, this can be a reporting Site, but other uses require a live Site to get the most recent data.
Access rights are required for the following service accounts depending on which features are used.
To grant rights to the ActiveEfficiency and Scout service accounts, do the following on the Configuration Manager site database server.
ConfigMgr_DViewAccess(this localgroup should already exist on a Primary site database server, but will not exist for a CAS or any CB 1710 site database servers)
You can use your ActiveEfficiency installer account to configure the above rights before or after installation. Whatever installation account is used, it will need the following with respect to the
ConfigMgr_DViewAccesslocalgroup and add the service accounts
Nomad Dashboard uses the following sources to populate its tiles:
ConfigMgr_DViewAccesslocal group described in the paragraph above
Microsoft Message Queuing (MSMQ) Windows feature must be enabled in order to install the 1E ActiveEfficiency service component. This service is required by:
MSMQ is only required to support the above features, and is no longer required by other 1E companion products that use ActiveEfficiency Server (AppClarity 5.x and Shopping 5.x).
These considerations are only relevant if you are using the Scout to get data for AppClarity 5.2, which is no longer supported.
Nomad requires the FQDN of the ActiveEfficiency server to be configured in the PlatformURL setting of the Nomad agent on all machines. Therefore a DNS alias is recommended for the ActiveEfficiency server, but is not mandatory. This can be a CNAME or Host (A) record.
ActiveEfficiency Server requires Distributed Transaction Coordinator (MSDTC) to be enabled and configured on each of the SQL Servers used by:
MSDTC is a feature of Windows Server and is used to track of transactional processes, usually over multiple resource managers on multiple computers. MSDTC ensures that the transactions are completed and can be rolled-back if any part of the process fails. Nomad Sync uses MSDTC to perform complex queries on Configuration Manager and ActiveEfficiency data. For example, to retrieve computers targeted with Nomad Pre-cache policies and Nomad Dashboard data.
Nomad Sync uses a SQL linked server on the same SQL instance as the ActiveEfficiency database, to connect to the Configuration Manager database. The linked server is created by the ActiveEfficiency installer if the Nomad Sync option is enabled. The service account used by the ActiveEfficiency SQL instance must be trusted to present delegated credentials to the Configuration Manager SQL instance.
If the ActiveEfficiency service, the ActiveEfficiency database and the Configuration Manager database are on three separate servers and you plan to use the Nomad Dashboard or the Nomad pre-cache features or if you get the
Please review the documentation for each 1E product that uses ActiveEfficiency. If you are using ActiveEfficiency for multiple 1E products, ensure you add together each of the separate resource requirements.