Summary

Nomad integrates tightly with Configuration Manager, acting as an alternate download provider on a per-package basis for software distribution, per-task sequence or per-site for applications and software updates. The Configuration Manager client requests the download of package data using Nomad where it acts purely as a download client with the execution of the program being handled by the  Configuration Manager client. The Nomad client must be installed on all  Configuration Manager client machines and on all distribution points (DP).

On this page

With Nomad as an alternative download provider, you can set the priority for package downloads, interrupting less urgent downloads and then carrying on from where they left off. The Nomad provider can also send Configuration Manager status messages that show the progress for package download. To configure Nomad as an alternate download provider, see Nomad and Configuration Manager.

Downloading from a web-enabled distribution point with Nomad

Nomad enables the elected master to download from a web-enabled DP using either HTTP or HTTPS. The election process and criteria remain unchanged and the downloaded package data is peer-shared using the existing file sharing architecture.

When the Configuration Manager client instructs Nomad to download package content, it provides a list of content locations. This is a list of available DPs containing uniform naming convention (UNC) addresses, mapped drives and web addresses (depending upon how many DPs are available and if they are internet or intranet enabled). The web addresses and ordered first in the list. Nomad uses the first available address from which to download the package source. In Configuration Manager , Nomad is auto-enabled to use both SMB and HTTP by default, manual configuration to use HTTPS is still required though if the DPs are internet enabled.

Nomad and Configuration Manager 

In Configuration Manager , Nomad can be set as a download provider for packages, task sequences, driver packages, OS images and boot images. This can be configured from the Properties page or from the New Wizard for each of these.

Nomad properties Nomad properties is accessible as a tab on the Properties dialog for:

  • Packages
  • OSD driver packages
  • OS images
  • Boot images
  • Task sequences

The following can be set on the Nomad Properties tab:

  • Enable Nomad – enables Nomad to be used as a data transfer service for the selected package. The other controls on this page are only active if this is enabled. On task sequence Nomad Properties pages, this option is labeled Enable Nomad – Modifies currently associated reference packages. This is to emphasize the fact that, for task sequences, enabling Nomad at the task sequence level modifies the Nomad settings for all of the packages referenced by that task sequence.
  • Cache Priority – determines when the cache is purged. Values are from 1-9; the lower the value, the more likely the cache is purged. Want to find out more about cache priorities?
  • Local Multicast – enables local distribution multicast for the package after it is downloaded. Want to find out more about multicast?
  • Work Rate (%) – determines the percentage of available bandwidth to use for the download. The default value is 80%. If you have set intra-day work rates, the lower of these two values is used.
  • Override Intra-Day Work Rate – overrides the intra-day work rate for the duration of the download. If a work rate value is set, it takes precedence over the default work rate.
  • Additional Settings – enables you to define arguments for the download command-line. The arguments are:

    ArgumentsDefault valueRangeDescription
    ++pr
    • For software distribution and task sequences, the default is 3 for Packages, 0 for Applications
    • For software updates the default is 1
    • 0 – Foreground (highest priority)
    • 1 – High
    • 2 – Normal
    • 3 – Low
    • 4 – Background (lowest priority)

    Sets the priority for the package download. Packages with a higher priority will be downloaded before lower priority packages.

    Be careful not to confuse package priority (++pr), a setting related to Configuration Manager package downloads with cache priority (an option on the Nomad properties page), a setting related to the Nomad cache.


    If a package with a higher priority comes along while a package with a lower priority is downloading, the current download will be suspended and the new package will be downloaded. When the new package has finished downloading the previously suspended download will be continued from where it left off.
    This caters for the situation where a large image package is being downloaded and a critical patch needs to be sent. Setting the critical patch to have a higher priority will enable it to download first and then allow the image package to continue downloading.

    If you modify the priority values for packages associated with a task sequence, you must set all the priorities for all the packages to the same value.
    ++sm
     1 to 99Sets the frequency of the Nomad download status message. These messages are useful for monitoring the status of large package downloads taking place over a long period of time. The messages appear in Configuration Manager under the downloading package's status. The messages are also logged locally in the Nomad log file on the client machine.

    The value for this argument sets the percentage of the download at which a status message is sent. So, ++sm=10 sets Nomad to send a message each time ten percent of the download has been transferred.

    The messages sent are subject to an overall default limit of one message per hour per client. This is to prevent Configuration Manager from being overwhelmed by status message coming from many thousands of clients.
    --debug
    9
    • 1 – minimal logging
    • 9 – default and recommended logging level
    • 25 – detailed logging. If you use this, we recommend you increase the size of your log file to more than 1MB.
    Sets the level for debug logging. Changing this value will result in a persistent change on the client.

Additionally, in Configuration Manager under Client Settings, the 1E Nomad Properties menu item allows the definition of default settings for applications and software updates. The item is available on the default client settings, where it is best practice to configure them. If necessary, custom client settings can also be used to apply alternative settings to different collections. The 1E Nomad Properties menu item is only available if Software Deployment’ and/or Software Updates options are selected in custom client settings.

Configuring deployments with Nomad

Packages and task sequences make use of deployments for distribution. Package deployments intended for use with Nomad must be set to Download content from distribution point and run locally for both fast and slow connections. For example:

 Download content from distribution point and run locally

For task sequences, you need to select the Download all content locally before starting task sequence option on the Distribution Points screen in the Deploy Software Wizard for the task sequence deployment. Any distribution options for software updates must also be set to download and run locally. For software updates, this is a client setting.

 Download content before running task sequenct

Configuration Manager client settings

You can set Nomad as a download provider for:

  • applications
  • software updates.

To do this:

  1. Open the Configuration Manager console.
  2. Under Administration, choose Client Settings.

    Setting Nomad as a download provider for applications and software updates

  3. On Default Client Settings, choose Nomad Properties from the context menu.

  4.  In the Nomad Settings dialog, unique settings can be stored for both Application Management and Software Updates.
    Unique settings for application management and software updates

Custom device settings

As an alternative to changing the Default Client Settings, you can enable Nomad for Applications and Software Updates in within a custom client settings group. When creating new or modifying existing Custom Device Settings to enable Nomad, ensure the Software Deployment custom setting is selected (to enable Nomad for Applications) and Software Updates custom setting is selected to enable Nomad for Software Updates. When the Custom Settings have been created or modified to include these options, right-click the custom client settings (by Name) in the Client Settings list in the console, select 1E Nomad > Nomad Properties and enable and configure Nomad for Application Management and Software Updates as indicated in the screenshot above.

 Custom deice settings

When using Nomad in an OS Deployment Task Sequence that includes Applications or Software Updates, it is necessary for Nomad to be enabled (for Application Management and Software Updates respectively) in the Default Client Settings. When a Task Sequence is executing and the ConfigMgr client is initially installed, it uses only settings from the Default Client Settings and will not apply any custom settings.

Custom Nomad task sequence steps

Nomad includes a number of custom task sequence steps that can be used to integrate with OS deployments.