ComputerManagementDsc
ComputerManagementDsc copied to clipboard
PowerPlan: The system cannot find the path specified
Details of the scenario you tried and the problem that is occurring
The resource fails because it cannot find an unnamed file on Windows 2019 and a TMP file on Windows 2016.
Verbose logs showing the problem
On Windows 2016 computers Core or GUI
VERBOSE: [ComputerName]: LCM: [ Start Resource ] [[PowerPlan]Highperformance_1475074047]
VERBOSE: [ComputerName]: LCM: [ Start Test ] [[PowerPlan]Highperformance_1475074047]
VERBOSE: [ComputerName]: [[PowerPlan]Highperformance_1475074047] Validating power plan 'High performance'.
VERBOSE: [ComputerName]: LCM: [ End Test ] [[PowerPlan]Highperformance_1475074047] in 0.4530 seconds.
PowerShell DSC resource MSFT_PowerPlan failed to execute Test-TargetResource functionality with error message: Could not find a part of the path 'C:\Windows\system32\config\systemprofile\AppData\Local\Temp\kc2hwjb1.tmp'.
+ CategoryInfo : InvalidOperation: (:) [], CimException
+ FullyQualifiedErrorId : ProviderOperationExecutionFailure
+ PSComputerName : ComputerName
On Windows 2019 computers Core or GUI
VERBOSE: [ComputerName]: LCM: [ Start Resource ] [[PowerPlan]Highperformance_1278334551]
VERBOSE: [ComputerName]: LCM: [ Start Test ] [[PowerPlan]Highperformance_1278334551]
VERBOSE: [ComputerName]: [[PowerPlan]Highperformance_1278334551] Validating power plan 'High performance'.
VERBOSE: [ComputerName]: LCM: [ End Test ] [[PowerPlan]Highperformance_1278334551] in 0.7300 seconds.
PowerShell DSC resource MSFT_PowerPlan failed to execute Test-TargetResource functionality with error message: The system cannot find the path specified
+ CategoryInfo : InvalidOperation: (:) [], CimException
+ FullyQualifiedErrorId : ProviderOperationExecutionFailure
+ PSComputerName : ComputerName
Suggested solution to the issue
Unfortunately no idea...
The DSC configuration that is used to reproduce the issue (as detailed as possible)
Configuration in YAML format for Datum
ComputerManagementDsc:
PowerPlan:
Name: High performance
IsSingleInstance: Yes
The operating system the target node is running
OsName : Microsoft Windows Server 2016 Datacenter
OsOperatingSystemSKU : DatacenterServerEdition
OsArchitecture : 64-bit
WindowsBuildLabEx : 14393.1794.amd64fre.rs1_release.171008-1615
OsLanguage : en-US
OsMuiLanguages : {en-US}
OsName : Microsoft Windows Server 2019 Datacenter
OsOperatingSystemSKU : DatacenterServerEdition
OsArchitecture : 64-bit
WindowsVersion : 1809
WindowsBuildLabEx : 17763.1.amd64fre.rs5_release.180914-1434
OsLanguage : en-US
OsMuiLanguages : {en-US}
Version and build of PowerShell the target node is running
PSVersion 5.1.14393.1884
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.14393.1884
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
PSVersion 5.1.17763.316
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.17763.316
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
Version of the DSC module that was used ('dev' if using current dev branch)
ComputerManagementDsc 7.0.0.0