Rediger

Del via


About client installation properties published to Active Directory Domain Services

Applies to: Configuration Manager (current branch)

When you extend the Active Directory schema for Configuration Manager, and the site is published to Active Directory Domain Services, many client installation properties are published to Active Directory Domain Services. If a computer can locate these client installation properties, it can use them during Configuration Manager client deployment.

The advantages of using Active Directory Domain Services to publish client installation properties include the following:

  • Software update point-based client installations and Group Policy client installations do not require setup parameters to be set up on each computer.

  • Because this information is automatically generated, the risk of human error associated with manually entering installation properties is eliminated.

Note

For more information about how to extend the Active Directory schema for Configuration Manager, and how to publish a site, see Schema extensions for Configuration Manager.

Client installation properties published to Active Directory Domain Services

The following is a list of client installation properties. For more information about each item listed below, see About client installation properties.

  • The Configuration Manager site code.

  • The site server signing certificate.

  • The trusted root key.

  • The client communication ports for HTTP and HTTPS.

  • The fallback status point. If the site has multiple fallback status points, only the first one that was installed is published to Active Directory Domain Services.

  • A setting to indicate that the client must communicate by using HTTPS only.

  • Settings related to PKI certificates:

    • Whether to use a client PKI certificate.

    • The selection criteria for certificate selection. This may be required because the client has more than one valid PKI certificate that can be used for Configuration Manager.

    • A setting to determine which certificate to use if the client has multiple valid certificates after the certificate selection process.

    • The certificate issuers list that contains a list of trusted root CA certificates.

  • Client.msi installation properties that are specified in the Client tab of the Client Push Installation Properties dialog box.

Client installation (CCMSetup) uses the properties that are published to Active Directory Domain Services only if no other properties are specified by using either of the following:

  • The manual installation method (described later in this article)

  • The Group Policy installation method (described later in this article)

Note

The client installation properties are used to install the client. These properties might be overwritten with new settings from its assigned site after the client is installed and has successfully been assigned to a Configuration Manager site.

Use the details in the following sections to determine which Configuration Manager client installation methods use Active Directory Domain Services to obtain client installation properties.

Client push installation

Client push installation does not use Active Directory Domain Services to obtain installation properties.

Instead, you can specify client installation properties in the Installation Properties tab of the Client Push Installation Properties dialog box. These options and client-related site settings are stored in a file that the client reads during client installation.

Note

You do not have to specify any CCMSetup properties for client push installation, or the fallback status point, or the trusted root key in the Installation Properties tab. These settings are automatically supplied to clients when they are installed by using client push installation. In addition to Client.msi properties, CCMSetup supports the following parameters: /forcereboot, /skipprereq, /logon, /BITSPriority, /downloadtimeout, /forceinstall

Any properties that you specify in the Installation Properties tab are published to Active Directory Domain Services if the site is published to Active Directory Domain Services. These settings are read by client installations where CCMSetup is run with no installation properties.

Software update point-based installation

The software update point-based installation method does not support the addition of installation properties to the CCMSetup command line.

If no command line properties have been provisioned on the client computer by using Group Policy, CCMSetup searches Active Directory Domain Services for installation properties.

Group Policy installation

The Group Policy installation method does not support the addition of installation properties to the CCMSetup command line.

If no command line properties have been provisioned on the client computer, CCMSetup searches Active Directory Domain Services for installation properties.

Manual installation

CCMSetup searches Active Directory Domain Services for installation properties under the following circumstances:

  • No command line properties are specified after the CCMSetup.exe command.

  • The computer has not been provisioned with installation properties by using Group Policy.

Logon script installation

CCMSetup searches Active Directory Domain Services for installation properties under the following circumstances:

  • No command line properties are specified after the CCMSetup.exe command.

  • The computer has not been provisioned with installation properties by using Group Policy.

Software distribution installation

CCMSetup searches Active Directory Domain Services for installation properties under the following circumstances:

  • No command line properties are specified after the CCMSetup.exe command.

  • The computer has not been provisioned with installation properties by using Group Policy.

Installations for clients that cannot access Active Directory Domain Services

These client computers cannot read or access the published installation properties from Active Directory Domain Services.

These clients include:

  • Workgroup computers.

  • Clients that are assigned to a Configuration Manager site that is not published to Active Directory Domain Services.

  • Clients that are installed when they are on the Internet.