1E 8.1 (on-premises)

AuthenticatedUsers

1

Grants read-only access to the Nomad cache as follows:

Unauthorised HTTP requests to access the caches are met with a 403 status code.

The Nomad share has more information about share permissions and NTFS security. The difference between Authenticated Users and Everyone depends on the OS version, but in general Everyone includes Authenticated Users plus Guest.

BlockSize

131072(128KB)

Must be between 4096(4KB) to 4194304(4MB) inclusive.

CacheCleanCycleHrs

0 (turned off)

The first automatic cache clean runs randomly between 10 to 60 mins of service start up. Subsequent cache clean cycles run after the number of hours specified.

0 means feature turned off. No cache cleaning cycle would run. Changing this registry entry performs an internal restart.

The minimum value is 4.

The maximum value is 168 (Once a week)

Please refer to Cache management for details about other cache management settings.

CacheCleanSubnetLookup

REG_DWORD

1

Before deleting content, Nomad checks if it is on any other client in the same subnet, and will only delete local content if the same is present on at least one other client on the same subnet.

To disable subnet lookup, set the value to 0. Its value can be 0 or 1.

The default value is 1, subnet lookup is enabled.

New setting introduced in 8.0.

Please refer to Cache management for details about other cache management settings.

LocalCachePath

%ALLUSERSPROFILE%\1E\NomadBranch\

There are two registry values called LocalCachePath that are used by Nomad.

The path is created if it does not exist. If the drive letter does not exist, and it is not possible to create the specified path, %TEMP% is used. Default values are dependent on OS.

Known issue fixed in latest accumulated hotfix

The value for the installer property CACHEPATH requires a trailing backslash \. When Nomad is installed on a DP this location is also used for the LSZFiles vDir folder. If LocalCachePath does not contain a trailing backslash, then:

PBA cache is also derived from the same installer property MODULE.NOMAD.CACHEPATH, but it is stored in the registry value> CachePath in the NomadBranch\NMDS registry key.

CachePath

<NomadCachePath>\NMDS

This REG_SZ registry value is found under the PBA registry key NomadBranch\NMDS. This parameter relies on the folder it points to as being configured as a share. In normal circumstances, this should not be modified from the default value.

The MODULE.NOMAD.CACHEPATH installer property also used to configure the location of the Nomad cache, which is stored in the registry value LocalCachePath. The location of the PBA cache is derived from the MODULE.NOMAD.CACHEPATH property, and is stored in the registry value CachePath in the NomadBranch\NMDS registry key.

CacheStateSyncIntervalMinutes

1440 (1day)

Range: from 60 to 525600 (1Year).

CertIssuer

" "

Set this value to the name of the certificate issuer (Certificate Authority (CA)) that Nomad should use to select the appropriate PKI certificate. A case-insensitive substring-within-a-string match is performed.

If you have multiple CAs you can specify a:

If you are only using HTTPS for downloading from an HTTPS DP (That is, not using HTTPS for peer-to-peer data transfer) you can leave this blank and set CertSubject instead.

CertSubject

" "

For downloads over HTTPS from the Distribution Point, set either the CertIssuer or CertSubject registry values. Set this value to the subject name of the certificate that Nomad should use to select the appropriate PKI certificate. The match has the following properties:

If you have multiple valid subject names you can specify a:

For the installer property, configure either MODULE.NOMAD.CERTISSUER or MODULE.NOMAD.CERTSUBJECTinstaller properties for HTTPS downloads.

CompatibilityFlags

0x1E18000A (504889354)

For Nomad in full OS, the registry value is set to the sum of the values for the required bits.

The default value combines the following settings:

First bit is bit 0. The default in binary is: ‭0001 1110 0001 1000 0000 0000 0000 1010

0x00100002 (1048578)

For the task sequence action Install and configure Nomad in Windows PE, the registry value is set to the sum of the values for the required bits.

The default value combines the following settings:

The installer property must be set to sum of the values for the required bits, and given in decimal notation. For example, the following installer command-line uses:

> msiexec /i 1E.Client-x64.msi MODULE.NOMAD.COMPATIBILITYFLAGS=505020427 [other properties] /qn

0

0x0001

1

Never check hashes of downloaded content.

1

0x0002

2

Enable longer values for hashes. This value is auto-enabled when the Configuration Manager client is detected.

You must manually configure this setting on any DP that does not have the Configuration Manager client installed.

2

0x0004

4

Calculate CRCs as files are downloading.

3

0x0008

8

Fix wrong IPs in election messages.

On multi-homed machines sometimes the IP from a wrong adapter can get sent in the election messages resulting in peers failing to connect to the master. Enabling this flag causes Nomad to correct such IPs at the time when messages are received and thus prevent master connectivity issues.

4

0x0010

16

Determines compatibility with Nomad v3.x caches. Set this option once all Nomad v3.x installations have been upgraded.

5

0x0020

32

Disable all RDC data generation.

6

0x0040

64

Keep Packages that failed the CRC test during P2P or download from DP.

7

0x0080

128

Prevent computers using wireless connections from becoming fill-in multicast masters.

8

0x0100

256

Include LinkLocal IPv4 addresses.

9

0x0200

512

Include LinkLocal IPv6 addresses.

11

0x0800

2048

RESERVED

12

0x1000

4096

Do not automatically jump from HTTP to HTTPS during download from DP.

13

0x2000

8192

Always use HTTPS. (Use this setting when Configuration Manager is configured to use HTTPS-only communication for downloading content from Distribution Points)

14

0x4000

16384

RESERVED

15

0x8000

32768

RESERVED

16

0x00010000

65536

RESERVED (this flag is no longer used; previously this flag disabled a workaround for the issue described in Nomad post-installation tasks: IIS request filtering)

17

0x00020000

131072

Disable DelegatedLSZ checks and errors.

18

0x00040000

262144

Disable partial download when App-V streaming, i.e. download entire application.

19

0x00080000

524288

Enable full hash generation for SIS content when an LsZ file is generated on a DP. If this is not enabled, SIS content is trusted, and corrupted content may be downloaded. Enabled by default.

20

0x00100000

1048576

Abort download on the Nomad client if an LsZ hash mismatch is detected. If this is not set, when a Nomad client detects a hash mismatch it will re-request LsZ generation on the DP then try again, and get stuck in a loop if the SIS content is corrupt. Must be set on clients if Bit 19 is set on DPs. Enabled by default.

25

0x02000000

33554432

Turn off Dynamic Block Size. This flag is set by default, which means Dynamic Block Size is disabled by default.

26

0x04000000

67108864

Enable download of Windows 10 Express update files. Enabled by default.

27

0x08000000

134217728

Enable download of full file software updates from Microsoft Update when deployed through Configuration Manager. Enabled by default.

28

0x10000000

268435456

Enable download of byte-range software updates (e.g. Express updates, O365 updates) from Microsoft Update when deployed through Configuration Manager. Enabled by default.

30

0x40000000

1073741824

Enable SoftwareUpdate metadata validation. This is not enabled by default. It can be used to resolve rare issues related to SoftwareUpdates where the contents could be updated without any change in its ID or version. Please refer to Resolving SoftwareUpdate metadata validation for more details.

ContentProviderOnWifi

0

Values are:

Platform\ContentRegistration

0

To enable content registration, update the value to 1 – it is found under the Platform\ContentDistribution

To enable SSD when you install Nomad, you must specify the MODULE.NOMAD.SSDENABLED installer property and ensure the Tachyon client is enabled by specifying SWITCH and BACKGROUNDCHANNELURL installer properties. If MODULE.NOMAD.SSDENABLED is specified during installation, the registry value of ContentRegistration is automatically set to 1.

If you want to enable SSD as a provider after installation, then you also need to configure the registry values for SSDEnabled and ContentRegistration, in addition to enabling the Tachyon client. The ContentDistribution registry setting is found under the Platform key.

In legacy versions of Nomad, Platform features were provided using ActiveEfficiency. This required the PlatformURL setting to be configured. This is no longer required. You will see that the PlatformURL registry is used, but this is configured automatically by Nomad on startup by querying the value that the Tachyon client is using (stored in the 1EClient.conf file).

Debug

0x09 (9)

See the table below for customer supported values. The default is a combination of 0x01 (Minimal logging) and 0x08 (Registry changes). For example, to set maximum debugging, set bit 0, 3 and 4, which is a value of 0x19 hexadecimal or 25 decimal.

Values on the installer command-line must be provided in decimal. So to set maximum debugging you would use the following installer command-line:

> msiexec /i 1E.Client-x64.msi DEBUG=25 [other properties] /qn

DeliveryOptimizationReportingEnabled

0

Enables monitoring of Delivery Optimization downloads and reporting them to Tachyon Platform (ContentDistribution).

Delivery Optimization monitoring and reporting is only supported in versions of Windows Server 2019 and Windows 10 Version 1909 onwards.

When it is enabled, DO download events get written to .etl files in the Nomad cache folder, for example: NomadDo-20210325-182415.etl.

And aggregated information about the downloads gets writtern to sqlite files Do.db and DoDownloadMonitor.db in LocalDb folder inside Nomad cache folder.

