Skip to content

Update about-client-installation-properties.md #4627

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update about-client-installation-properties.md #4627

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 14 additions & 12 deletions memdocs/configmgr/core/clients/deploy/about-client-installation-properties.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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).<!-- MEMDocs#1996 -->

### `/UPGRADETOLATEST`

<!-- Intune 13745717 -->

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`

## <a name="ccmsetupReturnCodes"></a> 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.
Expand Down Expand Up @@ -825,18 +839,6 @@ This property specifies a Configuration Manager site to which you assign the cli

Example: `CCMSetup.exe SMSSITECODE=XZY`

### `UPGRADETOLATEST`

<!-- Intune 13745717 -->

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.

## <a name="BKMK_attributevalues"></a> Attribute values for certificate selection criteria

Configuration Manager supports the following attribute values for the PKI certificate selection criteria:
Expand Down