Content Distribution client settings

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

• 0 – Everyone built-in security group and the SMSNomadP2P& Nomad share account. This is the least restrictive option and is not valid with HTTP or HTTPS protocol and is treated as 2 (only the SMSNomadP2P& Nomad share account)

• 1 – Authenticated Users built-in security group and the SMSNomadP2P& Nomad share account

• 2 – Only the SMSNomadP2P& Nomad share account. This account has also been added to NTFS permission settings.

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.

MODULE.NOMAD.BLOCKSIZE

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

• The default block size is 128KB

• The maximum block size is 4MB

• Multicast environments can only use the default block size. If you define a larger value for multicast environments, Nomad automatically resets it to the default.

• Clients use the block size defined in the registry and ignore the values from the LSZ

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.

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.

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

• The LocalCachePath REG_SZ registry value under the HKLM\Software\1E\NomadBranch key sets the path to the local Nomad package cache.

• The LocalCachePath REG_SZ registry value under the HKLM\Software\1E\NomadBranch\NMDS key sets the path to the PBA package cache.

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:

• the LSZFILES folder is incorrectly created (LocalCachePathLSZFILES instead of LocalCachePath\LSZFILES)

• IIS vDIR points to wrong folder (LocalCachePathLSZFILES instead of LocalCachePath\LSZFILES)

• LSZGEN fails because it is attempting to store LSZ files to non-existent path (LocalCachePath\LSZFILES)

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.

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.

Range: from 60 to 525600 (1Year).

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:

• Common sub-string (e.g. "CORPCA" would work for certificates issued by CORPCA1 or CORPCA2)

• Comma-separated list of certificate issuers (both exact names or substrings are acceptable values). For example, "DigiCert,Thawte,Verisign" would work for certificates issued by DigiCert, DigiCert EV, Thawte or Verisign.

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.

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:

• case-insensitive

• a substring search is done, so if the text is set to ACME it will return certificates where ACME appears anywhere in the certificate's subject.

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

• Common sub-string, for example "contoso.com" would work for certificates that have contoso.com anywhere in the subject name

• Comma-separated list of subject names or sub-strings, for example, you can specify multiple subject domain suffixes, for example "contoso.com,abc.in".

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

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.

Note

This is a new setting in 1E Client 5.1 (Nomad 7.0.200).

Values are:

• 0 – Only devices connected to a LAN can be content providers

• 1 – Devices connected to any network (including WLANs) can be content providers

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 1E 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 1E client. The ContentDistribution registry setting is found under the Platform key.

• Content Distribution app provides visibility of content distribution activity

• Single Site Download (SSD)

• Single Site Peer Backup Assistant - SSPBA (SSPBA)

• Get Migration Settings taskHigh sequence action used to manage computer associations

• Nomad Pre-caching

• Nomad Download Pause

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 1E client is using (stored in the 1EClient.conf file).

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

Enables monitoring of Delivery Optimization downloads and reporting them to 1E 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.

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).

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.

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:

• 0x205A – in valid special package path (set using --pp)

• 0x205D – DP path not found

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

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.

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:

• 0 disables this feature

• 1 enables this feature

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.

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.

Note

Please consult 1E before changing this value.

This setting works in conjunction with SiteSsdStagger.

Located under the PBA registry key NomadBranch\NMDS.

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.

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.

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

• If PercentAvailableDisk has a value greater than zero set its method will be used to control the cache size.

• If MaxCacheSizeMB is set to a value greater than zero and PercentAvailableDisk is set to zero then MaxCacheSizeMB will be used as the method for determining the maximum size of the Nomad cache.

Located under the PBA registry key NomadBranch\NMDS.

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.

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.

A non-zero value enables PBA share.

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

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.

Note

The default has been increased from 1048576 (1MB) to 5242880 (5MB) for Nomad 7.0 onwards (1E Client 4.1).

Note

The installer property name is different from the registry name.

Works in conjunction with the RunUncachedPermittedFastLAN registry value.

Note

The installer property name is different from the registry name.

Note

The installer property name is different from the registry name.

Note

The installer property name is different from the registry name.

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.

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

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.

Warning

The MaxStuckCount value is an internal NomadBranch registry value. You should not change this value unless advised by 1E.

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.

