Introducing Nomad 7.0.200
Working with Nomad
For details of how to obtain this utility, please see Installing Nomad tools for operating system deployment.
The format of the Nomad service command-line is as follows:
NMDS commands can only be used within a Configuration Manager task sequence and must be wrapped by calling NomadPackageLocator.exe. NMDS functionality requires setting and making use of task sequence variables, which is not directly supported via the
NomadBranch.exe command. We recommend you first try the pre-defined Nomad custom task sequence actions available from the Configuration Manager console and failing that, use the equivalent NomadPackageLocator commands. Only use
NomadBranch.exe NMDS commands as a last resort – they are minimally documented below for completeness only.
Nomad service command-line switches are:
Forces verification of specific content in Nomad cache.
|Forces verification of all content in Nomad cache.|
| ||Stops the current Nomad job immediately, which then exits with an error condition. This is intended for use by an administrator when a problem has occurred and a running job is taking an excessively long time.|
| ||1||Sets the debug level for the NomadBranch service, where typical values are: 1=general logging, 31=maximum logging. The value is set in the registry and retained.|
|Starts a pre-cache cycle.|
|Starts the |
| ||Stops the |
|–NMDS_COMPLETE||The NMDS_COMPLETE argument is available on the |
|–NMDS_DELETE||The NMDS_DELETE argument is available on the |
|–NMDS_FIND||The NMDS_FIND argument is available on the |
|–NMDS_HA||The NMDS_HA argument is available on the |
|The NMDS_POLL argument is available on either the |