NMDS_FIND

 

  • Nomad PBA Task Sequence steps are not designed for use with offline USMT or WinPE

  • -NMDS_POLL command-line option for the NomadPackageLocator.exe tool cannot be used in WinPE

  • -NMDS_<command> command-line options for NomadBranch.exe have not been tested in WinPE, so their behavior may be unpredictable in that environment.

The NMDS_FIND argument is available on the NomadPackageLocator.exe (recommended) or NomadBranch.exe service argument-line. When run, it locates and connects to the share associated with it. It is only for use in a task sequence.

NMDS_FIND takes the following format:

Copy
NomadPackageLocator.exe -NMDS_FIND,<name>

or

Copy
NomadBranch.exe -NMDS_FIND,<name>

Using the following parameter:

Parameter

Description

<name>

Used to identify the shared cache and must be the same as the one used in the NMDS_POLL argument that initially requested the share, i.e. usually the value of the %PBAComputerName% of the task sequence variable. This may be up to 40 characters, consisting of 0-9 and A-Z characters, and is case-insensitive.

Storing the result

This is not necessary if NomadPackageLocator.exe is used.

The details for the located share can be set into a variable %NMDS_REMOTE% using the TSEnv2.exe function. For example, the following argument locates the shared cache for acme1234 and sets the %NMDS_REMOTE% with the details of the located share.

Copy
cmd /c "NomadBranch.exe -NMDS_FIND,acme1234 | TSEnv2.exe -"

However, NomadPackageLocator.exe sets up task sequence environment variables automatically. The equivalent of the above argument is:

Copy
cmd /c "NomadPackageLocator.exe -NMDS_FIND,acme1234"

Deleting the share and contents

Once you have finished using the items in the share, issue the NMDS_DELETE argument to delete its contents and associated share.

Task sequence environment variables

NMDS_FIND uses the following task sequence environment variables:

Name

Use

%OSDStateStorePath%

Set to the path to the share that USMT should use for restoring migrated data.