Details of the scenario you tried and the problem that is occurring
I get an error trying to run the following:
(Invoke-DscResource -Name AccountPolicy -Method Get -Property @{Name ='notrequired'} -ModuleName SecurityPolicyDsc).Account_lockout_duration
This happens after the DSC is successfully applied to the machine. I am running the above command to test the DSC configuration...
Verbose logs showing the problem
==> azure-arm.dsc_node: The term 'secedit.exe' is not recognized as the name of a cmdlet, function, script file, or operable program. Check
==> azure-arm.dsc_node: the spelling of the name, or if a path was included, verify that the path is correct and try again.
==> azure-arm.dsc_node: + CategoryInfo : ObjectNotFound: (secedit.exe:) [], CimException
==> azure-arm.dsc_node: + FullyQualifiedErrorId : CommandNotFoundException
==> azure-arm.dsc_node: + PSComputerName : localhost
==> azure-arm.dsc_node:
==> azure-arm.dsc_node: The PowerShell DSC resource '[AccountPolicy]DirectResourceAccess' with SourceInfo '' threw one or more non-terminating
==> azure-arm.dsc_node: errors while running the Get-TargetResource functionality. These errors are logged to the ETW channel called
==> azure-arm.dsc_node: Microsoft-Windows-DSC/Operational. Refer to this channel for more details.
==> azure-arm.dsc_node: + CategoryInfo : InvalidOperation: (root/Microsoft/...gurationManager:String) [], CimException
==> azure-arm.dsc_node: + FullyQualifiedErrorId : NonTerminatingErrorFromProvider
==> azure-arm.dsc_node: + PSComputerName : localhost
Details of the scenario you tried and the problem that is occurring
I get an error trying to run the following:
(Invoke-DscResource -Name AccountPolicy -Method Get -Property @{Name ='notrequired'} -ModuleName SecurityPolicyDsc).Account_lockout_duration
This happens after the DSC is successfully applied to the machine. I am running the above command to test the DSC configuration...
Verbose logs showing the problem
Suggested solution to the issue
SecEdit.exe is available:
PS C:\Users\admintest> where.exe secedit.exe C:\Windows\System32\SecEdit.exe
The DSC configuration that is used to reproduce the issue (as detailed as possible)
The operating system the target node is running
Version and build of PowerShell the target node is running
Version of the DSC module that was used
2.1.0.0