diff --git a/memdocs/configmgr/core/clients/deploy/about-client-installation-properties.md b/memdocs/configmgr/core/clients/deploy/about-client-installation-properties.md index d5f397f6a4e..14b3b6f1e52 100644 --- a/memdocs/configmgr/core/clients/deploy/about-client-installation-properties.md +++ b/memdocs/configmgr/core/clients/deploy/about-client-installation-properties.md @@ -305,6 +305,20 @@ If a device uses Microsoft Entra ID for client authentication and also has a PKI Specify this parameter to manually upgrade an excluded client. For more information, see [How to exclude clients from upgrade](../manage/upgrade/exclude-clients-windows.md). +### `/UPGRADETOLATEST` + + + +This parameter forces CCMSetup to send a location request to the management point to get the latest version of the Configuration Manager client installation source. There are several scenarios where this is especially useful: + +- Pre-production clients. A newly installed client uses the production baseline because it can't evaluate the pre-production collection until the client is installed. In that scenario, after the client is installed and it evaluates policy, it will later upgrade to the pre-production client version. Use this property so that the device immediately installs the latest version of the client. + + This scenario also includes when using [Autopilot into co-management](../../../comanage/autopilot-enrollment.md). Use this parameter to make sure the newly provisioned Autopilot device uses the pre-production client version right away. + +- Pull distribution points. Allow pull distribution points to install the latest client version even if it's not in the pre-production collection. This action makes sure that the client version on the pull distribution point is the same as the distribution point binaries. If these versions aren't the same, it may cause issues. + + Example: `ccmsetup.exe /UPGRADETOLATEST` + ## CCMSetup.exe return codes The CCMSetup.exe command provides the following return codes. To troubleshoot, review `%WinDir%\ccmsetup\Logs\ccmsetup.log` on the client for context and additional detail about return codes. @@ -825,18 +839,6 @@ This property specifies a Configuration Manager site to which you assign the cli Example: `CCMSetup.exe SMSSITECODE=XZY` -### `UPGRADETOLATEST` - - - -This property forces CCMSetup to send a location request to the management point to get the latest version of the Configuration Manager client installation source. There are several scenarios where this property is especially useful: - -- Pre-production clients. A newly installed client uses the production baseline because it can't evaluate the pre-production collection until the client is installed. In that scenario, after the client is installed and it evaluates policy, it will later upgrade to the pre-production client version. Use this property so that the device immediately installs the latest version of the client. - - This scenario also includes when using [Autopilot into co-management](../../../comanage/autopilot-enrollment.md). Use this property to make sure the newly provisioned Autopilot device uses the pre-production client version right away. - -- Pull distribution points. Allow pull distribution points to install the latest client version even if it's not in the pre-production collection. This action makes sure that the client version on the pull distribution point is the same as the distribution point binaries. If these versions aren't the same, it may cause issues. - ## Attribute values for certificate selection criteria Configuration Manager supports the following attribute values for the PKI certificate selection criteria: