Introducing Nomad 7.0.200
Working with Nomad
Download once to branch
Download resumption and consistency checking
- Nomad Cache
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
Peer access methods
Nomad can be configured to use HTTP or HTTPS for all P2P sharing – thereby eliminating Nomad's dependency on SMB and File and Printer Sharing Services. Nomad also supports certificate-based client authentication, which eliminates the local SMSNomadP2P& account previously required for clients to authenticate with the elected master.
This is the recommended method of peer sharing content. For more detail please refer to Peer copy over HTTP or HTTPS.
File and Printer Sharing Services
This is the original and default method for Nomad peer sharing, which uses SMB and requires File and Printer Sharing Services.
For more detail please refer to The Nomad share.
Nomad can be configured to bypass these services and use the connectionless transfer protocol over the User Datagram Protocol (UDP) instead.
Connectionless P2P does not use authentication and is approximately five times slower than SMB. This transfer method is only recommended for environments where other methods are not available.
To enable Connectionless P2P update the Nomad P2Penabled registry value on all Nomad clients to:
- 0x0000 – P2P disabled
- 0x0002 – Enable connectionless P2P server
- 0x0004 – Enable connectionless P2P client
In most cases both P2P server and P2P client should be enabled, by setting 0x0006 (decimal 6), as shown below:
Switching between wireless and wired network connections
When network connections are switched between wireless and wired, Nomad may encounter problems accessing the share. Problems are likely to occur if DHCP uses a short lease time and the DNS does not reflect these changes quick enough. To mitigate these issues, from version 4 onwards, Nomad has support for net literal names (IP addresses) for identifying its shares. Nomad clients normally use the elected master's hostname to connect to the NomadSHR in order to download the LSZ, LST and package files.
Using IP addresses to access shares
To configure Nomad to use net literal names when connecting to peer shares, update the P2Penabled registry value to include:
- 0x0001 – P2P enabled
- 0x0008 – Enable use of net literal names (IP addresses)
For example, P2P enabled (0x1) plus enable use of net literal names (0x8), by setting 0x0009 (decimal 9), as shown below:
By default, Nomad clients use the master's hostname to connect to the master in order to retrieve the package and signature files.
In a multi-forest environment where computers from different forests may be present in the same subnet as the peers are not able to connect to the master using just the hostname. In this scenario, Nomad should be configured to use FQDN for peer-to-peer connections. For this to work, it is necessary that the reverse lookup for IP addresses is correctly configured and running. If this is not available, Nomad reverts to using the IP address for connection to P2P shares.
To configure Nomad to use FQDN when connecting to peer shares, update the P2PEnabled registry value to include:
- 0x0001 – P2P enabled
- 0x0010 – Enable use of FQDN name
For example P2P enabled (0x1) plus enable use of FQDN (0x10), by setting 0x0011 (decimal 17), as shown below: