Once we applied these patches, the stability of our PRTG instance was lost - the additional load involved with handling the more secure encryption must have pushed our probes over the limit and we're getting a lot of complaints now about the probe being overloaded and WMI sensors and such taking too long. Nothing in PRTG was changed, only this patch was applied to our DCs.
Have others seen this and reported it already? Is there a better option for addressing this in PRTG other than creating additional probes? I'm looking for guidance on best practice from PRTG.
This article details the related patch and changes to domain authentication once applied: https://support.microsoft.com/en-us/help/4557222/how-to-manage-the-changes-in-netlogon-secure-channel-connections-assoc
Hello Matt,
Thank you for your post.
We did not have any prior cases regarding this, so we do not have any information at the moment. However we will take a closer look at this.
In the mean time I would suggest to check if you are bale to make exceptions for server that need to comunicate with non-secure RPC.
Kind regards,
Sasa Ignjatovic, Tech Support Team
Sep, 2020 - Permalink