Process-portal-install.properties

Properties are global variables used by Windows Installer during an installation. Their values can be set by the operating environment or by authoring them into the installation database. There are two main types of Windows Installer properties:. The difference between Private and Public Properties consists in the way their values are being passed on.

The value of a Public Property is passed on from the Wizard Dialogs Stage in which the dialogs are showed to the Install Execution Stage in which the system is modified. Additionally, only Public Properties can be specified at the "msiexec" command line. Therefore, make sure that you use a Public Property for an UI control Editbox, Combobox etc if you want its value to be available in the InstallExecute Sequence for instance, if the value of this Property is written in the registry.

One very important group of properties are the Windows Installer predefined system Folders. Most properties used in an installation package created with Advanced Installer are Windows Installer Properties. However, some of them are custom and they are specific only to Advanced Installer:. Table of Contents. If not, review the log messages on disk. If necessary, you can share this information with Esri Support. If you installed Portal for ArcGIS on such a machine, you may want to identify the IP address or hostname the portal should use for network communication.

Perform these steps immediately after installation, prior to creating the initial administrative account and portal site. In some cases, such as when a host name is the same for multiple interfaces, you should instead specify the IP address of the interface you want ArcGIS Server to use for network communication.

When you upgrade your portal to a newer version, the upgrade will reset this hostidentifier. You must add the appropriate IP address back in after upgrading. Feedback on this topic? Back to Top. Note: If you're upgrading to Privacy policy. Use the CCMSetup. 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. The CCMSetup.

These files might include:. You specify the value of a parameter when necessary using a colon : immediately followed by the value. For more information, see CCMSetup.

You can also supply properties at the CCMSetup. Properties by convention are upper case. For more information, see Client. Configuration Manager shares this folder to the network under the site share. Specifies the management point named SMSMP01 to request a list of distribution points to download the client installation files.

Specifies that installation should stop if a version of the client already exists on the computer. 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.

Starting in version , 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. If you reinstall the client on an existing device, it uses the following priority to determine its configuration:. This parameter specifies whether or not a client will auto upgrade when you enable Automatic client upgrade.

For more information, see Extended interoperability client. When the device downloads client installation files over an HTTP connection, use this parameter to specify the download priority. Specify one of the following possible values:.

To provide the correct file format, use the mobileclienttemplate. This file has comments about the sections and how to use them. 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 minutes one day. Example: CCMSetup. 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. If any version of the client is already installed, this parameter specifies that the client installation should stop.

Specifies a source management point for computers to connect to. Computers use this management point to find the nearest distribution point for the 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. For more information on how ccmsetup downloads content, see Boundary groups - client installation.

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. 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.

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. Although Configuration Manager supports using a computer name in the certificate for connections on the intranet, using an FQDN is recommended.

Use this URL to install the client on an internet-based device. To get the value for this parameter, use the following steps:. Create a CMG. For more information, see Set up a CMG. Example for when you use the cloud management gateway URL: ccmsetup. This parameter prevents CCMSetup from running as a service, which it does by default. This account might not have sufficient rights to access required network resources for 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. If you're using a script to run CCMSetup. It might not correctly report installation details to the script.

This parameter specifies that CCMSetup. You can enter more than one value. Use the semicolon character ; to separate each value. For more information on client prerequisites, see Windows client prerequisites. Specifies the file download location. Use a local or UNC path.

The device downloads files using the server message block SMB protocol. Use this parameter to uninstall the Configuration Manager client. For more information, see Uninstall the client. Starting in version , when you uninstall the client it also removes the client bootstrap, ccmsetup. 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 Azure Active Directory Azure AD 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 Azure AD onboarding information from a cloud management gateway CMG. 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. Also specify this parameter when you install a client for internet-only communication. For more information about internet-based client management, see Considerations for client communications from the internet or an untrusted forest. Specify this parameter to manually upgrade an excluded client.

For more information, see How to exclude clients from upgrade. Use this ccmsetup.