You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An attempt to test WindowsCapability resource fails.
Details of the scenario you tried and the problem that is occurring
Trying to handle capability resource 'SNMP.Client~~~~0.0.1.0' via following script:
WindowsCapability SNMP {
Name = 'SNMP.Client~~~~0.0.1.0'
Ensure = 'Present'
}
Verbose logs showing the problem
VERBOSE: An LCM method call arrived from computer COMP-XYZ with user sid S-1-5-21-xyz.
VERBOSE: [COMP-XYZ]: LCM: [ Start Compare ]
VERBOSE: [COMP-XYZ]: LCM: [ Start Resource ] [[WindowsCapability]SNMP::[WindowsFeatures]DefaultOSFeatures]
VERBOSE: [COMP-XYZ]: LCM: [ Start Test ] [[WindowsCapability]SNMP::[WindowsFeatures]DefaultOSFeatures]
VERBOSE: [COMP-XYZ]: [[WindowsCapability]SNMP::[WindowsFeatures]DefaultOSFeatures] Begin executing Test functionality on Windows Capability
'SNMP.Client~~~~0.0.1.0'.
A parameter cannot be found that matches parameter name 'Ensure'.
+ CategoryInfo : InvalidArgument: (:) [], CimException
+ FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.Dism.Commands.GetWindowsCapabilityCommand
PowerShell Desired State Configuration does not support execution of commands in an interactive mode. Please ensure that the underlying command is not prompting for user
input, such as missing mandatory parameter, confirmation prompt etc.
+ CategoryInfo : OperationStopped: (:) [], CimException
+ FullyQualifiedErrorId : System.NotSupportedException
Suggested solution to the issue
It seems that Test-TargetResource passes unexpected parameters to Get-WindowsCapability. Parameter set should be handled in a similar way as in Set-TargetResource.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
WindowsCapability SNMP {
Name ='SNMP.Client~~~~0.0.1.0'
Ensure ='Present'
}
The operating system the target node is running
Windows 10 1709 Enterprise
Version and build of PowerShell the target node is running
PSVersion 5.1.16299.1146
PSEdition Desktop
Version of the DSC module that was used ('dev' if using current dev branch)
Using ComputerManagementDsc version 7.1.0.0.
The text was updated successfully, but these errors were encountered:
An attempt to test WindowsCapability resource fails.
Details of the scenario you tried and the problem that is occurring
Trying to handle capability resource 'SNMP.Client~~~~0.0.1.0' via following script:
WindowsCapability SNMP {
Name = 'SNMP.Client~~~~0.0.1.0'
Ensure = 'Present'
}
Verbose logs showing the problem
VERBOSE: An LCM method call arrived from computer COMP-XYZ with user sid S-1-5-21-xyz.
VERBOSE: [COMP-XYZ]: LCM: [ Start Compare ]
VERBOSE: [COMP-XYZ]: LCM: [ Start Resource ] [[WindowsCapability]SNMP::[WindowsFeatures]DefaultOSFeatures]
VERBOSE: [COMP-XYZ]: LCM: [ Start Test ] [[WindowsCapability]SNMP::[WindowsFeatures]DefaultOSFeatures]
VERBOSE: [COMP-XYZ]: [[WindowsCapability]SNMP::[WindowsFeatures]DefaultOSFeatures] Begin executing Test functionality on Windows Capability
'SNMP.Client~~~~0.0.1.0'.
A parameter cannot be found that matches parameter name 'Ensure'.
+ CategoryInfo : InvalidArgument: (:) [], CimException
+ FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.Dism.Commands.GetWindowsCapabilityCommand
PowerShell Desired State Configuration does not support execution of commands in an interactive mode. Please ensure that the underlying command is not prompting for user
input, such as missing mandatory parameter, confirmation prompt etc.
+ CategoryInfo : OperationStopped: (:) [], CimException
+ FullyQualifiedErrorId : System.NotSupportedException
Suggested solution to the issue
It seems that Test-TargetResource passes unexpected parameters to Get-WindowsCapability. Parameter set should be handled in a similar way as in Set-TargetResource.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
The operating system the target node is running
Windows 10 1709 Enterprise
Version and build of PowerShell the target node is running
PSVersion 5.1.16299.1146
PSEdition Desktop
Version of the DSC module that was used ('dev' if using current dev branch)
Using ComputerManagementDsc version 7.1.0.0.
The text was updated successfully, but these errors were encountered: