• Overview
• Release notes
• Puppet platform documentation
• Quick start guides
• Managing Windows nodes
• Installing
• Migrating from 3.8
• Configuring PE
• Configuring high availability
• Monitoring infrastructure state
• Managing nodes
• Managing access
• Managing applications
• Enforcing change with Puppet orchestrator
• Managing and deploying Puppet code
• Provisioning with Razor
• SSL and certificates
• APIs
• Managing MCollective
• Maintenance
• Troubleshooting
• Appendix

## Troubleshooting Puppet on Windows

This version is out of date. For current versions, see Puppet Enterprise support lifecycle.
###### Sections

Puppet Enterprise supports Windows agents, for both the core Puppet configuration management features and the MCollective features.

Windows agents can have different problems and symptoms than *nix agents. This page outlines some of the more common issues and their solutions.

## Tips

### Process Explorer

We recommend installing Process Explorer and configuring it to replace Task Manager. This will make debugging significantly easier.

### Logging

Puppet agent on Windows logs messages to the Windows Event Log. You can view its logs by browsing the Event Viewer. (Control Panel → System and Security → Administrative Tools → Event Viewer) To enable debugging, stop the puppet service and restart it as:

c:\>sc stop puppet && sc start puppet --debug --trace


Puppet’s Windows service component also writes to the windows.log within the same log directory and can be used to debug issues with the service.

## Common issues

### Installation

The Puppet MSI package will not overwrite an existing entry in the puppet.conf file. As a result, if you uninstall the package, then reinstall the package using a different Puppet master hostname, Puppet won’t actually apply the new value if the previous value still exists in <data directory>\etc\puppet.conf.

In general, we’ve taken the approach of preserving configuration data on the system when doing an upgrade, uninstall or reinstall.

To fully clean out a system make sure to delete the <data directory>.

Similarly, the MSI will not overwrite the custom facts written to the PuppetLabs\facter\facts.d directory.

### Unattended installation

Puppet may fail to install when trying to perform an unattended install from the command line, e.g.

msiexec /qn /norestart /i puppet.msi


To get troubleshooting data, specify an installation log, e.g. /l*v install.txt. Look in the log for entries like the following:

MSI (s) (7C:D0) [17:24:15:870]: Rejecting product '{D07C45E2-A53E-4D7B-844F-F8F608AFF7C8}': Non-assigned apps are disabled for non-admin users.
MSI (s) (7C:D0) [17:24:15:870]: Note: 1: 1708
MSI (s) (7C:D0) [17:24:15:870]: Product: Puppet -- Installation failed.
MSI (s) (7C:D0) [17:24:15:870]: Windows Installer installed the product. Product Name: Puppet. Product Version: 2.7.12. Product Language: 1033. Manufacturer: Puppet Labs. Installation success or error status: 1625.
MSI (s) (7C:D0) [17:24:15:870]: MainEngineThread is returning 1625
MSI (s) (7C:08) [17:24:15:870]: No System Restore sequence number for this installation.
Info 1625.This installation is forbidden by system policy. Contact your system administrator.


If you see entries like this you know you don’t have sufficient privileges to install puppet. Make sure to launch cmd.exe with the Run as Administrator option selected, and try again.

## File paths

### Path separator

Make sure to use a semi-colon (;) as the path separator on Windows, e.g., modulepath=path1;path2

### File separator

In most resource attributes, the Puppet language accepts either forward- or backslashes as the file separator. However, some attributes absolutely require forward slashes, and some attributes absolutely require backslashes. See the relevant section of Writing manifests for Windows for more information.

### Backslashes

When backslashes are double-quoted(“), they must be escaped. When single-quoted (‘), they may be escaped. For example, these are valid file resources:

file { 'c:\path\to\file.txt': }
file { 'c:\\path\\to\\file.txt': }
file { "c:\\path\\to\\file.txt": }


But this is an invalid path, because \p, \t, \f will be interpreted as escape sequences:

file { "c:\path\to\file.txt": }


