-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Still breaking puppetlabs/registry #7
Comments
What system are you running on? |
Windows XP SP2 and SP3 On Dec 18, 2013, at 10:59 AM, Liam Bennett [email protected] wrote:
|
What fact are you seeing this error? Do you have puppetlabs/registry installed? |
Yea .. i have registry installed .. and it seems to happen if both are installed ( I saw the notes on previous tickets ) but I can't see a conflict. On Dec 18, 2013, at 12:25 PM, Liam Bennett [email protected] wrote:
|
Ok, apologies, yes I can see the bug now in the windows_sid fact. I will get this fixed shortly. If your interested it's this line: |
Danke ;) I am starting to write several windows based puppet modules myself .. cygwin most specifically ;) On Dec 18, 2013, at 12:40 PM, Liam Bennett [email protected] wrote:
|
That's great to hear. If you need any help, advice or guidance in doing that then I'm happy to help. You can always contact me on twitter @liamjbennett |
Also accepting feature requests as well as bugs ;) |
k .. you can find me as @sandinak ;) On Dec 18, 2013, at 12:44 PM, Liam Bennett [email protected] wrote:
|
Are you aware of any repo managers for windows + puppet? I've taken to creating /module/foo/install and putting installers in there and setting up shared mount .. etc. I am considering writing a tool to manage populating the install directories if people put source's in the module/manifests/init.pp .. kicking it around ;) On Dec 18, 2013, at 12:44 PM, Liam Bennett [email protected] wrote:
|
http://chocolatey.org/ and https://github.com/chocolatey/puppet-chocolatey is probably the nearest thing your after. I am in the process of writing a couple of providers to cover the network and http sources for when you don't have or don't want to have a chocolatey infrastructure. What your are doing now is still unfortunately a very common pattern. |
Hello, |
Bump on this issue as well |
Still seeing an issue, Windows Server 2008 R2 (64 bit). Any clue how to mitigate it? |
Bump, getting it here too. |
I was getting this error and found a fix that had nothing to do with win_facts. I was using the puppetlabs/registry module to change values without prefixing them with "32:" e.g. "32:HKLM\Softw..." Don't ask me WHY this fixed it (there is an answer but it goes completeley over my head) but it might be worth a try. |
+1 for dylanratcliffe1's answer... that solved my issue. Thanks. |
Error: Failed to apply catalog: Parameter path failed on Registry_value[HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\fDenyTSConnections]: Munging failed for value "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\fDenyTSConnections"
Wrapped exception:
Munging failed for value "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\fDenyTSConnections" in class path: uninitialized constant PuppetX::Puppetlabs::Registry::KEY_WOW64_64KEY
uninstall and things start working again.
The text was updated successfully, but these errors were encountered: