Summary

Many Nomad features are available with minimal configuration of the Nomad client. However, some features require additional configuration of the Nomad client on Configuration Manager Distribution Points.

Nomad features maximize download efficiency in branch network deployment scenarios, and reduces the number of Configuration Manager Distribution Points. Nomad integrates closely with Configuration Manager, assists with WAN link usage efficiency during downloads, copes with different network protocols.

Nomad features and concepts

With Nomad, you get all the benefits you would expect from Nomad with the additional benefits of the Tachyon Platform, included in the license fee:

  • Increased patch compliance by ensuring clients are functioning, and you are able to deploy updates to them at all times.
  • Total control over downloads in your environment with the ability to stop them in their tracks if needed.
  • Centrally managed content in the Nomad cache on clients, with the ability to remove content from any client in real time.

New features in Nomad 7.1

Platform

  • Works with Tachyon Platform 5.2
  • Modernized backend infrastructure - Nomad requires a back-end server, which was previously the legacy ActiveEfficiency platform, this has been replaced by the Tachyon Platform to provide Single-Site download, Pre-caching and a new Dashboard. For customers moving to Modern Management, Nomad provides visibility and control of Delivery Optimization, which is used by Intune, MS store and MS update.
  • Leverage the Tachyon Platform and 1E Client - with the Tachyon Platform you can enable further features including Experience, User Sentiment, Guaranteed State and Patch Success, as well as opening up real-time management to any task by acquiring the appropriate license.
  • Content Distribution - Content Distribution is a new component of the Tachyon Platform that provides control and visibility on content deployments and delivery in an organization
    • Replaces ActiveEfficiency features, maintaining support during upgrade for legacy Nomad clients (versions earlier than Nomad 7.1 in 1E Client 5.2)
    • Nomad 7.1 clients now connect to Tachyon Response Stack components (Switch and Background Channel) which act as a proxy for Content Distribution, and legacy clients continue to connect directly to Content Distribution.
  • Nomad app - the user interface for Content Distribution, provides real-time visibility of what content is downloading or available in each location, subnet and client, see how much WAN traffic is being saved overall and each day
    • Delivery Optimization (DO) Visibility - visibility of Delivery Optimization downloads and content availability in each location, subnet and device
    • Delivery Optimization (DO) and Windows Update Agent (WUA) monitoring - track Windows download or Microsoft Endpoint Configuration Manager deployments on clients being downloaded via Delivery Optimization in real time, their peer to peer downloads efficiency, sources of the downloaded content and see this reported in the Nomad app dashboards
    • Overview page - gives a high-level view of the current status of content throughout the entire network
    • Content page - provides a Content-centric view of content distributed throughout your network
    • Task Sequences page - provides that visibility by grouping the reference content for each Task Sequence into a single view, so you can see which content is cached and which is not
    • Devices page - lists all Devices that have sent Nomad device registration events and have sent download events within a selected time period, links through to Device View 
    • Nomad Sites page - shows how the network is being used for content distribution in different locations
    • Client Health page - shows information from two Integrated Product Packs provided with the Tachyon Platform.

Client

  • NomadBranch 7.1 client is the Nomad module in 1E Client 5.2
  • ActiveEfficiency features are now provided by Content Distribution on Tachyon Platform 5.2
  • Client status messages are sent via Tachyon event policy system - Content Distribution uses these instead of StatusMsgEvents using Configuration Manager
  • New client settings:
    • DeliveryOptimizationReportingEnabled - monitoring of Delivery Optimization downloads and reporting them to Content Distribution - disabled by default
    • SupportWPAD - provides support for Web Proxy Auto-Discovery Protocol (WPAD) - disabled by default.

Tools

  • ActiveEfficiency features are now provided by Content Distribution on Tachyon Platform 5.2.

Modern management

Nomad provides a way of managing legacy and modern applications in a unified way by providing enhanced oversight, security and awareness to IT departments, with a particular focus on Delivery Optimization (DO). The following table describes the Nomad capabilities:

Nomad capabilityNomad featureNomad 7.0.200 feature requiring ActiveEfficiencyNomad 7.1 feature requiring Content Distribution on the Tachyon Platform
Content Distribution










Bandwidth management and peer sharing

Protect the WAN when downloading from DP and share content with local peers.

Refer to Nomad fundamentals: Full control over WAN link usage.

(tick)(tick)

Single Site Download

Share content across subnets in the same location.

Refer to Single Site Download.

(tick)(tick)

Pre-caching

Get content distributed ahead of important deployments.

Refer to Nomad Pre-caching.

(tick)(tick)

Cache management

Periodically delete unused content from the cache.

Refer to Cache management.

(tick)(tick)

Cloud-attached CM support

Download content from Cloud DP / Content enabled CMG.

Refer to Cloud Support.

(tick)(tick)
OS Deployment

Peer Backup Assistant

Use available storage on peers instead of servers to temporarily store user state during OS deployment.

Refer to Peer Backup Assistant - PBA.

(tick)(tick)

PXE Everywhere

Dynamic peer-based PXE eliminates PXE servers.

Refer to Using Nomad with PXE Everywhere.



Nomad OSD Tools

Nomad support for Configuration Manager OS Deployment.

Refer to Nomad OS Deployment task sequence actions.



Nomad Management


Nomad app

Real-time visibility of what content is downloading or available in each location, subnet and client. See how much WAN traffic is being saved overall and each day.

Refer to the Nomad app.

(tick)(tick)

Delivery Optimization (DO) Visibility

Real-time visibility of Delivery Optimization downloads and content availability in each location, subnet and device.



Nomad Download Pause

Immediately stop Nomad downloads across your network or on specific CM Collections.

Refer to Nomad Download Pause.



Client Health



Nomad Client Health

Real-time monitoring to ensure Nomad is running, can communicate through the firewall, is correctly registered with the CM client, its cache share is accessible.

Refer to Nomad Client Health.

(tick)(tick)

MEMCM Client Health

Real-time monitoring to ensure the CM client is installed, running and assigned to the correct site, it is communicating with the MP, supporting services are running and WMI is healthy, with real-time remediation for many client issues.

Refer to MEMCM Client Health.

(tick)(tick)

Windows Client Health

Check for application crashes, free disk space and WMI repository health. 

Refer to Windows Client Health.

(tick)(tick)

Monitoring Nomad Client Health

The Client Health page of the Nomad app shows information from two Integrated Product Packs provided with the Tachyon Platform:

Refer to Monitoring Nomad Client Health.

(tick)(tick)

Nomad features

These features are described in greater detail in the following pages:

Content Distribution
1E Content Distribution is a Tachyon Consumer providing control and visibility on content deployments and delivery in an organization.
  • Download once to branch

    Nomad ensures that software packages are only ever copied once per branch over the WAN, utilizing local computers as temporary file caches to distribute the software locally. This reduces the bandwidth required for delivering software updates and means that small offices or sites connected by poor network links can receive software updates more reliably.

    The Nomad clients with local copies of the package can themselves act as the master if the need arises. This significantly reduces the number of Configuration Manager servers required to manage a Configuration Manager hierarchy, thereby reducing initial and ongoing maintenance costs.

  • Single Site Download

    Nomad's Single Site Download (SSD) feature ensures a download across the WAN only happens once per site. It does this by maintaining information about which subnets are neighbors of each other (accessible on LAN rather than WAN), so that when an elected master considers a download from a DP rather than a peer in its subnet, it can discover which other local subnets already has the package. These subnets are typically at a single customer site, specifically a single geographical location.

    Nomad SSD uses Content Distribution. When a Nomad client downloads a package, it registers this information with Content Distribution enabling a profile to be created on which Nomad clients hold particular packages.

  • Nomad Pre-caching

    Pre-caching lets you pre-load the Nomad caches of particular machines directly from the Configuration Manager console. This enables downloads to be available on the branch prior to a deployment taking place, which can be very useful in large-scale deployment scenarios.

  • Nomad cache

    An overview of the Nomad cache including different methods used by Nomad peers to access the cache on the elected master. The Nomad cache is essential to Nomad's download once to branch feature. The cache enables Nomad to hold its downloaded content so that it can be distributed locally to other Nomad peers. The Nomad cache contains downloaded content (such as packages, applications, and software updates) which can vary in size from relative small patches to rather large OS image files.

  • Cloud Support

    Nomad supports the following Configuration Manager (CM) on Azure scenarios:

  • App-V support

    Nomad supports application virtualization (App-V) applications which are deployed as streamed content by Configuration Manager.

  • Integrating with WakeUp

    The integration with WakeUp feature is not supported in the Tachyon 5.2 release. This feature is under consideration for re-design and may be available in future versions of Nomad.

  • Deploying Office 365 updates

    Configuration Manager introduced support for Office 365 agents in Current Branch 1602, and Nomad introduced support in version 6.1.100. This section describes how Office 365 deployments differ in terms of ACP requirements and goes on to describe how Nomad behaves during the download.

OS Deployment
Nomad support for Configuration Manager OS Deployment.
  • OS deployment task sequences

    Nomad can integrate with OSD strategies to maximize the efficiency of distributing large OS content across the network. It does this by providing a number of Task Sequence steps that can be integrated directly into your OSD Task Sequences.

Nomad Management
Real-time visibility of what content is downloading or available in each location, subnet and client. Real-time visibility of Delivery Optimization downloads and content availability in each location, subnet and device.
  • Nomad app overview

    The Nomad app Overview page gives a high level view of the current status of content throughout the entire network. By default, the view will show activity and status for both Nomad and Delivery Optimization. These defaults can be modified using the Technology filter (to show Nomad or DO activity only) and the Time period filter.You can use the Nomad app, powered by the Tachyon Platform to get a visual snapshot of download activity in your environment.

  • Nomad Download Pause

    Nomad integrates with Tachyon to enable pausing or resuming Nomad downloads throughout the estate. This feature provides a safety measure for situations when a faulty or harmful deployment is made by mistake. In such situations pausing Nomad downloads on all targeted devices can prevent or limit the potential damage.

    It can also be used to facilitate troubleshooting, making it possible to pause all Nomad downloads across the network and enable IT teams to eliminate content distribution from their assessment of network bandwidth usage.

Client Health

The purpose of Client Health is to ensure the success of your Content Distribution deployments. There are a number of ways Nomad supports Client Health.

  • Nomad Client Health

    Nomad is included as part of the 1E Client, and as part of that integration, we offer a Nomad client health compliance policy in Guaranteed State. This verifies common Nomad requirements such as ACP registration, disk availability, firewall exceptions, crash notifications and cache monitoring.

    The Nomad client health policy replaces the client health tile in the Nomad dashboard plus additional remediation steps:

  • MEMCM Client Health

    Many businesses rely on Microsoft Endpoint Manager Configuration Manager (MEMCM) to deploy software, patches and updates across their company networks. It is crucial that Configuration Manager is working effectively.

    The MEMCM Client Health policy monitors Configuration Manager client health and performance. It checks for cache availability, inventory cycles, service availability and Configuration Manager WMI integrity - common causes of Configuration Manager client problems on devices.

  • Windows Client Health

    Over time Windows devices can develop performance problems related to device or service availability. This policy verifies the available storage capacity on devices, notifies of application crashes, monitors WMI health and service function and also checks the behavior of core Windows services.

    The Windows client health policy covers all of the following:

  • Monitoring Nomad Client Health

    The Client Health page shows information from two Integrated Product Packs provided with the Tachyon Platform: