Jira (FACT-1356) External facts should be able to return structured data
Title: Message Title
Paul W commented on FACT-1356
Re: External facts should be able to return structured data
Is there an example on how this is working with a external PowerShell script?
Tried to put a foo.ps1 file in my module's facts.d folder:
$var = "bar"
Write-Host "{ `"foo`":`"$var`" }"
Running Facter in debug mode I receive the following messages:
DEBUG leatherman.execution:92 - executing command: C:\Windows\system32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive -NoLogo -ExecutionPolicy Bypass -File C:/ProgramData/PuppetLabs/puppet/cache/facts.d\foo.ps1
DEBUG | - { "foo":"bar" }
DEBUG puppetlabs.facter - ignoring line in output: { "foo":"bar" }
DEBUG leatherman.execution:688 - process exited with exit code 0.
DEBUG puppetlabs.facter - completed resolving facts from powershell script "C:/ProgramData/PuppetLabs/puppet/cache/facts.d\foo.ps1".
Jira (PUP-7326) Group resource (with auth_membership) failes if local Winows group contains not resolvable Domain accounts
Title: Message Title Paul W updated an issue Puppet / PUP-7326 Group resource (with auth_membership) failes if local Winows group contains not resolvable Domain accounts Change By: Paul W Environment: Tested with multiple Windows versions (i.e. Server 2012R2) and Puppet Apply 4.9.3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7326) Group resource (with auth_membership) failes if local Winows group contains not resolvable Domain accounts
Title: Message Title Paul W updated an issue Puppet / PUP-7326 Group resource (with auth_membership) failes if local Winows group contains not resolvable Domain accounts Change By: Paul W Environment: Tested with multiple Windows version versions and Puppet Apply 4.9.3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7326) Group resource (with auth_membership) failes if local Winows group contains not resolvable Domain accounts
Title: Message Title
Paul W updated an issue
Puppet / PUP-7326
Group resource (with auth_membership) failes if local Winows group contains not resolvable Domain accounts
Change By:
Paul W
After leaving a Domain Windows systems may still contain not resolvable domain accounts inside local groups, i.e. in *Administrators* group: !local_administrators_group_with_former_domain_object.png|thumbnail!When trying to manage this group using *auth_membership => true* (to ensure all not resolvable domain user accounts are tidied to only have the local user *Administrator* inside the local *Administrators* group), Puppet will fail:{code: ruby puppet }group {'Administrators': members => ['Administrator'], auth_membership => true }{code} Tested with the following Puppet Apply command: {code }puppet apply -e "group {'Administrators' : ruby members => ['Administrator'], auth_membership => true } {code}{code:puppet} Error: Could not resolve name: S-1-5-21-776561741-1409082233-725345543-15784Error: /Stage[main]/Main/Group[Administrators]/members: change from TEST-WIN2012\Administrator,S-1-5-21-776561741-1409082233-725345543-15784 to TEST-WIN2012\Administrator failed: Could not resolve name: S-1-5-21-776561741-1409082233-725345543-15784{code}!puppet_apply_example.png|thumbnail!
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To pos
Jira (PUP-7326) Group resource (with auth_membership) failes if local Winows group contains not resolvable Domain accounts
Title: Message Title
Paul W updated an issue
Puppet / PUP-7326
Group resource (with auth_membership) failes if local Winows group contains not resolvable Domain accounts
Change By:
Paul W
Summary:
Group resouce resource (with auth_membership) failes if local Winows group contains not resolvable Domain Accounts accounts
After leaving a Domain Windows systems may still contain not resolvable domain accounts inside local groups, i.e. in *Administrators* group: !local_administrators_group_with_former_domain_object.png|thumbnail!When trying to manage this group using *auth_membership => true* (to ensure all not resolvable domain user accounts are tidied to only have the local user *Administrator* inside the local *Administrators* group), Puppet will fail:{code:ruby}group {'Administrators': members => ['Administrator'], auth_membership => true }{code}{code:ruby}Error: Could not resolve name: S-1-5-21-776561741-1409082233-725345543-15784Error: /Stage[main]/Main/Group[Administrators]/members: change from TEST-WIN2012\Administrator,S-1-5-21-776561741-1409082233-725345543-15784 to TEST-WIN2012\Administrator failed: Could not resolve name: S-1-5-21-776561741-1409082233-725345543-15784{code} !puppet_apply_example.png|thumbnail!
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7326) Group resouce (with auth_membership) failes if local Winows group contains not resolvable Domain Accounts
Title: Message Title Paul W created an issue Puppet / PUP-7326 Group resouce (with auth_membership) failes if local Winows group contains not resolvable Domain Accounts Issue Type: Bug Affects Versions: PUP 4.9.3 Assignee: Unassigned Attachments: local_administrators_group_with_former_domain_object.png, puppet_apply_example.png Created: 2017/03/09 5:57 AM Environment: Tested with multiple Windows version and Puppet Apply 4.9.3 Labels: windows Priority: Normal Reporter: Paul W After leaving a Domain Windows systems may still contain not resolvable domain accounts inside local groups, i.e. in Administrators group: When trying to manage this grou
Jira (PUP-4917) puppet resource package does not display installs that use QuietDisplayName
Title: Message Title Paul W commented on PUP-4917 Re: puppet resource package does not display installs that use QuietDisplayName Tanks, Rob Reynolds. Keep working Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4917) puppet resource package does not display installs that use QuietDisplayName
Title: Message Title Paul W commented on PUP-4917 Re: puppet resource package does not display installs that use QuietDisplayName This should generally be pretty easy to add. apparently not? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3387) Enhance Windows Service Provider to handle dependent services
Title: Message Title Paul W commented on PUP-3387 Re: Enhance Windows Service Provider to handle dependent services Any news on this issue? Regards Paul Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4917) puppet resource package does not display McAfee Agent
Title: Message Title Paul W assigned an issue to Rob Reynolds Puppet / PUP-4917 puppet resource package does not display McAfee Agent Change By: Paul W Assignee: Paul W Rob Reynolds Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4917) puppet resource package does not display McAfee Agent
Title: Message Title
Paul W commented on PUP-4917
Re: puppet resource package does not display McAfee Agent
Okay, I figured out that this key is located here:
HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{1FDB8EC6-BAF1-42F9-8E09-4D9AB369F1B5}
However, your PowerShell script doesn't print it, because the DisplayName is empty. The String "McAfee Agent" is registered to the value QuietDisplayName. So, I extended your script to query for the QuietDisplayName as well:
$local_key = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key6432 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*'
Get-ItemProperty -Path @($machine_key6432,$machine_key, $local_key) -ErrorAction SilentlyContinue | ? { $_.DisplayName -like 'McAfee*' -or $_.QuietDisplayName -like 'McAfee*' } | % { Write-Host "$($_.DisplayName)|$($_.QuietDisplayName)|$($_.PSPath)" }
Output:
Jira (PUP-4917) puppet resource package does not display McAfee Agent
Title: Message Title
Paul W commented on PUP-4917
Re: puppet resource package does not display McAfee Agent
Thanks Rob Reynolds. Here is the output:
Windows Server 2012 R2
McAfee VirusScan Enterprise|Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{CE15D1B6-19B6-4D4D-8F43-CF5D2C3356FF}
Windows Server 2008 R2
McAfee VirusScan Enterprise|Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{CE15D1B6-19B6-4D4D-8F43-CF5D2C3356FF}
McAfee Agent|Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{DE91C193-2611-4BD3-A9F9-DF589C572565}
So, obviously there is no key for the McAfee Agent on Windows 2012.
When I'm querying the installed software with WMIC
wmic product where "Name like 'McAfee%'" get Name,Version,IdentifyingNumber
I'm getting this:
Windows Server 2012 R2
Jira (PUP-4917) puppet resource package does not display McAfee Agent
Title: Message Title Paul W created an issue Puppet / PUP-4917 puppet resource package does not display McAfee Agent Issue Type: Bug Affects Versions: puppet-agent 1.2.2, puppet-agent 1.2.1 Assignee: Unassigned Attachments: ProgramsAndFeaturesW2008.png, ProgramsAndFeaturesW2012.png Components: Windows Created: 2015/07/23 1:30 AM Environment: Operating System information provided by Facter: kernel => windows kernelmajversion => 6.3 kernelrelease => 6.3.9600
