These errors\warnings do not affect the integrity of the audit log (unless the policy settings are disabled in audited servers). Our R&D team is actively investigating the issue and working on a fix. A patch will be released shortly, and we will notify you here on the Community as soon as it becomes available.
Unable to detect audit policy settings for the server ########## due to the following error: Netwrix Auditor cannot automatically configure advanced audit on servers running Windows NT 10.0.
Is there a Netwrix patch/update coming out for this? The only monitoring plan that we are experiencing issues with is our Windows Monitoring plan that watches over our domain controllers for Add/Remove programs, Services, Audit policies, etc… Applying an update to Netwrix would be a lot better than having to install an OOB patch to a bunch of domain controllers. If not, does someone have a link to the 2019 version of the KB so I can pass it on to our SysAdmins?
I installed 10.7.13820 and it did NOT fix the issue - I’m still seeing the log entries for nearly all of our monitored endpoints. I rebooted the Auditor and SQL servers for good measure but the issue still remains - any advice on what I can try next?
The patch that was released did fix the issue caused with Logon Activity plans that had errors about an Unknown Format with the registery. However, you are correct that the Auditor patch did not resolve the Windows NT 10.0 errors. Those errors will be resolved in a 2nd patch that we plan on releasing soon.
Thanks all for saving me typing back to Dan. It is correct - the patch corrected two of the 3 issues I saw after the installation of the April Patch Tuesday patches. The AD Logon Activity and ADFS activity plans were both fixed.
As mentioned in my previous message, the Windows Server monitoring plans are still showing the Windows NT 10.0 errors. I will let support know to save us all some time.
If you do not have a ticket yet with us, please let me know if you want one because we are tracking all customers who have the Windows NT 10.0 issue and we will be proactively reaching out to them once we have the new patch released that fixes this error. In addition, we will be posting in here as well.