Forum Discussion
Deleted
Deleted I have the exactly the same problem, might be a non US language problem ? I also run PA 4.0 on DE systems.
The reported line differs between client and server and I am missing the effective state of all audit policys if I ignore the error message.
FLeven and @bennn2806 : at what point does this happen? What are you doing when the error message appears?
Deleted
It is a a problem with the GPOs on the local system, I managed to run "Compare to effective state" on a non domain joined machine, but it will not work on a domain joined machine in the "Computers" OU, where the Default Domain Policy is applied.
Also it will work if I choose a simple GPO without Sec or Autit policys.
I am using the "MSFT-Win10-WS-v1809-FINAL.PolicyRules" shipped with PA 4.
As you can see the effictive state of the Audit Policy entry's are empty, because it failed to compare them for whatever reason.
I did some cleanup of my local auditpols etc. but no dice.
FLeven Look in your user account's %TEMP% directory and see whether it leaves behind any temporary files. If so, what's in them?
Compare to effektiv state, after the Username / Password I get the error.
FLeven - I'm trying to repro but haven't been able to. I don't see "EntityName" anywhere, so I think it's something specific to your report. Can you send me a private message through here with the .PolicyRules report attached?