DownloadTimeout

0

This parameter is associated with the distribution point resilience feature and is used in conjunction with the RecycleDPDelay registry value. If a value greater than zero is set, the download timeout will either use this or the Configuration Manager setting depending on which is the smaller value.

When the timeout is reached, the job package download is cancelled and a success is sent to the Configuration Manager client with the ERROR_MAXDURATION timeout error sent as the package status message.

The default is to use the Configuration Manager setting (28 days by default).

DpCacheCleanupEnabled

0 (turned off)

This entry controls the cached LSZ files cleaning feature. When turned on, this feature deletes all LSZ files in a Distribution Point (DP) cache where the associated content is not present in ContentLib.

The following table describes the values this entry may be set to:

Please refer to Cache management for details about other cache management settings.

DPNotAvailableCodes

0x205A, 0x205D

This registry entry contains a comma-separated list of return codes, see Nomad return codes for a list of the possible ones. If Nomad encounters one of these during download it will attempt a retry from an alternative DP. It gets the list of possible DPs from Configuration Manager. The two return codes set as default are the only ones that are applicable to DP availability:

Under normal circumstances, you would not change this from the default value. You may want to not allow failover to an alternative DP altogether, in which case you would set the value to " " in the registry. Or you may only want to failover if the DP path was not found, in which case you would set the value to 0x205D only.

This installer property should be set to a string containing the comma-separated hex values. For example the following sets Nomad to failover to the next DP only when the DP path was not found:

> msiexec /i 1E.Client-x64.msi DPNOTAVAILABLECODES="0x205D" [other properties] /qn

EnforceQuotas

0x0 (0)

Enables quotas to be enforced but requires Windows Disk Quotas to be configured. If the size specified in the NMDS_POLL request causes the quota to be exceeded, the request fails and you get disk full error. This registry value is found under the PBA registry key NomadBranch\NMDS.

GenerateWEREvents

1

If enabled and if Nomad experiences an unexpected failure, a dialog is displayed prompting the user to send the debug information to Winqual which is forwarded to 1E for continued quality improvements. Values are:

HAACKTimeoutMins

20

Applies to synchronized backups only. The PBA tost sends the acknowledgement messages back to the machine running the task sequence approximately every 5% of the synchronized copy. This registry value is found under the PBA registry key NomadBranch\NMDS.

LocalSsdStagger

REG_DWORD

5

Sets the local SSD query stagger duration in seconds. The stagger is 0 (disabled) by default.

The maximum value that can configured is 600 seconds (10 minutes).

There is no SSD staggering in WinPE.

Local SSD happens when only when network broadcast is disabled.

This setting works in conjunction with SiteSsdStagger.

MultiCastMADCAPScope

SMSNomad

Values may be set using either of the formats in the table below.

<ScopeName>

<ScopeName> is the name of a scope defined in the DHCP (if you are using the Microsoft implementation of MADCAP). Use this format if you have multiple MADCAP servers. This method uses the time to live settings for the scope.

<MADCAP_ServerIP>

<MADCAP_Scope_IP>

<TTL>

Nomad is also capable of performing control multicast without a MADCAP server installation on the network. In order to use this feature, the <MADCAP_ServerIP> must be set to 0.0.0.0. For example, the following supports MADCAP server not being present, with a scope of 239.0.9.0 and a time to live of 3.

0.0.0.0,239.0.9.0,3

MaxAllocRequest

0xC8 (200)

Located under the PBA registry key NomadBranch\NMDS.

MaxCacheDays

0 (turned off)

Set to delete application or package content that last triggered Nomad elections before the specified number of days from the date the cache cleaner runs.

This ensures that only application or package content that have triggered elections recently will be kept in the cache.

0 means that application and package content will not be deleted automatically when the cache cleaner runs.

Please refer to Cache management for details about other cache management settings.

MaxCacheDaysThreshold

REG_DWORD

0

This is the maximum number of days content is present on a client. If it's not zero, then content will be deleted without any other checks once it reaches the threshold. If the threshold has a value greater than zero and less than 30, Nomad uses the threshold of 30 days and creates an associated log.

Default value is 0.

New setting introduced in 8.0.

Please refer to Cache management for details about other cache management settings.

MaxCacheSizeMB

0

There is no maximum value for this property. This method for determining the maximum size of the cache is an alternative to PercentAvailableDisk:

MaxConcurrency

0x3 (3)

Located under the PBA registry key NomadBranch\NMDS.

MaxDevicesFromAE

10

The maximum number of devices (i.e. machines) with the content (package, application or software update) that Nomad can retrieve from Content Distribution in one call. The maximum value is 20.

