Introducing Nomad 7.0.200
Working with Nomad
Download once to branch
Download resumption and consistency checking
Distributing software with Nomad and Configuration Manager
Downloading content for CM Software Updates from Microsoft Update
Deploying Office 365 updates
Windows 10 Express Installation Files and Delta Content for Updates
Remote differential compression integration
- Download once to branch
OS Deployment features
Operational best practices
Frequently asked questions
- Core features
Nomad and Configuration Manager
Nomad can be set as a content provider for individual instances of the following types of Configuration Manager content.
To configure properties in the Configuration Manager Console:
- Navigate to Software Library → Overview and then to one of the following:
- Application Management → Packages and select a package
- Operating Systems → Driver Packages and select a driver package
- Operating Systems → Operating System Images and select an operating system image
- Operating Systems → Operating System Upgrade Packages and select an operating system upgrade package
- Operating Systems → Boot Images and select a boot image
- Operating Systems → Task Sequences and select a task sequence
- Right-click and select Properties or click on Create and to start a New Wizard. Nomad properties is then accessible on the Nomad tab.
Nomad can be set as a content provider for Applications and Software Updates. You must configure settings for all Applications and all Software Updates using Client settings, as described below Configuration Manager client settings, and not individual instances.
Nomad includes a number of custom task sequence steps that can be used to integrate with OS deployments.
The following can be set on the Nomad 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 the Nomad tab for a task sequence, 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 – defines the priority of this specific content in the Nomad cache to manage purging when new content requires cache space. Values are from 1-9; the lower the value, the more likely the content will be purged by other content that requires the space. 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 unless you enable the Override Intra-Day Work Rate option
- Override Intra-Day Work Rate – overrides the intra-day work rate for the duration of the download. If Intra-day work rates have been defined on the client and this option is selected, the value defined in the Work Rate property will take precedence over the Intra-day work rate for the current day and time.
- Additional Settings – enables you to define arguments for the download command-line. The arguments are listed in the table below:
Configuration Manager defines the following default values
Nomad will use the default values defined by CM unless the ++pr argument is specified.
Note that as these defaults are defined by Microsoft, they may change in future.
Sets the priority for the package download. Packages with a higher priority will be downloaded before lower priority packages.
|1 to 99||Sets 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,
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.
|9||Sets the level for debug logging. Changing this value will result in a persistent change on the client.|
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 clients using a distribution point from both a current boundary group and from a neighbour boundary group or the default site boundary group. Using Nomad, you can also safely allow clients to use distribution points from the default site boundary group. For example:
For task sequence deployments, select the Download content locally when needed by the running task sequence option on the Distribution Points screen in the Deploy Software Wizard. Using Nomad You can safely allow clients to use distribution points from the neighbor boundary group and allow clients to use distribution points from the default site boundary group if this is appropriate based on your Boundary Group configuration.
Enabling Nomad for Applications and Software Updates
Set Nomad as a download provider for applications and software updates in Configuration Manager Client Settings.
To do this:
- Open the Configuration Manager console.
- Under Administration, choose Client Settings.
On Default Client Settings, choose Nomad Properties from the context menu.
In the Nomad Settings dialog, unique settings can be stored for both Application Management and Software Updates.
Custom device settings
In addition to configuring the Default Client Settings, you can also enable Nomad for Applications and Software Updates in within a custom client settings group.
You must configure Default Client Settings so that clients have default settings to fall back to if they move out of scope of the custom settings.
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.