This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(19.2, 35%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESB%3C/text%3E%3C/svg%3E)
Hi,
to control some Windows workstations, I configured some administrative templates and attack surface reduction policies.
The policies seem to be partially pushed to the devices. I see following error:
MDM ConfigurationManager: Command failure status. Configuration Source ID: (3DD3FD9F-8ECB-4BD0-A606-B0805729CDD2), Enrollment Name: (MDMDeviceWithAAD), Provider Name: (defender), Command Type: (Add: from Replace or Add), CSP URI: (./vendor/msft/defender/configuration/devicecontrol/policyrules/{b7db918d-3702-4daa-865b-e71b45047c9e}/ruledata), Result: (The parameter is incorrect.).
How can I find out what is this policy rule impacted and which parameter is the wrong one?
Thanks
Weird
After some hours, I revisited the configuration. Now the error message doesnt appear and the CD/DVD block (which I was trying to do) seems to be working.
Is this observation a result of a behavior in Intune or on the workstation?
However, now I have other errors, which I cannot decipher:
MDM ConfigurationManager: Command failure status. Configuration Source ID: (3DD3FD9F-8ECB-4BD0-A606-B0805729CDD2), Enrollment Name: (MDMDeviceWithAAD), Provider Name: (Policy), Command Type: (Add: from Replace or Add), CSP URI: (./Device/Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/Receiver/Properties/Policy/FakePolicy/Version), Result: (The system cannot find the file specified.).
This Fakepolicy error event I see in other enviroments as well, that does sound a bell for me. It might be "by design", something which you don't need to care about. I am sure every mdm managed machine you will see, has some of these errors, even all settings would be correct and applied.
thanks for the suggestion.
I think MS needs to review their code why they throw an error if there is no error, smells like bad design.