MaxElectionResponseLogging

By default this REG_DWORD value is not present and all election responses are logged.

Add this REG_DWORD value and set it to the number of responses that Nomad should log for any given election.

Setting the value to 0 effectively turns off logging of any election responses.

MaximumMegaByte

0

A non-zero value enables PBA share.

This registry value is located under the PBA registry key NomadBranch\NMDS.

MaxLogFileSize

5242880

When the log file reaches this size, it is renamed with a .LO_ extension and a new .LOG file is created. The .LO file is overwritten each time.

MaxPackageSizeFastLAN

0

Works in conjunction with the RunUncachedPermittedFastLAN registry value.

MaxPackageSizeRAS

0

MaxPackageSizeSlowLAN

0

MaxPacketsPerSecond

800

Modify this value with caution. If packets are sent too fast, machines will drop packets and multicast will not be effective - too slow and multicast works, but slowly. The default value is indicative of how this should be set.

MaxPreCacheDays

0 (turned off)

Set to delete pre-cached content that last triggered Nomad elections before the specified number of days from the date the cache cleaner runs.

This ensures that only pre-cached content that has triggered elections recently will be kept in the cache.

0 means that pre-cached content will not be deleted automatically when the cache cleaner runs.

Please refer to Cache management for details about other cache management settings.

MaxStatusFrequency

3600

Works in conjunction with the ++sm setting on the Nomad properties tab and the StatusMsgEvents registry values.

MaxStuckCount

100

The number of times Nomad attempts to copy content after failure (such as network outages, incomplete LSZ files, hash mismatches, election issues, connecting with peers) before it aborts the operation.

The range is 3 to 1000, but if the value is less than 3 or greater than 1000, it sets to the default of 100.

MaxSUCacheDays

0 (turned off)

Set to delete software updates that last triggered Nomad elections before the specified number of days from the date the cache cleaner runs.

This ensures that only software updates that have triggered elections recently will be kept in the cache.

0 means that software updates will not be deleted automatically when the cache cleaner runs.

Please refer to Cache management for details about other cache management settings.

MulticastSupport

0x0 (0)

All machines in a single branch must be configured using the same value for this parameter.

If you are not using multicast, deploy the Nomad branch agent with the MULTICASTSUPPORT property set to 0 to reduce the noise in Nomad logs.

Prior to Nomad 7.0 multicast was enabled (0x1) by default. Now it is disabled (0x0) by default.

0x0

0

No Multicast– disables the feature.

0

0x1

1

Data Only Multicast – choose this for a standard Nomad multicast. Data refers to the content of the downloaded package.

Nomad control communications are broadcast as normal on the local subnet. Select this option for standard functionality.

1

0x2

2

Control Only Multicast – control information refers to the communications between Nomad enabled machines, especially for elections.

This may be used if there is more than one subnet in a single location to enable a single Nomad master to be elected for all the subnets.

0x3

3

Control and Data Multicast – data and control information is multicast.

Select this option if a branch has multiple subnets connected by high speed routers.

NoHardlink

0

Values are:

For more detail about the Nomad Cache please refer to Nomad cache.

NomadInhibitedADSites

(empty)

A comma-separated list for each AD site to be inhibited. Useful for sites with:

For example, to inhibit three AD sites called site1, site2 and site3:

site1,site2,site3

Please refer to Design Considerations: Inhibiting subnets and sites.

NomadInhibitedSubnets

(empty)

A comma-separated list of each subnet to be inhibited in CIDR notation. Useful for sites with either of the following:

For example, to isolate two subnets:

10.2.0.0/16,192.168.9.0/24

Please refer to Design Considerations: Inhibiting subnets and sites.

P2PDisqualifyMaxNumPeers

5

A device does not further disqualify a peer if it has disqualified P2PDisqualifyMaxNumPeers number of peers within last P2PDisqualifyMaxWindowMins minutes.

P2PDisqualifyMaxWindowMins

60

A device does not further disqualify a peer if it has disqualified P2PDisqualifyMaxNumPeers number of peers within last P2PDisqualifyMaxWindowMins minutes.

P2PEnabled

9

The default (Hex 0x0009) configures P2P to use SMB and Net Literal Names.

You can set more than one option at the same time by combining the bit values. See the table below for details.

0

0x0001

1

(Default) Use the SMB protocol to share its own cache, and create the NomadSHR file share upon the start of the Nomad service, unless the CustomShare option has been enabled in SpecialNetShare. When P2PEnabled is set in addition to Bit 5 (use HTTP) or Bit 6 (use HTTPS), Nomad will attempt to use HTTPS/HTTP and will fall-back to SMB if HTTPS/HTTP is unavailable on other peers. To disable SMB P2P, set this bit to 0.

