1E 23.7 (SaaS)

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:

MODULE.NOMAD.SUCCESSCODES

(This installer property was introduced in 1E Client 4.1 for Nomad 7.0)