Ccmsetup.exe Not Installing

[Beronike Watkin]

Usethe CCMSetup.exe command to install the Configuration Manager client. If you provide client installation parameters on the command line, they modify the installation behavior. If you provide client installation properties on the command line, they modify the initial configuration of the installed client agent.

CCMSetup.exe provides command-line parameters to customize the installation. Parameters are prefixed with a slash (/) and are generally lower case. You specify the value of a parameter when necessary using a colon (:) immediately followed by the value. For more information, see CCMSetup.exe command-line parameters.

You can also supply properties at the CCMSetup.exe command line to modify the behavior of client.msi. Properties by convention are upper case. You specify a value for a property using an equal sign (=) immediately followed by the value. For more information, see Client.msi properties.

CCMSetup.exe and the supporting files are on the site server in the Client folder of the Configuration Manager installation folder. Configuration Manager shares this folder to the network under the site share. For example, \\SiteServer\SMS_ABC\Client.

If you extend the Active Directory schema for Configuration Manager, the site publishes many client installation properties in Active Directory Domain Services. The Configuration Manager client automatically reads these properties. For more information, see About client installation properties published to Active Directory Domain Services

Use this parameter to control the client's behavior on a metered network. This parameter takes no values. When you allow client communication on a metered network for ccmsetup, it downloads the content, registers with the site, and downloads the initial policy. Any further client communication follows the configuration of the client setting from that policy. For more information, see About client settings.

When using the /AlwaysExcludeUpgrade parameter, the auto upgrade still runs. However when CCMSetup runs to perform the upgrade, it will note that /AlwaysExcludeUpgrade parameter has been set and will log the following line in the ccmsetup.log:

To provide the correct file format, use the mobileclienttemplate.tcf file in the \bin\ folder in the Configuration Manager installation directory on the site server. This file has comments about the sections and how to use them. Specify the client installation properties in the [Client Install] section, after the following text: Install=INSTALL=ALL.

If CCMSetup fails to download the client installation files, this parameter specifies the maximum timeout in minutes. After this timeout, CCMSetup stops trying to download the installation files. The default value is 1440 minutes (one day).

Use this parameter to force the computer to restart if necessary to complete the installation. If you don't specify this parameter, CCMSetup exits when a restart is necessary. It then continues after the next manual restart.

Specifies a management point for clients to use to find the nearest distribution point for the client installation files. If there are no distribution points, or computers can't download the files from the distribution points after four hours, they download the files from the specified management point.

This parameter specifies an initial management point for computers to find a download source, and can be any management point in any site. It doesn't assign the client to the specified management point.

Computers download the files over an HTTP or HTTPS connection, depending on the site system role configuration for client connections. The download can also use BITS throttling if you configure it. If you configure all distribution points and management points for HTTPS client connections only, verify that the client computer has a valid client certificate.

You can use the /mp command-line parameter to specify more than one management point. If the computer fails to connect to the first one, it tries the next in the specified list. When you specify multiple management points, separate the values by semicolons.

If the client connects to a management point using HTTPS, specify the FQDN not the computer name. The value must match the management point PKI certificate's Subject or Subject Alternative Name. Although Configuration Manager supports using a computer name in the certificate for connections on the intranet, using an FQDN is recommended.

This parameter can also specify the URL of a cloud management gateway (CMG). Use this URL to install the client on an internet-based device. To get the value for this parameter, use the following steps:

The /mp command-line parameter doesn't specify the management point used by the Configuration Manager client once it is installed. To specify the initial management point used by the Configuration Manager client once it is installed, use the SMSMP client.msi property. To specify a list of management points for the Configuration Manager client to use once it is installed, use the SMSMPLIST client.msi property.

Specifies that a client shouldn't check the certificate revocation list (CRL) when it communicates over HTTPS with a PKI certificate. When you don't specify this parameter, the client checks the CRL before it establishes an HTTPS connection. For more information about client CRL checking, see Planning for PKI certificate revocation.

This parameter prevents CCMSetup from running as a service, which it does by default. When CCMSetup runs as a service, it runs in the context of the Local System account of the computer. This account might not have sufficient rights to access required network resources for the installation. With /noservice, CCMSetup.exe runs in the context of the user account that you use to start the installation.

Use this parameter to provide a bulk registration token. An internet-based device uses this token in the registration process through a cloud management gateway (CMG). For more information, see Token-based authentication for CMG.

If CCMSetup.exe fails to download installation files, use this parameter to specify the retry interval in minutes. CCMSetup continues to retry until it reaches the limit specified in the /downloadtimeout parameter.

Specifies the file download location. Use a local or UNC path. The device downloads files using the server message block (SMB) protocol. To use /source, the Windows user account for client installation needs Read permissions to the location.

Specify this parameter for the client to use a PKI client authentication certificate. If you don't include this parameter, or if the client can't find a valid certificate, it filters out all HTTPS management points, including cloud management gateways (CMG). The client uses an HTTP connection with a self-signed certificate.

If a device uses Microsoft Entra ID for client authentication and also has a PKI-based client authentication certificate, if you use include this parameter the client won't be able to get Microsoft Entra onboarding information from a cloud management gateway (CMG). For a client that uses Microsoft Entra authentication, don't specify this parameter, but include the AADRESOURCEURI and AADCLIENTAPPID properties.

In some scenarios, you don't have to specify this parameter, but still use a client certificate. For example, client push and software update-based client installation. Use this parameter when you manually install a client and use the /mp parameter with an HTTPS-enabled management point.

Also specify this parameter when you install a client for internet-only communication. Use CCMALWAYSINF=1 together with the properties for the internet-based management point (CCMHOSTNAME) and the site code (SMSSITECODE). For more information about internet-based client management, see Considerations for client communications from the internet or an untrusted forest.

Use this ccmsetup.msi property to pass additional command-line parameters and properties to ccmsetup.exe. Include other parameters and properties inside quotation marks ("). Use this property when you bootstrap the Configuration Manager client with the Intune MDM installation method.

Specifies the Microsoft Entra client app identifier. You create or import the client app when you configure Azure services for Cloud Management. An Azure administrator can get the value for this property from the Azure portal. For more information, see get application ID. For the AADCLIENTAPPID property, this application ID is for the Native application type.

Specifies the Microsoft Entra server app identifier. You create or import the server app when you configure Azure services for Cloud Management. When you create the server app, in the Create Server Application window, this property is the App ID URI.

An Azure administrator can get the value for this property from the Azure portal. In Microsoft Entra ID, find the server app under App registrations. Look for application type Web app / API. Open the app, select Settings, and then select Properties. Use the App ID URI value for this AADRESOURCEURI client installation property.

Specifies the Microsoft Entra tenant identifier. Configuration Manager links to this tenant when you configure Azure services for Cloud Management. To get the value for this property, use the following steps:

Specifies one or more Windows user accounts or groups to be given access to client settings and policies. This property is useful when you don't have local administrative credentials on the client computer. Specify a list of accounts that are separated by semicolons (;).

This value is a case-sensitive match for subject attributes that are in the root CA certificate. Separate attributes by a comma (,) or a semicolon (;). Specify more than one root CA certificate by using a separator bar ().

3a8082e126