New in Nomad 7.0.200

This maintenance release is implemented as the Nomad module in 1E Client 5.1 and introduces the following features

  • Certificate-based client authentication. Nomad peers can now use client authentication certificates to authenticate peer-to-peer communications, as an alternative to the default Windows authentication using the local SMSNomadP2P& account that the Nomad service creates and manages. When you enable this option, Nomad will not create the local account and you no longer need to allow the local account to access the computer from the network. This feature is supported in the full OS, in Windows PE and for Peer Backup Assistant. This enables organizations to implement Nomad in conjunction with best practice security policies. 
  • Configuration Manager Enhanced HTTP Support. Microsoft introduced Enhanced HTTP in CM1810 to allow organizations that struggled to manage PKI certificates to use secure communication between clients and DP without the need for PKI-generated certificates. Enhanced HTTP also allows administrators to remove the Network Access Account as it implements a new token-based authentication endpoint on DPs and MPs that do not require Windows authentication. Nomad is now able to communicate with this token-based endpoint and download content from a DP when Enhanced HTTP has been enabled. In this scenario the Network Access account can also be removed. Refer to the Microsoft Configuration Manager documentation for more details on Enhanced HTTP and the Network Access Account   
  • Support for multiple Certificate Authorities. When configuring Nomad to use HTTPS when communicating with a DP or for P2P communication, the Nomad CertIssuer registry setting defines the issuing Certificate Authority (CA). Nomad now allows multiple CAs to be defined and also supports sub-string matching (for example, if you have ROOTCA1 and ROOTCA2, you can specify ROOTCA as the CertIssuer and Nomad will be able to use a certificate from either ROOTCA1 or ROOTCA2).
  • Improved PKI client certificate selection logic. When using HTTPS for communication with HTTPS CM Site Systems or P2P communication using PKI client certificates and the CM client is using PKI client certiicates, Nomad will use the same certificate that CM uses. If CM is using self-signed certificates (or is not present at all) then in most cases Nomad will be able to select an appropriate certificate from the local computer personal store without additional configuration.   
  • VMware Workspace One support. Nomad 7.0.200 includes updates that will enable VMware Workspace One clients to download and share content using Nomad. This will be supported in an upcoming VMware Workspace One release.
  • Improved handling of updated Software Updates. If the source for a Software Update is updated after it has been distributed to one or more clients, Nomad clients may get into a situation where they get into a loop downloading an invalid LsZ file from peers that have the older version of the content. Improvements have been made that can be enabled through the CompatibilityFlags.
  • Option to turn off or reduce election notifications in Nomad log. By default, Nomad logs all election responses when elections occur. In large subnets this can result in the logs filling up and rolling over. You can now turn off or limit the number of election responses that are logged.
  • 1E Client telemetry for Nomad feature usage. To help 1E understand how customers are using and configuring our products, a telemetry feature has been implemented in Tachyon Platform 5.1. When the Tachyon Platform is implemented, the 1E Client sends telemetry data relating to enabled Nomad features to the Tachyon server. This data will be forwarded to 1E if you enable email and telemetry in Tachyon Setup. If telemetry is not enabled in the platform, the data can be manually exported and may be requested by 1E Support when troubleshooting issues.                 

The Nomad 7.0.100 maintenance release was implemented as the Nomad module in 1E Client 5.0. This release included rolled up hotfixes but did not introduce any new features.

The main Nomad 7.0 release contained the following features:

  • NomadBranch 7.0 client is the Nomad module in 1E Client 4.1 - refer to Installing and upgrading for more details on how to install/upgrade Nomad 7.0
  • Support for NomadBranchTools installation on remote SMS Providers - NomadBranchTools can now be installed on remote SMS Providers without the manual steps that were required previously.
  • Support for Windows 10 Express File Updates - 1E Client 4.1 supports download of express installation files deployed through Configuration Manager. To use this feature in Nomad, you must first configure Delivery Optimization Download Mode to 0 on all clients. For new installations, the feature is enabled by default and for upgrades it can be enabled in 1E Client 4.1 by setting bit 26 (0x4000000, 67108864 in decimal) of the CompatibilityFlags registry value.
  • Support for downloading content for CM Software Updates from Microsoft Update - if you deploy Software Updates, including regular updates, Windows 10 express updates and Office 365 updates with Configuration Manager and in the deployment settings select the option If software updates are not available on distribution points in current, neighbor or site boundary groups, download content from Microsoft Updates, Nomad will be used to download that content from Microsoft Update if it is not available from a DP or local Nomad peers. (Please refer to CompatibilityFlags bits 27 and 28 for further details).

Enhancements:

  • SSD optimizations 
    • Large Configuration Manager deployments and downloads to 30K or more machines could result in significant traffic spike from 1E Client to an ActiveEfficiency server that may result in IIS 503 Overload errors, this has been optimized.
    • When Local SSD is enabled to support networks where broadcasts are disabled, it is not used when a Nomad master detects broadcasts. This allows the same SSD setting to be used by all clients in a mixed network environment.
  • Improved resilience of content registration - a Content Registration Cycle mechanism has been introduced that registers the pending and failed content registrations with ActiveEfficiency.
  • Support for TLS 1.1/1.2 in environments where TLS 1.0 is disabled.

Features released in Nomad 6.3.201

This maintenance release introduced the following features:

Features released in Nomad 6.3.100

This maintenance release introduced the following features:

  • Enhanced Nomad support for Office 365 Updates - Nomad support for Office 365 updates has been enhanced to add support for Peer copy over HTTP or HTTPS and to enable the Single-site download to work with updates.
  • Support for Configuration Manager in the Cloud - Nomad is able to use Configuration Manager Distribution Points hosted on the Windows Azure platform. Nomad has also been tested to work in Azure Infrastructure as a Service (IaaS) scenarios, where Configuration Manager and Active Directory are hosted on Windows Azure platform. In this scenario, ActiveEfficiency Server may also be hosted on the Windows Azure platform.
    Nomad also supports downloading from Cloud Distribution Points and communication via the Cloud Management Gateway. Please refer to Cloud Support for more details.
  • Increased download speed - the size of Nomad download blocks has been made dynamic. This enables Nomad to better adapt to the available link bandwidth and increases the efficiency and speed of the download on high-bandwidth links whilst still maintaining its minimal impact on low-bandwidth links. This enhancement has been made available to downloads from the DP as well as peer-to-peer copying. Please refer to Maximizing download speed for high-bandwidth links using Dynamic Block Sizes for more details.
  • New cached content report available on the Nomad dashboard - now you can view the location of content held in Nomad caches across the network providing greater visibility on where content is being stored. Please refer to The Nomad dashboard - Cached content report for more details.
  • 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. Please refer to Nomad Download Pause for more details.
  • Nomad pass through to Configuration Manager on license expiry - Nomad can be configured to pass responsibility for content download back to the Configuration Manager agent when the Nomad license expires. This minimizes the possible impact on downloads when a Nomad licence renewal is imminent. Please refer to Installation - Handling license expiry gracefully for more details.
  • Optimization of Nomad Cache cleaning to minimize impact on local devices - from Nomad 6.3 and above the Nomad cache now has a regulated cache cleaning cycle that works in addition to the automated cache cleaning rules. This is to cater for the lately added pre-caching feature where extra content is being stored in the Nomad caches. For more details please refer to Cache management - The cache clean cycle.
  • New Nomad Baseline wizard for creating Configuration Manager baselines for Nomad - This wizard creates a baseline in Configuration Manager that can be used to manage settings related to NomadBranch and ClientHealth. Please refer to The Nomad Baseline Wizard for more details.
  • Added support for Windows Server 2016 Core OS and Windows Server 2012 R2 Core OS

Features released in Nomad 6.2.200

This release introduced the following features:

Features released in Nomad 6.1.100

This maintenance release introduced the following features:

  • Support for Office 365 update deployments.
  • Improved support for wireless clients:
    • Local SSD – enables downloads from subnet peer masters.
    • Enable devices on WLAN to become content providers.
  • Nomad Dashboard enhancements:
    • Drill-down for client version distribution versions.
    • Support for Word/Excel/PDF export.
  • Client Health has a new Nomad cache in temp check. When this check is enabled, it will send a warning if it detects the Nomad cache directory in C:\Windows\temp
  • Support for Configuration Manager CB 1511, 1602, 1606 and 1610.
  • Support for Server 2016.

Features released in Nomad 6.1

This release introduced the following features:

  1. The Nomad dashboard – provides a visualisation of activities and their statuses on collections and devices to enable to make informed decisions. You must be running ActiveEfficiency 1.9.500 or later to benefit from this feature.
  2. Dynamic pre-caching – how pre-caching keeps up when there are modifications to collections in Configuration Manager. You must be running ActiveEfficiency 1.9.500 or later to benefit from this feature.
  3. Client health – a background process that monitors Nomad to ensure that it is smoothly. It reports the statuses of the services it monitors in the Nomad dashboard, and where possible, performs a self-heal.
  4. Nomad SECure – signs, encrypts and compress content on the DP for clients to download.
  5. BIOS to UEFI – automates firmware reconfiguration on Dell, Lenovo and HP systems to switch from BIOS-emulation to native UEFI with secure boot during a Windows 10 deployment.
  6. Enhancements:
    1. Hash checks for Windows 10 service updates
    2. HTTPS support for ActiveEfficiency – can be set-up during installation or by updating the PlatformURL registry value post-installation.
  7. Support for Configuration Manager CB 1511 and 1602.

Features released in Nomad 6.0.200

This maintenance release introduced the following features:

  • Precaching improvements and enhancements
    • Managing pre-cached jobs in the Configuration Manager console
    • RBAC support
    • Support for multiple management points
    • Hash validation
    • Support for custom ports
    • Powershell cmdlets for Pre-cache job management
  • OSD
    • Support for Auto Apply drivers tS action in SMSTSNomad
    • Support for multiple network access accounts
  • Core
    • Job Manager improvements for improved queuing of jobs
    • Improved interaction between Nomad and NightWatchman
    • Net literal support for SSD and PBA/SSPBA/PBAHA

Features released in Nomad 6.0

  • Nomad pre-caching
  • OSD Integration enhancements
  • FIPS compliant communication encryption
  • Enhanced Nomad share security
  • Windows 10 system deployment and support
  • Configuration Manager 2012 SP2 and Configuration Manager 2012 R2 SP1 support

Features released in Nomad 5.5

This release introduced the following features:

  • WakeUp integration – Nomad can now integrate with the WakeUp component of NightWatchman Enterprise enabling Nomad machines that contain useful content to be woken up automatically when a peer requires the content.
  • Improved content integrity check (CIC) behavior – Nomad clients prevent the download and re-distribution of content where the hash does not match the client's expected hash for the content.

  • Support for App-V 5.0 SP2.
  • Effective memory usage for large file P2P transfer – handles large file transfers that exceed system memory without impacting machine performance.

Features released in Nomad 5.2

This release introduced the following features:

  • Single site peer backup assistant (PBA) – makes use of single site data to locate potential PBA data stores at the local site not just the local subnet.
  • High-availability peer backup assistant – supports the creation of multiple backups of USMT data to minimize risk and maximize success for OS migration.
  • App-V support – integrates with App-V streaming applications, recognizing that the initial download is only partial enabling full download at a later date.
  • Support for Configuration Manager 2012 R2, Windows 8.1 and Windows Server 2012 R2.
  • Pre-stage content using Nomad task sequence action – supports the use of custom ports in Configuration Manager 2012 and Configuration Manager 2007 when using Nomad for OS deployment.

Features released in Nomad 5.1

This release introduced the following features:

  • New Nomad PBA task sequence actions.
  • PBA supported across subnets.
  • PBA supports redundant backups.
  • Multicast support added to install and configure Nomad in WinPE and pre-stage content using Nomad task sequence actions.
  • Pre-stage content using Nomad task sequence action no longer requires the use of LSZ delegation for non-site server distribution points.
  • Pre-stage content using Nomad task sequence action displays progress information in the task sequence user interface.
  • Streamlined OSD task sequence Nomad integration.