SuccessCodes

A list of Content Distribution return codes that are translated as success to the Content Transfer Manager (CTM) component of the Configuration Manager client.

Registry value	Default	Notes	Installer property
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 Content Distribution 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 Content Distribution 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.Content Distribution also sends a status message to the Configuration Manager site containing its return code. Strictly speaking the Content Distribution return codes are actually internal status codes, Content Distribution 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 Content Distribution 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 Content Distribution 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 Content Distribution return code, and may have an undesirable impact on the network. 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". 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 Content Distribution return codes that can be set in the list: This list is subject to change with each release of Nomad, and provided for reference only.	MODULE.NOMAD.SUCCESSCODES

Registry value

Default

Notes

Installer property

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 Content Distribution 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 Content Distribution 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.Content Distribution also sends a status message to the Configuration Manager site containing its return code.

Strictly speaking the Content Distribution return codes are actually internal status codes, Content Distribution 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 Content Distribution 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 Content Distribution 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 Content Distribution return code, and may have an undesirable impact on the network.

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

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 Content Distribution return codes that can be set in the list:

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

MODULE.NOMAD.SUCCESSCODES

Return Code	Description
‭-1‬‬	0xFFFFFFFF	Reserved.
1	0x0001	Reserved.
112	0x0070	Insufficient disk space to create the cache.
259	0x0103	Reserved.
8272	0x2050	The download has been suspended by APM.
8273	0x2051	The user has canceled this download.
8274	0x2052	Invalid command line.
8275	0x2053	Command-line execution failure.
8276	0x2054	Internal Error.
8277	0x2055	The package exceeds the threshold for a RAS connection.
8278	0x2056	The package exceeds the threshold for a Slow LAN connection.
8279	0x2057	The package exceeds the threshold for a Fast LAN connection.
8280	0x2058	Reserved.
8281	0x2059	Unknown transport. Returned when an attempt is made to download a Software Update from an Internet location (like Microsoft Updates).
8282	0x205A	Invalid special package path (set using --pp).
8283	0x205B	Incorrect file hash.
8284	0x205C	Exited due to a kill request.
8285	0x205D	DP path not found.
8286	0x205E	The MaxBusyBackOff consecutive event threshold has been exceeded.
8287	0x205F	The service has stopped.
8288	0x2060	The advertisement has expired.
8289	0x2061	Reserved.
8290	0x2062	This is an unlicensed version of Content Distribution.
8291	0x2063	Invalid alternate cache path (set using --cp).
8292	0x2064	No Configuration Manager job data found in WMI.
8293	0x2065	Incorrect package hash.
8294	0x2066	MaxDuration or execution runtime for this program has been exceeded.
8295	0x2067	Reserved.
8296	0x2068	Incorrect package version.
8297	0x2069	Obsolete package version.
8298	0x206A	The BlockSize has been changed during download.
8299	0x206B	The "no progress" re-check threshold has been exceeded.
8300	0x206C	The parent process has terminated.
8301	0x206D	Duplicate download for the package.
8302	0x206E	The service was reset. This will occur if certain configuration parameters are changed during a download e.g. NomadInhibitedSubnets
8303	0x206F	Nomad inhibited.
8311	0x2077	Internal error LST incomplete.
8346	0x209A	Client certificate missing. Content Distribution is configured to use certificate-based client authentication but was unable to find an appropriate certificate.