PUPPET_MASTER_SERVER

Note: If you set a non-default value for this property, the installer replaces any existing value in puppet.conf. Also, the next time you upgrade, the installer re-uses your previous value for this property unless you set a new value on the command line. So if you’ve used this property once, you shouldn’t change the server setting directly in puppet.conf; you should re-run the installer and set a new value there instead.

PUPPET_CA_SERVER

The hostname where the CA Puppet master server can be reached, if you are using multiple masters and only one of them is acting as the CA. This sets a value for the ca_server setting in the [main] section of puppet.conf.

Default: the value of the PUPPET_MASTER_SERVER property

Note: If you set a non-default value for this property, the installer replace any existing value in puppet.conf. Also, the next time you upgrade, the installer re-uses your previous value for this property unless you set a new value on the command line. So if you’ve used this property once, you shouldn’t change the ca_server setting directly in puppet.conf; you should re-run the installer and set a new value there instead.

PUPPET_AGENT_CERTNAME

The node’s certificate name, and the name it uses when requesting catalogs. This sets a value for the certname setting in the [main] section of puppet.conf.

For best compatibility, you should limit the value of certname to only use lowercase letters, numbers, periods, underscores, and dashes. (That is, it should match /\A[a-z0-9._-]+\Z/.)

Note: If you set a non-default value for this property, the installer replaces any existing value in puppet.conf. Also, the next time you upgrade, the installer re-uses your previous value for this property unless you set a new value on the command line. So if you’ve used this property once, you shouldn’t change the certname setting directly in puppet.conf; you should re-run the installer and set a new value there instead.

PUPPET_AGENT_ENVIRONMENT

Note: If you set a non-default value for this property, the installer replaces any existing value in puppet.conf. Also, the next time you upgrade, the installer re-uses your previous value for this property unless you set a new value on the command line. So if you’ve used this property once, you shouldn’t change the environment setting directly in puppet.conf; you should re-run the installer and set a new value there instead.

PUPPET_AGENT_STARTUP_MODE

Whether the Puppet agent service should run (or be allowed to run). Allowed values:

Manual — Puppet agent won’t run by default, but can be started in the services console or with net start on the command line.

Disabled — Puppet agent is installed but disabled. You must change its startup type in the services console before you can start the service.

PUPPET_AGENT_ACCOUNT_USER

Which Windows user account the Puppet agent service should use. This is important if the Puppet agent needs to access files on UNC shares, since the default LocalSystem account cannot access these network resources.

This user account must already exist, and can be a local or domain user. (The installer allows domain users even if they haven’t accessed this machine before.)

If the user isn’t already a local administrator, the installer adds it to the Administrators group.

PUPPET_AGENT_ACCOUNT_DOMAIN

Downgrades

If you need to replace a 64-bit version of Puppet with a 32-bit version, you must uninstall Puppet before installing the new package. You must also uninstall if you are downgrading from 3.7 or later to 3.6 or earlier.

Uninstalling

You can uninstall Puppet through the “Add or Remove Programs” interface or from the command line.

To uninstall Puppet from the command line, you must have the original MSI file or know the ProductCode of the installed MSI:

When you uninstall Puppet, the uninstaller removes Puppet’s program directory, the Puppet agent service, and all related registry keys. It leaves the confdir, codedir, and vardir intact, including any SSL keys. To completely remove Puppet from the system, manually delete the confdir, codedir, and vardir.