Impacts: Windows 10 1903, probably older versions too.
Cause: somehow SYSTEM doesn’t have rights to performance profile the machine
Fix: Resolved March 2020
Seriously. I messed with User Rights Assignments, which I shouldn’t even have to do for SYSTEM in the first place, no dice. Google had 3 hits on this, all are just listing the error code presence in a dll.
Yay OneDrive and Google Drive, makes paving a 10 instance easy(er)
How was this solved at the end? I have the same issue, very annoying, as during the creation of a Data Collector Set I can’t configure things like monitoring duration, etc.
Hey Csaba, thanks for the question! It seems it’s addressed in the March 2020 update. If you are seeing this still with the updates applied, please let me know what OS you see it with so I can confirm and let them know ok?
Thanks for your reply. The OS is Windows Server 2016 Standard. The March Updates KB4540723 and KB4540670 have been installed a month ago, on 23.03.
OH sorry, I totally missed this response!!!
Let me check my lab. I think I only validated 2019 hosts.
No problem 😉 Could you test it in your lab?
Some more details: on most of our servers the problem doesn’t exist, except for three, even though the March security updates (KB4540723 and KB4540670) are installed. Weird…
Sorry for posting so many posts, but I think I have now the root cause: the problem is not solved by the March updates, but by the April updates. Apparently all our systems that already have the April updates KB4550929 and KB4550994 don’t have the problem, while the ones that don’t have these updates yet still have the issue.
AH, no worries! April, gotcha! Ill update my article thank you for sharing with me!