https://www.puppet.com/community logo
Join Slack
Powered by
# windows
  • s
    This message was deleted.
    c
    r
    • 3
    • 7
  • a
    I have a Server 2019 clients connecting to Puppet 7 Master server, when it is running the PowerShell DCS modules it comes up with a "The network path was not found" error. This is NOT happening on Server 2022, the same GPOs are being applied to both 2019 and 2022 servers. Any ideas or suggestions on what could be causing this? Googling has not resulted in anything helpful
    Copy code
    Error: Exception calling "Contains" with "1" argument(s): "The network path was not found."
Error: /Stage[main]/win_localusers::Config/Dsc_group[Group1]/ensure: change from 'absent' to 'present' failed: Exception calling "Contains" with "1" argument(s): "The network path was not found."
Error: Exception calling "Contains" with "1" argument(s): "The network path was not found."
Error: /Stage[main]/win_localusers::Config/Dsc_group[group2]/ensure: change from 'absent' to 'present' failed: Exception calling "Contains" with "1" argument(s): "The network path was not found."
Error: Exception calling "Contains" with "1" argument(s): "The network path was not found."
Error: /Stage[main]/win_localusers::Config/Dsc_group[Group3]/ensure: change from 'absent' to 'present' failed: Exception calling "Contains" with "1" argument(s): "The network path was not found."
Error: Exception calling "Contains" with "1" argument(s): "The network path was not found."
Error: /Stage[main]/Soe_win_localusers::Config/Dsc_group[Group4]/ensure: change from 'absent' to 'present' failed: Exception calling "Contains" with "1" argument(s): "The network path was not found."
Error: Exception calling "Contains" with "1" argument(s): "The network path was not found."
Error: /Stage[main]/win_localusers::Config/Dsc_group[Group5]/ensure: change from 'absent' to 'present' failed: Exception calling "Contains" with "1" argument(s): "The network path was not found."
  • s
    This message was deleted.
    a
    r
    l
    • 4
    • 4
  • e
    The first runs on newly deployed windows hosts always exit status 6, but last_run_summary shoes no failures.. how can I tell why exit 6 is happening?
    Copy code
    events:
  failure: 0
  success: 573
  total: 573
  • j
    Hi, thoughts on Forge module for managing users in Active Directory server 2016. Either my Forge-Fu is off or such a thing isn't there? I find things for local users and actually creating AD, but can't find for users. Thanks, Jerry
    n
    • 2
    • 6
  • r
    Anyone managing Windows file shares? and on Puppet 8?
  • d
    Not on Puppet 8, but we've used the dsc smb share module. We haven't updated that part of our code in a few years so I can't speak for if it's maintained still or anything with newer features
  • r
    I've been using the karmafeast/windows_smb module, it definitly needs some love. Hasn't been touched since 2019. Works well currently but is going to be problematic in Puppet 8 because of deprecated functions (at least our CD4PE Impact Analysis jobs scream about them) Saw the xsmbshare dsc module, but it also hasn't been touched since 2019. Kind of thinking about trying to fix the karmafeast code
  • d
  • d
    Its somewhat challenging as the DSC community seems to have really slowed down and many powershell gallery modules are just not updating, were keeping a close eye what comes with DSC v3 https://github.com/MicrosoftDocs/PowerShell-Docs-DSC/blob/main/dsc/docs-conceptual/dsc-3.0/overview.md
    this 1
    r
    d
    • 3
    • 2
  • r
    Just FYI, I've attempted to modernize the windows_smb from karmafest so hopefully it'll work in Puppet 8 fine. Haven't been able to test it on 8 yet though. I'm pretty sure 99% of the issues were around unneeded deprecated functions. https://forge.puppet.com/modules/rychannel/windows_smb/readme
  • r
    Not sure if anyone used the velocity303-netbt module, but I saw it was scheduled for deprecation and have jumped ahead and forked it. https://forge.puppet.com/modules/rychannel/netbt
  • r
    Updated the dsc-networkingdsc module and now every run I get the following message "ensurable changed to false" on the dsc_dnsserveraddress resources... I'm not really sure what to do with it, anyone have any ideas?
    d
    • 2
    • 2
  • t
    @tkishel has left the channel
  • d
    hello, I wonder if I can reach out for a little guidance. I am trying to setup a Windows Failover Cluster using either of the Puppet Failover Cluster Powershell DSC modules (https://forge.puppet.com/modules/dsc/xfailovercluster/reference#dsc_xcluster or https://forge.puppet.com/modules/dsc/failoverclusterdsc/readme) unfortunately, I have really been struggling to get it to setup a NEW cluster (all I get is “I cant find your cluster”) Has anyone used the Puppet DSC modules for Windows Failover clustering and could share some words/code-of-wisdom? I’ve been banging my head against a wall for a few days on this 🙂
    Copy code
    dsc_xcluster { 'cluster01':
      dsc_name                          => 'cluster01',
      dsc_staticipaddress               => '172.100.1.77/24',
      dsc_ignorenetwork                 => ['10.0.2.0/24'],
      dsc_domainadministratorcredential => {
        user          => 'sql_cluster_admin',
        password => Sensitive('password'),
      },
    }
    TIA! Rob Thread in Slack Conversation
    d
    • 2
    • 3
  • j
    Hi, we have a custom fact created to gather the drive space on Windows systems and on most nodes it works fine. For a few I'm getting the following: 
    Error while resolving custom fact fact='win_storage_pws', resolution='<anonymous>': Failed while executing 'C:\Windows\system32\powershell -command "Get-CimInstance -Classname win32_logicaldisk | ConvertTo-Json"': Permission denied - C:\Windows\system32\powershell -command "Get-CimInstance -Classname win32_logicaldisk | ConvertTo-Json"
    Source: Facter After researching, I've seen a couple of the nodes that also display this error, but they already created the fact. It runs fine as admin in PowerShell when on the node itself. Any thoughts appreciated.
    r
    l
    • 3
    • 3
  • n
    super long shot, but does anyone have 
    DnsServerDsc
    raked into puppet types from the badold method of getting Dsc into puppet?
  • d
    You can use dsc_lite at the same time as old dsc. That’s how we got around having to rebuild for new dsc modules
  • r
    Anyone ever have DSC resources be SUPER slow... like 23+ seconds per resource
    😮 1
    d
    r
    k
    • 4
    • 8
  • r
    So bizarre, we have two servers that if they run DSC resources, they take forever, to the point of the agent run timing out. But if it runs in debug mode... its fine
  • r
    ACtually the debug comment isn't as accurate as I thought
  • d
    Worth running with the full times to see which dsc resource takes the extra time rather than just debug.
  • d
    --evaltrace
  • a
    Hello, Do you know who is having a look on the https://github.com/puppetlabs/Puppet.Dsc ? We created to 2 issues but we don't really know if it's in the proper 'section' 🙂 thanks for your feedback
    d
    • 2
    • 2
  • a
    Hello, i created a new issue to ask for a release of the dsc xPSDesiredStateConfiguration module to Puppet.DSC : https://github.com/puppetlabs/Puppet.Dsc/issues/302 Thanks a lot for your help
    s
    • 2
    • 3
  • l
    A heads up regarding pe_patch: I'm just after noticing that parts of ${env:PROGRAMDATA}\PuppetLabs\pe_patch belongs only to user SYSTEM whereas an agent run wants write-access at least to pe_fact_generation.ps1 inside that folder, so if you enable Puppet Enterprise Patching (even only for looking at missing patches, not actual patching), you lose the ability to run the agent as a "regular" administrative user.
    👍 1
  • c
    @CVQuesty has left the channel
  • s
    @spp has left the channel
  • w
    Hello, We currently have an issue with the DSC modules
    Copy code
    Could not autoload puppet/type/dsc_computer: Could not autoload puppet/provider/dsc_computer/dsc_computer: no such file to load -- puppet/provider/dsc_base_provider/dsc_base_provider
    https://github.com/puppetlabs/Puppet.Dsc/issues/299 We have proposed this PR https://github.com/puppetlabs/Puppet.Dsc/pull/308 Do you think it's a valid approach ? Thank you for your feedback
    👍 1
    c
    • 2
    • 6
  • v
    @vchepkov has left the channel