Description
Ever increased RAM usage in the Credential Guard service (lsalso.exe) in the server that hosts the Redgate Monitor Base Monitor service. Eventually, the server might crash.
Causes
This appears to be caused by a bug in "WMI over DCOM" (Windows).
How to fix\work around the issue
Since this is an Operating System issue we can't fix this by changing the code in Redgate Monitor, however you can work around this by using "WMI over WinRM HTTP (or HTTPS)" rather than "WMI over DCOM" to connect to Windows Monitored servers in Redgate Monitor.
If you are monitoring a large number of servers, and if your repository is hosted in SQL Server, you can run the following T-SQL query on the Redgate Monitor repository which will automatically change the connection type:
UPDATE settings.Clusters
SET WmiConnectionMethod = 2
WHERE WmiConnectionMethod = 0;Functionality will remain the same, regardless of the connection method you use.
Factors to consider when changing the connection type WMI over RM HTTP (or HTTPS)
- Not supported by older versions of Windows (supported in Windows Server 2008 and newer)
- Requires Windows Management Framework 3.0 or greater installed
- Different networking requirements
Was this article helpful?
Articles in this section
- High RAM usage in the Credential Guard service on servers hosting the Base Monitor service
- Analysis page JavaScript error in Redgate Monitor 14.2.0
- Error: WINRM 0x8009030e
- Redgate Monitor migration guide to version 14
- "Your browser does not seem to be accepting cookies." error message
- Setting up OpenID Connect (OIDC) with Entra ID in Redgate Monitor
- Proxy Configuration in Redgate Monitor
- WMI error after DCOM hardening patch
- Redgate Monitor alert tuning
- Redgate Monitor set up for optimal performance