Introducing Nomad 6.3
Working with Nomad
Deploying Office 365 updates
Integrating with WakeUp
Managing large package distribution with multicast
Nomad Download Pause
Peer Backup Assistant (PBA)
OS deployment task sequences
The Download Monitor
The Nomad Baseline Wizard
- Client health
- Core features
Operational best practices
Frequently asked questions
- Feature Reference
Technical support for Nomad
The Nomad Baseline Wizard is used to create a Configuration Manager Baseline from the Configuration Manager console for settings related to Nomad and Client Health.
On this page
The Nomad Baseline Wizard
Baselines are used in Configuration Manager to help manage compliance settings. There are a number of reasons why you would create baselines for Nomad but specific examples include:
- Using separate baselines to configure different settings for client machines and DP Servers.
- Defining baselines with specific settings to be applied to machines in a particular site/collection.
- Create different baselines to enable or disable Nomad features on machines in particular collections.
The Nomad Baseline Wizard is accessible from the Configuration Manager console and makes it easy to define Nomad related baselines. The files created by the Wizard include a new Baseline and an associated Configuration Item that contains all the registry settings and rules used to apply Nomad and Client Health registry settings.
- The user can choose whether to remediate or just monitor these values when deploying a particular baseline
- If the baseline is deployed just for monitoring, any non-compliance of the settings on Configuration Manager clients will be reported as warnings to the server.
- The evaluation/remediation of these settings depends on the interval selected in the baseline deployment.
Running the Wizard
The Wizard can be launched by clicking on the Create Nomad Baseline button in the Configuration Baselines view in the Configuration Manager console.
The first screen of the Wizard lets you define the name of the baseline and how the baseline will be populated. You have two choices for the Configuration Type:
|Configure settings manually||Select this option to populate the baseline from scratch using the screens in this wizard.|
|Configure settings using MSI Transform|
Select this option to pre-populate the screens in the wizard by importing Nomad MSI and MST files.
When this option is selected a new screen appears called Import MST.
Before using this option you will need to have configured an MST file and have the associated Nomad installer file to hand.
This screen is only displayed if you select the Configure settings using MSI Transform option on the Configuration Type screen.
Here you can browse to the Nomad installer MSI file and the corresponding MST file. This is done by clicking on the Browse... button at the end of each field.
On clicking Next, the wizard will derive the registry differences between the MSI and MST file and add the corresponding rows to the Nomad Settings and Client Health Settings views.
Only the registry changes seen in the MST file are imported any other changes in the MST are ignored.
Next, the Wizard displays the Nomad Settings screens where the Nomad Registry Settings can be entered and edited.
To add a registry entry Type into the Registry Value Name field. The Wizard will provide suggestions for auto-completing the entry.
For integer values you can also enter hex numbers preceded by 0x.
Client Health Settings
The next screen lets you set the Client Health Settings.
There are two sections on this screen. The top section lets you set the general Client Health registry values. This controls how Client Health is configured. The bottom section lets you enable or disable individual health checks.
The picture opposite shows three health checks where Nomad AE Connectivity and Nomad License State have been set to Enabled and Nomad Cache in Temp has been set to Disabled.
Both the Nomad Settings and Client Health Settings screens are validated on clicking the Next button. The validations are:
- Empty values not allowed.
- Duplicate Nomad/ClientHealth registry settings are not allowed.
- Duplicate Health Check settings not allowed.
- When the data type is specified as an integer - only numbers (in decimal and hexadecimal format) are allowed.
The Summary screen shows all the settings entered on the previous screens and lets you do a final review before clicking Apply.
Nomad Baselines created in the Configuration Manager Configuration Baselines view
After clicking Apply on the Summary screen a baseline will be created with the settings made in the wizard.
The created baseline will also contain a Configuration Item that defines the registry values and rules that determine what the baseline will remediate.
Deploying the baseline
The baseline created by the Nomad Baseline Wizard can be deployed to a device collection from the Configuration Manager console. When the Deploy Configuration Baselines dialog is displayed you should check the Remediate noncompliant rules when supported checkbox if you want to remediate any values in the Nomad registry that vary from the baseline.