Using Puppet on Windows workstations can be a challenge. The different architectures (x86 and x86_64) can have an impact on declaring packages. I have decided to ignore 32 bit systems and treat all as 64 bit – after all, it is 2016 and 32 bit should not be deployed.
\n<\/p>\n
Since everything is stored in the registry (and I am no registry expert), I find myself first making a change in the GPO, searching for the change in the registry, and converting what I found to Puppet manifests. There are a few modules that also help with local policy settings.<\/p>\n
I have my Windows workstations checking in to Puppet every hour as it is not critical for them to be in-sync as often as multi-user servers.<\/p>\n
I have found PuppetDB to be a great alternative to inventory software. The modules to get it in that state are:<\/p>\n
ody\/pkginventory<\/a> (using my pull request for Windows support) Several other modules help Windows become easier to manage – they are:<\/p>\n puppetlabs\/<\/span>registry<\/a>
\njhaals\/<\/span>warranty<\/a><\/p>\n
\nchocolatey\/chocolatey<\/a>
\npuppetlabs\/powershell<\/a>
\nayohrling\/local_security_policy<\/a>
\nhttps:\/\/github.com\/Puppet-Finland\/local_group_policy<\/a><\/p>\n