1

0x0002

2

Enable connectionless P2P server.

2

0x0004

4

Enable connectionless P2P client.

3

0x0008

8

(Default) Use Net Literal Names when connecting to P2P shares. This causes Nomad to use the Nomad master's IP address when connecting to the share and is recommended when running wirelessly.

4

0x0010

16

Use FQDN when connecting to P2P shares. Recommended when using a multi-forest environment where computers from different forests may be present in the same subnet. This requires that reverse lookup for IP addresses is correctly configured and running. If this is not available Nomad will revert to using the IP address for connecting to the P2P shares.

5

0x0020

32

Use the HTTP protocol to share its own cache and access other caches.

6

0x0040

64

Use the HTTPS protocol to share its own cache and access other caches.

P2PHttpPort

5080

Default HTTP port to use for peer copy. If you are using a custom port, ensure that all agents use the same custom port.

P2PHttpsPort

5443

Default HTTPS port to use for peer copy. If you are using a custom port, ensure that all agents use the same custom port.

P2P_Port

1779

P2PSslSettings

0

The default value (0) configures Nomad to use a self-signed certificate for server authentication and disables certificate-based client authentication.

P2PSslSettings is a numeric value where, when represented in binary, each bit represents a configurable option as defined in the table below. You can combine these options to derive the required value, for example setting P2PSslSettings to 3 (0x1 + 0x2) configures Nomad to use a PKI certificate for server authentication and also enables certificate-based authentication.

These options are only applicable if the HTTPS protocol has been enabled in the P2PEnabled setting.

If you are using PKI certificates you must deploy the certificates to all clients before enabling this option. Refer to Peer copy over HTTP or HTTPS for further details on using HTTPS and associated authentication.

0

0x0001

1

If not set (0), use self-signed certificate for server (Master) authentication

If set (1), use PKI certificate for server (Master) authentication

1

0x0002

2

Enables certificate-based client authentication (Requires a PKI client authentication certificate)

PercentAvailableDisk

10

By default, the cache will not grow such that less that #674800-677899-maxcachesizemb10% of total disk space is available. The maximum value is 80. The cache will not grow beyond 20% of the total available disk space. This method for determining the maximum size of the cache is provided as an alternative to MaxCacheSizeMB:

PermittedLSZShares

SMSPKG*$

SMS_DP_SMSPKG*$

A list of comma-separated package source locations. Enables increased security and is only used by the Nomad client installed on a distribution point. Nomad LSZ file generation requests will only be completed if the content location is listed. If you are using additional package source locations, you must manually add these to this registry value.

PermittedLSZShares can incorporate wildcard characters to provide flexible naming convention support.

If you leave the registry value blank, security checks on package source locations are not carried out.

RunUncachedPermittedFastLAN

0

Works in conjunction with MaxPackageSizeFastLAN (which needs to contain a value value greater than zero). Values are:

To ensure that the un-cached mode works correctly, set the Program Environment Properties to include the Drive mode/Require drive letter option.

PlatformURL

(empty)

Located under the following registry keys, depending on the component.

To enable SSD when you install Nomad, you must specify the MODULE.NOMAD.SSDENABLED installer property and ensure the Tachyon client is enabled by specifying SWITCH and BACKGROUNDCHANNELURL installer properties. If MODULE.NOMAD.SSDENABLED is specified during installation, the registry value of ContentRegistration is automatically set to 1.

If you want to enable SSD as a provider after installation, then you also need to configure the registry values for SSDEnabled and ContentRegistration, in addition to enabling the Tachyon client. The ContentDistribution registry setting is found under the Platform key.

In legacy versions of Nomad, Platform features were provided using ActiveEfficiency. This required the PlatformURL setting to be configured. This is no longer required. You will see that the PlatformURL registry is used, but this is configured automatically by Nomad on startup by querying the value that the Tachyon client is using (stored in the 1EClient.conf file).

PostCompleteTimeoutHours

0xA8 (168)

Only applies to a PBA share after the NMDS_COMPLETE command has been run for it, otherwise the PreCompleteTimeoutHours value will apply. The intention is that an incomplete share will only be available for a short period of time, defined in PreCompleteTimeoutHours.

Once the NMDS_COMPLETE command is sent, it will be fixed for this longer time. When the share is deleted the folder and associated user will be removed.

This registry value is found under the PBA registry key NomadBranch\NMDS.

PrecachePollBatchSize

20

Range is 1 to 500. If the value is greater than 500, it defaults to 500. If you set the value to 0, it defaults to 20.

PrecachePollMinutes

0x5A0 (1440)

Nomad clients normally start their polling cycle when the service starts-up, with a random delay to minimize the possibility of concurrent polls from different clients.

The range is 60 - 525600 (1 year). 0 disables polling

PreCompleteTimeoutHours

0x3 (3)

Located under the PBA registry key NomadBranch\NMDS, it only applies to a PBA share after the NMDS_POLL command has been run, but not the NMDS_COMPLETE command.

The intention is that an incomplete share will only be available for a short period of time. When the share is deleted the folder and associated user is removed.

RecycleDPDelay

600

It is associated with the distribution point resilience feature and is used in conjunction with DownloadTimeout. The default equates to 10 minutes.

RandomizeRemotePaths

REG_DWORD

0

By default, RandomizeRemotePaths is not present in the Nomad registry hive. To change the value, you need to create it and set your desired value.

You can enable and disable the remote paths randomization for either Configuration Manager (CM) or pre-cache jobs using the following bits:

SigsFolder

C:\SMSSIG$

Relates to RDC integration and must point to the folder where the signature files are held for Configuration Manager. Wildcards are not allowed. For example:

E:\SMSSIG$

When it is not set, Nomad assumes that signature files location as C:\SMSSIG$, if it exists.

SiteSsdStagger

REG_DWORD

0

Sets the site SSD query stagger duration in seconds. The stagger is 0 (disabled) by default.

The maximum value that can configured is 300 seconds (5 minutes).

There is no SSD staggering in WinPE.

Site SSD happens when broadcast is enabled or if local SSD is enabled and it does not return any devices from ActiveEfficiency.

This setting works in conjunction with LocalSsdStagger.

SiteSSDMinPackageSizeKB

REG_DWORD

0

The default value is 0 which can be changed after installation when it will be an installer property.

There is no lower limit for this key, upper limit is 10240. If the registry value is greater than 10240, the agent will only consider 10240 and will log a warning.

Size of content is first taken from Job data, if that's not available it's taken from the LST file, if it's not present there, this key is ignored and an SSD request is made irrespective of size.

SpecialNetShare

0x2060 (8288)

You can set more than one option at the same time by combining the bit values. For example, to have custom share permissions and use the machine account for access to the Nomad share, set the value for SpecialNetShare to 129 (decimal value 1+128 or 0x0081 hex). See The Nomad share for more detail on configuration and security.

The default value in different versions has changed, based on feedback. Upgrading does not change the value unless explicitly set.

The default used in all versions of Client Deployment Assistant (and earlier Endpoint Agent Installer) is 0x2070 (8304):

0x0000

0

No special features enabled.

0

0x0001

1

Custom Share Permissions: Administrators configure and manage custom share permissions. The service doesn't create the NomadSHR share on start-up, leaving the administrator to manually create it and set the permissions. It is also not deleted when the service stops and therefore existing share permissions are preserved.

1

0x0002

2

Enables support for IPv6: If the network supports both IPv6 and IPv4, enable support for both – set bit 1 but not bit 2.

2

0x0004

4

Disables support for IPv4: If the network supports only IPv6, disable IPv4 and set both bit 1 and bit 2.

3

0x0008

8

RESERVED

4

0x0010

16

The Nomad share is hidden and named NomadSHR$. When using a hidden share, all Nomad installations must be configured to use this option. See The Nomad share for more detail on configuration and security.

5

0x0020

32

Disables broadcast of download statistics. By default, this is disabled. If enabled, Nomad broadcasts download statistics to all peers when a download is complete.

6

0x0040

64

Enables Nomad FanOut.

7

0x0080

128

The machine account is used when connecting to a peer client. The SMSNomadP2P& account is not created. Please refer to The Nomad share: Use Machine Account.

8

0x0100

256

RESERVED

9

0x0200

512

RESERVED

10

0x0400

1024

RESERVED

11

0x0800

2048

RESERVED

12

0x1000

4096

RESERVED (deprecated)

13

0x2000

8192

Use HTTP/S or SMB. Ensure that this is set if Nomad integration is used by Tachyon. HTTP/S is automatically used if CM client is detected.

14

0x4000

16384

Web LSZ generation: enables the Nomad client on Configuration Manager standalone DPs to handle LSZ file generation requests coming from HTTP/HTTPS enabled clients.

Used when Nomad clients are configured with either of the following enabled:

When enabled, the Nomad distribution point client creates a virtual folder called LSZFILES. The permissions for this are copied from the Configuration Manager SMS_DP_SMSPKGX$ share. By default, access to the LSZFILES folder requires SSL to be enabled. This is the case for Internet facing scenarios where local client access certificates will ensure authentication. If you are using HTTP instead of HTTPS, manually disable SSL on the LSZFILES web folder in order for the Nomad LSZ file generation process to work.

Only needs to be enabled when using HTTP or HTTPS on standalone DPs; it is not required on site server DPs because Nomad automatically configures Web LSZ generation on them.

15

0x8000

32768

Use HTTP/S only, not SMB: enables the Nomad client to download content using HTTPS or HTTP depending on the content location provided by Configuration Manager or Tachyon. The Nomad client will not use SMB to download content when this is enabled.

SSDEnabled

0

You can set more than one option at the same time by combining the bit values. For example, to enable clients to fetch downloads using SSD and provide them to peers, set the value to 3 (decimal value 1+2 or 0x3).

To enable clients to fetch downloads using site and local SSD and provide them to peers, set the value to 7.

To enable SSD when you install Nomad, you must specify the MODULE.NOMAD.SSDENABLED installer property and ensure the Tachyon client is enabled by specifying SWITCH and BACKGROUNDCHANNELURL installer properties. If MODULE.NOMAD.SSDENABLED is specified during installation, the registry value of ContentRegistration is automatically set to 1.

If you want to enable SSD as a provider after installation, then you also need to configure the registry values for SSDEnabled and ContentRegistration, in addition to enabling the Tachyon client. The ContentDistribution registry setting is found under the Platform key.

In legacy versions of Nomad, Platform features were provided using ActiveEfficiency. This required the PlatformURL setting to be configured. This is no longer required. You will see that the PlatformURL registry is used, but this is configured automatically by Nomad on startup by querying the value that the Tachyon client is using (stored in the 1EClient.conf file).

If your network is running over a WLAN or have devices on a wireless network you want to be content providers, set ContentProviderOnWifi=1.

0x0

0

SSD is disabled, the Nomad client takes no part in the SSD on the site.

0

0x1

1

SSD is enabled and the Nomad client fetches downloads using SSD. This setting on its own (without provider mode set) should be used with sensitive server weighting. Provider mode is where a peer gets content from another peer but cannot serve it (it cannot act as a master).

1

0x2

2

SSD is enabled and the Nomad client provides downloads to peers. Enabling this bit causes Nomad to register content with Content Distribution. In practice, this is unlikely to be used on its own. This is automatically disabled for WinPE installations (because cached content is only temporary).

2

0x4

4

Local SSD is enabled and the Nomad client fetches downloads from a local client (also known as a subnet peer master - the term used for local devices which have content but cannot be located during the normal election process because network broadcasts have been disabled) within the subnet.

The local SSD feature was introduced to supplement site SSD for clients on networks such as wireless where broadcasts are disabled, to prevent each client becoming its own master and downloading direct from the DP. In a SSD enabled environment, a master queries Content Distribution to get a list of devices on other subnets within the site that have content. With local SSD enabled, the master also queries for devices having content within local subnet. If any local peers with content are available, then the master downloads from them, otherwise it attempts to download from Site peers (other subnets in the site), and if the master still cannot find any peers, it downloads the content direct from the DP.

In version 7.0 and later, a master skips using local SSD if it sees broadcast messages from peers. This means clients in mixed network environments can be configured with the same SSDEnabled setting (with Local SSD enabled) and clients can move seamlessly between networks. When on a wireless network (where broadcasts are typically disabled) local SSD can be used. On LAN networks (where broadcasts are typically allowed) local SSD would be skipped because a master is elected and sees broadcast activity from peers.

This setting should only be used if networks have broadcasts being disabled (for example wireless networks) and clients are forced to download from the DP as they can't participate in an election.

Local SSD requires that a peer on the local subnet be configured to provide downloads to peers, that is at least one client on the subnet must be configured with Bit 1 enabled. To maintain consistency with typical Nomad peer sharing behavior where local SSD is not required, configure all clients with SSDEnabled=7. You'll also want to set ContentProviderOnWifi=1.

When enabled, the elected master:

To distinguish between a master derived from Content Distribution and an election, the log records: Connection::SetDownloadSource = SubnetPeer (an elected peer) instead of Connection::SetDownloadSource = Peer (an SSD peer master).

SSPBAEnabled

0

Has a dependency on the Tachyon Platform PlatformURL. Values are:

StatusMsgEvents

0x0