Values are:

• 0 – hard links are used. The Nomad cache will link to the Configuration Manager cache so only a single copy of a package is held locally.

• 1 – hard links are not used and results in the content being double-cached

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

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

• a local DP

• a VPN without isolation

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

site1,site2,site3

Please refer to Inhibiting subnets and sites.

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

• a local DP

• a VPN without isolation

For example, to isolate two subnets:

10.2.0.0/16,192.168.9.0/24

Please refer to Inhibiting subnets and sites.

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

Warning

The P2PDisqualifyMaxNumPeers value is an internal NomadBranch registry value. You should not change this value unless advised by 1E.

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

Warning

The P2PDisqualifyMaxWindowMins value is an internal NomadBranch registry value. You should not change this value unless advised by 1E.

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.

Note

We recommend restarting the Nomad Branch service when you modify this parameter.

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

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

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

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.

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

Note

If this option is enabled and the Configuration Manager client is using self-signed client authentication certificates (or Nomad is being used outside of CM), you should specify CertIssuer to ensure Nomad uses the intended certificate.

By default, the cache willnot exceed 10% of MaxCacheSizeMB 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:

• If PercentAvailableDisk is greater than zero, its method is used to control the cache size

• If MaxCacheSizeMB is greater than zero and PercentAvailableDisk is zero, then MaxCacheSizeMB is used as the method for determining the maximum size of the Nomad cache.

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.

Note

When Configuration Manager (specifically Distribution Point servers) is configured to use HTTPS only, you must also add NOCERT_SMS_DP_SMSPKG*$ and CCMTOKENAUTH_SMS_DP_SMSPKG*$ to the PermittedLSZShares registry value.

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

• 0 – do not run package from the distribution point.

• 1 – run package directly from the distribution point if there is either insufficient disk space to create the cache, or the maximum package threshold is exceeded but the connection is fast (>500kbps).

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

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

• For NomadBranch, it is found under HKLM\Software\1E\NomadBranch\Platform

• For NomadBranchAdminUIExt on 64-bit machines, it is found under HKLM\Software\Wow6432Node\1E\NomadAdminUI\Platform

• For NomadBranchAdminUIExt on 32-bit machines, it is found under HKLM\Software\1E\NomadAdminUI\Platform

Warning

Do not configure this registry setting, it is automatically configured on service startup.

To enable SSD when you install Nomad, you must specify the MODULE.NOMAD.SSDENABLED installer property and ensure the 1E 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 1E client. The ContentDistribution registry setting is found under the Platform key.

• Content Distribution app provides visibility of content distribution activity

• Single Site Download (SSD)

• Single Site Peer Backup Assistant - SSPBA (SSPBA)

• Get Migration Settings task sequence action used to manage computer associations

• Nomad Pre-caching

• Nomad Download Pause

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 1E client is using (stored in the 1EClient.conf file).

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.

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.

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

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.

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

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:

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.

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.

Note

Please consult 1E before changing this value.

This setting works in conjunction with LocalSsdStagger.

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.

Note

This check is for site SSD, not for local SSD.

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):

• Bit 4: Enable Nomad hidden share as NomadSHR$

• Bit 5: Disables broadcast of download statistics

• Bit 6: Enable Nomad FanOut

• Bit 13: Use HTTP/S or SMB

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 1E. The Nomad client will not use SMB to download content when this is enabled.

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 1E 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 1E client. The ContentDistribution registry setting is found under the Platform key.

• Content Distribution app provides visibility of content distribution activity

• Single Site Download (SSD)

• Single Site Peer Backup Assistant - SSPBA (SSPBA)

• Get Migration Settings task sequence action used to manage computer associations

• Nomad Pre-caching

• Nomad Download Pause

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 1E 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.

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:

1. Queries Content Distribution to get a list of local devices having the content.

2. Queries each of those devices to check if they are available and have the content. The list is ordered by percentage of content the device holds.

3. Repeats the same process for devices on other subnets (existing SSD feature).

4. Stores a list of subnets as well as site devices in memory.

5. Cycles through the list in the following order:

   1. Subnet peer master (fetched from list of local devices from Content Distribution)

   2. Site master

   3. DP.

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).

Has a dependency on the 1E Platform PlatformURL. Values are:

• 0 – disables single-site integration with ContentDistribution

• 1 – enables single-site integration with ContentDistribution

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.

Warning

Status message events should be used with caution as they could impact your Configuration Manager environment when scaled up to tens of thousands of machines.

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

• 0x0000000001 – SNO_EVT_START

• 0x0000000002 – SNO_EVT_STOP

• 0x0000000004 – SNO_EVT_ERROR

• 0x0000000008 – SNO_EVT_PAUSED

• 0x0000000010 – SNO_EVT_RESUMED

• 0x0000000020 – SNO_EVT_REQUEST_STARTED

• 0x0000000040 – SNO_EVT_REQUEST_COMPLETED

• 0x0000000080 – SNO_EVT_SERVICE_RESET

• 0x0000000100 – SNO_EVT_STARTED_CACHE_MANAGEMENT

• 0x0000000200 – SNO_EVT_FINISHED_CACHE_MANAGEMENT

• 0x0000000400 – SNO_EVT_STARTED_HASHCHECK

• 0x0000000800 – SNO_EVT_FINISHED_HASHCHECK

• 0x0000001000 – SNO_EVT_ELECTION_REQUEST

• 0x0000002000 – SNO_EVT_MASTER_CHANGED

• 0x0000004000 – SNO_EVT_FILLIN_MASTER_CHANGED

• 0x0000008000 – SNO_EVT_MCAST_CENTRALSCHED

• 0x0000010000 – SNO_EVT_MCAST_ERROR

• 0x0000020000 – SNO_EVT_MCAST_COMPLETE

• 0x0000040000 – SNO_EVT_SCHEDULER

• 0x0000080000 – SNO_EVT_STARTED_TX_CENTRALMCAST

• 0x0000100000 – SNO_EVT_STOPPED_TX_CENTRALMCAST

• 0x0000200000 – SNO_EVT_STARTED_TX_ACTIVEMCAST

• 0x0000400000 – SNO_EVT_STOPPED_TX_ACTIVEMCAST

• 0x0000800000 – SNO_EVT_STARTED_TX_FILLINMCAST

• 0x0001000000 – SNO_EVT_STOPPED_TX_FILLINMCAST

• 0x0002000000 – SNO_EVT_STARTED_RX_CENTRALMCAST

• 0x0004000000 – SNO_EVT_STOPPED_RX_CENTRALMCAST

• 0x0008000000 – SNO_EVT_STARTED_RX_ACTIVEMCAST

• 0x0010000000 – SNO_EVT_STOPPED_RX_ACTIVEMCAST

• 0x0020000000 – SNO_EVT_STARTED_RX_FILLINMCAST

• 0x0040000000 – SNO_EVT_STOPPED_RX_FILLINMCAST

• 0x0080000000 – SNO_EVT_STARTED_COPY

• 0x0100000000 – SNO_EVT_STOPPED_COPY

• 0x0200000000 – SNO_EVT_WORKRATE_CHANGED

• 0x0400000000 – SNO_EVT_WRONG_PKG_VERSION

• 0x0800000000 – SNO_EVT_INFORMATIONAL

• 0x1000000000 – SNO_EVT_FINALSTATS (see notes below)

• 0x2000000000 – SNO_EVT_WAIT

• 0x4000000000 – SNO_EVT_MAX_EVENTID

SNO_EVT_FINALSTATS notes

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.

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.

Note

The special code 0x9999 can be added to the list, or used on its own, to cause Nomad to always return a success to CTM. As a consequence this code is also known as "prevent failover to BITS".

Note

The SuccessCodes list need not be modified under normal circumstances, other than to add or remove the 0x9999 code.

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

Note

This list is subject to change with each release of Nomad, and provided for reference only.

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:

• Disable WPAD set SupportWPAD = 0

• Enable WPAD set SupportWPAD= 1 (or non-zero value).

Value are:

• 0 – standard Nomad encryption

• 1 – FIPS encryption

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.

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)

Enables WakeUp integration for the site and the local subnet.

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.

Note

For standalone downloads (using SMSNomad.exe) and under WinPE, there has no effect as the size of the content cannot easily be determined. Wake-up requests are always sent in these instances.

The value must be 20 seconds or more.