A user reported that at a customer, WMI memory leaks were happening due to the use of cuAgent on machines using ControlUp 8.8 or higher. Removing cuAgent resolved the issue and a ticket with support was created. They suggest using a ControlUp script (https://www.controlup.com/script-library-posts/show-local-wmi-activity/) to obtain WMI logs and identify the problematic cuAgent WMI queries.
Read the entire ‘Troubleshooting WMI Memory Leaks with ControlUp cuAgent’ thread below:
cuAgent seems to cause WMI memory leaks
At a customer I have a strange behaviour.
We migrated the customer from COP 8.8 to 8.8 MR in DEC last year.
The cuAgent is deployed in v8.8.0.1181 to Win10, Win2016 and Win2022 Citrix golden masters…
In Win2022 we are seeing issues with WMI memory leaks. After some uptime (2-3 days) the load evaluators inside the VDA is crashing and we are seeing 70+ users/sessions per affected vm.
No more WMI querys are possible… (RPC not ready)
When we remove cuAgent the machines are doing well.
In WMI Eventlog we see a lot of errors regarding cuAgent thats why I suggested to remove cuAgent and bingo…
I havent seen something at other on-prem and win2022 customers.
Somebody saw something similar?
Ticket with support will be created soonish…
It would be great to get the WMI logs and see exactly which CU Agent WMI queries are causing this issue
maybe our script can help – https://www.controlup.com/script-library-posts/show-local-wmi-activity/
Continue reading and comment on the thread ‘Troubleshooting WMI Memory Leaks with ControlUp cuAgent’. Not a member? Join Here!
Categories: All Archives, ControlUp Scripts & Triggers