The Nomad Dashboard is a collection of interactive tiles made available in the Configuration Manager console that provides you with a global view across your network of Nomad status and latest operation details. 

Tiles no longer updated with Nomad 7.0

Nomad 7.0, implemented through the 1E Client, no longer includes 1E Client Health. The Client Health Status tile and associated drill-down data will not be updated by clients after upgrading from previous versions of Nomad. Also, the Client Version Distribution tile and associated drill-down data will not show Nomad 7.0 clients (Nomad 7.0 clients will show as 'Missing' in this dashboard tile.

The functionality of 1E Client Health is now provided through the Guaranteed State feature of the 1E Tachyon platform, please refer to Tachyon 5.1 - Nomad Client Health Policy for more details.


To use this feature with  Nomad 7.0.200 you must have ActiveEfficiency Server 1.10 or later installed with Nomad Sync enabled. The Nomad Sync feature must be enabled during installation or upgrade of ActiveEfficiency, it cannot be enabled post-installation because it has several additional prerequisites and configuration steps including a SQL Server linker server used to connect to the Configuration Manager database. If required later you can uninstall and reinstall ActiveEfficiency Server keeping the same ActiveEfficiency database. 

Please refer to ActiveEfficiency 1.10 - Installing and upgrading ActiveEfficiency. Nomad 7.0 requires ActiveEfficiency 1.10 (or later) with the latest accumulated hotfix.

Nomad clients must be configured to return the following status messages into the Configuration Manager site database in order to populate the Nomad dashboard's Latest Operations tiles. Because the Nomad client does not return any status messages by default, you must configure the Nomad client registry StatusMsgEvents value, either during installation of 1E Client or using The Nomad Baseline Wizard.

  • SNO_EVT_ERROR (0x0000000004)
  • SNO_EVT_REQUEST_STARTED (0x0000000020)
  • SNO_EVT_REQUEST_COMPLETED (0x0000000040)
  • SNO_EVT_FINALSTATS (0x1000000000)

These combine to the following value: 0x1000000064

Status message events should be used with caution as they could impact your Configuration Manager environment when scaled up to tens of thousands of machines. They are provided mainly for advanced troubleshooting purposes, although some events are also used to support the Nomad dashboard tiles.

Allow the Nomad synchronization service to run after the status messages reaches the Configuration Manager database from the clients in order for the dashboard to update. Where a client has both warnings and failure for a particular health check, only failures are reported in the tile.

Please refer to Resolving Nomad Dashboard issues if you encounter issues after installation or using the dashboard.

On this page:


The Nomad Dashboard stores data for the past 30 days only (by default).  Data older than this is automatically deleted from the ActiveEfficiency database when the Nomad Sync is executed.  This can be increased by modifying by the MaxNomadDashboardDataDays value in %ProgramFiles(x86)%\1E\ActiveEfficiency\Service\ServiceHost.exe.config, however this will increase the ActiveEfficiency database size.

The Nomad Dashboard is split into two main sections:

The Nomad Dashboard is an HTML page in the Configuration Manager console that aggregates data from ActiveEfficiency which gets its content from the Configuration Manager database using the Nomad Synchronization service which runs every 30 minutes by default. You can access the dashboard from the Configuration Manager console or from a browser.

We recommend running this on a host capable of displaying a 1920x1080 resolution. However, if the host you are running on has a lower resolution, use the CTRL and +/- keys to adjust the display to suite your personal preferences and avoid having to scroll to view the tiles.

The dashboard is made up of eight tiles:

The Nomad dashboard

A summary at the top of the dashboard displays the headline savings for successful Nomad downloads and the WAN bandwidth savings.

To the top right of each tile there are icons to refresh the tile, to see a summary about the data or to get detailed information about the data. Hover your mouse over these icons to get a tool-tip. For example, if you click the Info icon, it displays a summary of the event for that tile and where appropriate, the date it was updated or the date range for the report.

Information about a tile

The Nomad Status tiles

These tiles provide information about how Nomad is performing, including the distribution of Nomad client versions across the network.

There are four Status tiles oulined below. You can click on a heading below to take you to the a more detailed description of the tile on the Nomad Dashboard Status tiles page

Client version distribution

This tile displays the distribution of Nomad client versions across your environment. The red bar indicates the number of computers that do not have the Nomad client installed (y-axis) and the turquoise bars identify the version (x-axis) and the number of clients for that version.

Tile not updated with Nomad 7.0

The Client version distribution tile is not currently updated with Nomad 7.0 clients. Nomad 7.0 clients will be represented in the 'Missing' column in this dashboard tile.

This tile currently has a dependency on hardware inventory, which is handled by the reports installer. We are working on removing this dependency in a future release.

Client health status

This tile displays the health status of your Nomad clients. There are three top-level status shown: Healthy, Warning and Failed. You can click on the Warning and Failed segments displayed to see a detailed breakdown of the warnings and failures that make up the overall status.

Where a client has both warnings and failure for a particular health check, only failures are reported in the tile.

The tile additionally shows the health of CM client which is not gathered by Nomad agent, but directly queried from SCCM database.

Tile not updated with Nomad 7.0

The 1E Client Health service has been removed from Nomad 7.0 and will be replaced in the near future using the real-time Guaranteed State feature of the 1E Tachyon platform. Clients upgraded to Nomad 7.0 will no longer report client health data and this dashboard tile will not be updated by clients running Nomad 7.0.

This tile depends on Nomad status message reporting being enabled on each of the Nomad clients.

Content by type

This tile displays the distribution of the various types of Nomad content downloaded across your network split into those that are, and those that are not, enabled to use Nomad.

Overall WAN bandwidth usage

This tile shows a comparison between the available WAN bandwidth and that used by Nomad over a period of time. Hover your mouse over a date for a summary of the network usage over that period.

The Latest Operations tiles 

These tiles provide information on the progress of the latest Nomad Operations.

There are four Latest Operations tiles, as outlined in the following table. 

You can click on a heading below to take you to the a more detailed description of the tile on the Nomad Dashboard Latest Operations tiles page.

If you enable the SECure feature, the Nomad Dashboard will not differentiate between secure and non-secure downloads in its reports for the Download Progress and Caching Metrics tiles.

Download Progress:<Latest deployment>

This tile shows the download progress for the latest deployment.

Caching Metrics:<Latest deployment>

This tile shows the caching metrics (distribution point, peer and already cached and a combination of these) for the latest deployment.

Download progress: <Latest pre-cache job>

This tile shows the download progress for the latest pre-cached job.

This tile shows the proportion of clients downloading content for the last pre-cached job from the different pre-cached locations.

Caching metrics: <Latest pre-cache job>

This tile displays the caching metrics for a particular package.

Nomad clients must have ContentRegistration registry value set to 1 to enable pre-caching.

Accessing the Nomad Dashboard

To access the dashboard:

  1. From the Configuration Manager console, open the Monitoring workspace.
  2. Expand the 1E Nomad folder and click Dashboard.
  3. From a browser, type http://<ActiveEfficiency Server Name>/ActiveEfficiency/NomadDashboard in the address bar (where <ActiveEfficiency Server Name> is the name of the server where you installed ActiveEfficiency). For example in the ACME.LOCAL domain there could be an AESERVER01 server where ActiveEfficiency has been installed. In this case the URL would be:  http://AESERVER01.ACME.LOCAL/ActiveEfficiency/NomadDashboard .

Restricting access to the Nomad dashboard

The Nomad Dashboard is implemented through ActiveEfficiency. When using the Nomad Dashboard with ActiveEfficiency 1.9, Configuration Manager Role-based Access Control is applied. Users will not be able to see data for deployments or content that they do not have read permissions on in CM security. From ActiveEfficiency 1.10 this has been replaced with a simpler AD group security model. This change was made due to performance issues with the dashboard when role-based access control was used, and feedback from customers that role-based access control was not as important as being able to view the data in a timely fashion.

By default, when ActiveEfficiency 1.10, or later, is installed, the Domain Users group (in the ActiveEfficiency server's domain) is granted access to the Nomad Dashboard. To restrict the dashboard to a different AD user group:

  1. Navigate to C:\Program Files (x86)\1E\ActiveEfficiency\Web\WebService\
  2. Edit the web.config file.
  3. Locate the <appSettings> element, and update the value attribute for DashboardAccessGroup:

    	<add key="DashboardAccessGroup" value="Domain Users" />
  4. To specify a domain other than the ActiveEfficiency server's domain, you will need to add the following key to the web.config file (it is not in the default file - you can add it after the DashboardAccessGroup key) 

    	<add key="NomadDashboardDomain" value="MyDomain" />
  5. Save the file.