Nomad can send status messages through Configuration Manager based on specific download events which appear in its deployment status. They are provided mainly for advanced troubleshooting purposes, or for custom reporting solutions. From v7.1 onwards, they are no longer required for the Nomad Dashboard which now gets its status events directly via the Platform Content Distribution feature. However, you may have custom reporting in Configuration Manger that also use these messages, and you can configure this setting accordingly for this purpose.

These messages are controlled by the StatusMsgEvents registry value. This is a REG_SZ string data type and the format of the parameter must be a 64-bit value. Status messages are only sent when there is an active deployment.

For example, to set the request started, request completed, started copy and master changed events, update the StatusMsgEvents registry value to 0x80002060.

For success reporting, this message provides feedback on the status of the download. For example, it can show how much data was received using multicast as opposed to peer-to-peer copying. Turning this message on creates an extra status message per machine for each deployment. The format of the status message is:

Evt_FinalStats MD100067 1 170 59195038 170 59195038 0 59195038 0 0

Configuration Manager status messages are made up of insertion strings. The strings for the final stats event are:

If the package is already cached and is re-deployed with an unchanged package version, the final stats message will not be re-sent.

SuccessCodes

0x206b, 0x2077, 0x103, 0xffffffff, 0x1, 0x70, 0x2050, 0x2051, 0x2052, 0x2053, 0x2054,0x2055, 0x2056, 0x2057, 0x2058, 0x205a, 0x205b, 0x205c, 0x205d, 0x205e, 0x2060, 0x2061,0x2062, 0x2063, 0x2064, 0x2065, 0x2066, 0x2067, 0x2068, 0x2069, 0x209A

This REG_SZ value contains a comma-delimited list of possible Nomad return codes that should be treated as a success and thereby prevent Configuration Manager from attempting to download the content itself or use another Alternate Content Provider (ACP). Any code returned by Nomad that is not on the list will be treated as a failure and trigger the Configuration Manager client to attempt to download the content using alternate means. Nomad also sends a status message to the Configuration Manager site containing its return code.

Strictly speaking the Nomad return codes are actually internal status codes, Nomad will only ever return success or failure to the Content Transfer Manager (CTM) component of the Configuration Manager client. When CTM receives a success it passes control to the ExecMgr component of the Configuration Manager client, which attempts to execute the deployment. ExecMgr will fail if Nomad did not download the content and make it available in the Configuration Manager cache. In this case, ExecMgr sends a status message (e.g. failed deployment) back to the Configuration Manager site.

If Nomad generates a return code that is not in the list, it passes a fail to the CTM component which causes the Configuration Manager client to try downloading the content itself using BITS, or use another Alternate Content Provider (ACP). This process may itself succeed or fail depending on the conditions that resulted in the original Nomad return code, and may have an undesirable impact on the network.

The following table shows the possible Nomad return codes that can be set in the list:

SupportWPAD

0

By default, the WPAD feature is disabled. To enable WPAD in Nomad, add registry key 'SupportWPAD' and set it to 1 at registry path HKLM/Software/1E/NomadBranch

To enable or disable the WPAD feature in Nomad:

EncryptionType

0x0 (0)

Value are:

WakeUpBatchSize

10

Sets the maximum number of machines to wake up in one call, for subnet and site separately. (So up to twice this number of requests is sent in total if WakeUp is enabled for both subnet and site.) The next batch is launched, if necessary, after a re-election (usually a periodic election).

The value cannot be greater than MaxDevicesFromAE, and hence itself cannot be more than 20.

WakeUpEnabled

0

Determines the status of the WakeUp integration. If configured by the installer, it is disabled (0) by default. If integration is enabled, Nomad attempts to wake up dormant hosts that are known to have the requested content in their caches. The integration has a dependency on the PlatformURL.

To enable integration post-installation, for normal usage, set both bits 0 and 1 (0x3)

0x0

0

Disables WakeUp integration.

0

0x1

1

Enables WakeUp integration only for the local subnet.

1

0x2

2

Enables WakeUp integration only for the site.

0x3

3

Enables WakeUp integration for the site and the local subnet.

WakeUpMinPackageSizeMB

1024

Any content below this size is downloaded from the DP as downloads from the DP for files this size will likely complete before any wakeups will have had a chance to finish. The value can be 0, in which case wakeups will always be attempted.

For example, if it is set to 512 and size of the content downloaded is 500 MB, a wake-up request (to site or subnet) is not be sent. Similarly, if size of the content is 600 MB, then wake-up requests (to site and subnet, determined by WakeupEnabled) is be sent.

WLanBlipSecs

0

The value must be 20 seconds or more.

WLanProfileList

A comma-delimited list of wireless SSIDs (* for any all) which enables Nomad to switch form wireless to a wired LAN connection when it becomes available.