On the HTTPS Pull Server, the MOF is located at "\\wpdscweb01.intra.xxxx.com\c$\Program Files\WindowsPowerShell\DscService\Configuration\" and is called "6247b8fa-d271-4c8b-8c04-e80ae7ad2008.mof"
On the Clients, then LCM has the following configurationID: "6247b8fa-d271-4c8b-8c04-e80ae7ad2008"
When I run "Start-DscConfiguration -Path "\\wpdscweb01.intra.xxxx.com\c$\Program Files\WindowsPowerShell\DscService\Configuration\" -wait -verbose -force, I get the following error:
VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, "methodName' = SendConfigurationApply,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' =
VERBOSE: Operation 'Invoke CimMethod' complete.
Does anyone know why the client is looking for a computer called "6247b8fa-d271-4c8b-8c04-e80ae7ad2008" and not applying the configuration to itself?
I've got past this error but now have a second 🙂
It seems that my nodes are all expecting a different checksum when I run "update-dscconfiguration":
VERBOSE: [WDLEGACYWEB02DE]:  Executing Get-Action with configuration 's checksum failed.
I am generating the mof and checksum by doing the following:
$source = "\\wpdscweb01.intra.xxxx.com\mofs\iisnodes\iisnodes.mof"
So, if the mof & checksum should be the smae for all nodes, how come each node is expecting a different checksum?
problem solved. I had to upade to the latest WMF: https://docs.microsoft.com/en-us/powershell/wmf/5.1/install-configure
*i feel like this forum is one giant echo chamber 🙂
You must be logged in to reply to this topic.