### UNC paths

UNC paths are not currently supported. However, the path can be mapped as a network drive and accessed that way.

### Case-insensitivity

Several resources are case-insensitive on Windows (file, user, group). When establishing dependencies among resources, make sure to specify the case consistently. Otherwise, Puppet may not be able to resolve dependencies correctly. For example, applying the following manifest will fail, because Puppet does not recognize that FOOBAR and foobar are the same user:

file { 'c:\foo\bar':
ensure => directory,
owner  => 'FOOBAR'
}
user { 'foobar':
ensure => present
}
...
err: /Stage[main]//File[c:\foo\bar]: Could not evaluate: Could not find user FOOBAR


### Diffs

Puppet does not show diffs on Windows (e.g., puppet agent --show_diff) unless a third-party diff utility has been installed (e.g., msys, gnudiff, cygwin, etc) and the diff property has been set appropriately.

## Resource errors and quirks

### File

If the owner and/or group are specified in a file resource on Windows, the mode must also be specified. So this is okay:

file { 'c:/path/to/file.bat':
ensure => present,
mode   => 0770
}


But this is not:

file { 'c:/path/to/file.bat':
ensure => present,
}


The latter case will remove any permissions the Administrators group previously had to the file, resulting in the effective permissions of 0700. And since Puppet runs as a service under the “SYSTEM” account, not “Administrator,” Puppet itself will not be able to manage the file the next time it runs!

To get out of this state, have Puppet execute the following (with an exec resource) to reset the file permissions:

takeown /f c:/path/to/file.bat && icacls c:/path/to/file.bat /reset


### Exec

When declaring a Windows exec resource, the path to the resource typically depends on the %WINDIR% environment variable. Since this may vary from system to system, you can use the path fact in the exec resource:

exec { 'cmd.exe /c echo hello world':
path => $::path }  ### Shell builtins Puppet does not currently support a shell provider on Windows, so executing shell builtins directly will fail: exec { 'echo foo': path => 'c:\windows\system32;c:\windows' } ... err: /Stage[main]//Exec[echo foo]/returns: change from notrun to 0 failed: Could not find command 'echo'  Instead, wrap the builtin in cmd.exe: exec { 'cmd.exe /c echo foo': path => 'c:\windows\system32;c:\windows' }  Or, better still, use the tip from above: exec { 'cmd.exe /c echo foo': path =>$::path
}


### Powershell

By default, powershell enforces a restricted execution policy which prevents the execution of scripts. Consequently, make sure to specify the appropriate execution policy in the powershell command:

exec { 'test':
command => 'powershell.exe -executionpolicy remotesigned -file C:\test.ps1',
path    => \$::path
}


### Package

The source of an MSI package must be a file on either a local filesystem or on a network mapped drive. It does not support URI-based sources, though you can achieve a similar result by defining a file whose source is the Puppet master and then defining a package whose source is the local file.

### Service

Windows services support a short name and a display name. Make sure to use the short name in Puppet manifests. For example use wuauserv, not Automatic Updates. You can use sc query to get a list of services and their various names.

## Error messages

• Error: Could not connect via HTTPS to https://forge.puppetlabs.com / Unable to verify the SSL certificate / The certificate may not be signed by a valid CA / The CA bundle included with OpenSSL may not be valid or up to date

This can occur when you run the puppet module subcommand on newly provisioned Windows nodes.

The Puppet Forge uses an SSL certificate signed by the GeoTrust Global CA certificate. Newly provisioned Windows nodes may not have that CA in their root CA store yet.

To resolve this and enable the puppet module subcommand on Windows nodes, do one of the following:

• Download the “GeoTrust Global CA” certificate from GeoTrust’s list of root certificates and manually install it by running certutil -addstore Root GeoTrust_Global_CA.pem.
• Service 'Puppet Agent' (puppet) failed to start. Verify that you have sufficient privileges to start system services.

This can occur when installing Puppet on a UAC system from a non-elevated account. Although the installer displays the UAC prompt to install puppet, it does not elevate when trying to start the service. Make sure to run from an elevated cmd.exe process when installing the MSI.

• Cannot run on Microsoft Windows without the sys-admin, win32-process, win32-dir, win32-service and win32-taskscheduler gems.

Puppet requires the indicated Windows-specific gems, which can be installed using gem install <gem>

• err: /Stage[main]//Scheduled_task[task_system]: Could not evaluate: The operation completed successfully.

This error can occur when using version < 0.2.1 of the win32-taskscheduler gem. Run gem update win32-taskscheduler

• err: /Stage[main]//Exec[C:/tmp/foo.exe]/returns: change from notrun to 0 failed: CreateProcess() failed: Access is denied.

This error can occur when requesting an executable from a remote Puppet master that cannot be executed. For a file to be executable on Windows, set the user/group executable bits accordingly on the Puppet master (or alternatively, specify the mode of the file as it should exist on the Windows host):

  file { "C:/tmp/foo.exe":
source => "puppet:///modules/foo/foo.exe",
}

exec { 'C:/tmp/foo.exe':
logoutput => true
}

• err: getaddrinfo: The storage control blocks were destroyed.

This error can occur when the agent cannot resolve a DNS name into an IP address (for example the server, ca_server, etc properties). To verify that there is a DNS issue, check that you can run nslookup <dns>. If this fails, there is a problem with the DNS settings on the Windows agent (for example, the primary dns suffix is not set). See http://technet.microsoft.com/en-us/library/cc959322.aspx

• err: /Stage[main]//Package[7zip]/ensure: change from absent to present failed: Execution of 'msiexec.exe /qn /norestart /i "c:\\7z920.exe"' returned 1620: T h i s i n s t a l l a t i o n p a c k a g e c o u l d n o t b e o p e n e d . C o n t a c t t h e a p p l i c a t i o n v e n d o r t o v e r i f y t h a t t h i s i s a v a l i d W i n d o w s I n s t a l l e r p a c k a g e .

This error can occur when attempting to install a non-MSI package. Puppet only supports MSI packages. To install non-MSI packages, use an exec resource with an onlyif parameter.

• err: Could not request certificate: The certificate retrieved from the master does not match the agent's private key.

This error is usually a sign that the master has already issued a certificate to the agent. This can occur if the agent’s SSL directory is deleted after it has retrieved a certificate from the master, or when running the agent in two different security contexts. For example, running Puppet agent as a service and then trying to run puppet agent from the command line with non-elevated security. Specifically, this would happen if you’ve selected Start Command Prompt with Puppet but did not elevate privileges using Run as Administrator.

• err: Could not send report: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed. This is often because the time is out of sync on the server or client.

Windows agents that are part of an Active Directory domain should automatically have their time synchronized with AD. For agents that are not part of an AD domain, you may need to enable and add the Windows time service manually:

  w32tm /register
net start w32time
w32tm /config /manualpeerlist:<ntpserver> /syncfromflags:manual /update
w32tm /resync

• err: You cannot service a running 64-bit operating system with a 32-bit version of DISM. Please use the version of DISM that corresponds to your computer's architecture.

If you’ve installed Puppet Enterprise on a 64-bit Windows system using the 32-bit installer, you may end up accessing a wrong or unexpected version of an executable due to file system redirection. For more info, see the Puppet documentation about handling file paths on Windows.

In the case of this error message, Puppet accessed c:\windows\SysWOW64\dism.exe when it was attempting to access c:\windows\system32\dism.exe.

• “Error: Could not parse for environment production: Syntax error at ‘=’; expected ‘}’”

This error will usually occur if puppet apply -e is used from the command line and the supplied command is surrounded with single quotes (‘), which will cause cmd.exe to interpret any => in the command as a redirect. To solve this surround the command with double quotes (“) instead.

See an issue? Please file a JIRA ticket in our [DOCUMENTATION] project
Puppet sites use proprietary and third-party cookies. By using our sites, you agree to our cookie policy.