Jump to content
Welcome to our new Citrix community!
  • 0

CPU spikes every 30sec on VDAs - WmiPrvSE.exe & Citrix Broker Windows service


Dawid Bbn

Question

Hi all

I am raising another issue I found since migrating from CVAD 7.15 LTSR (WS 2012R2) to 2203 LTSR CU3 (WS 2019).

I get CPU spikes every 30 seconds on VDAs caused by the MSMpEng.exe (MS Defender) and WmiPrvSE.exe (WMI Provider Host) Windows processes. The height of the spikes is proportional to the amount of active sessions on the VDAs.

I think I ruled out a root cause on my side: removed all agents from the servers incl. antivirus, used a clean image, manual server build, Group Policy, tested with various published .NET & Java apps, etc. Tried to disable MS Defender completely via GPO.

Tried to use ProcMon and Process Explorer to see what exactly processes are doing but since I am not an expert on these tools could not see anything useful to base on.

The CPU spikes stop as soon as I stop the Citrix Broker Windows service. Stopping other Citrix services does not have any effect on the spikes.

No changes were made to the configuration of the site/farm after the migration from Citrix 7.14 to 2203 env. which could trigger such spikes.

As a side note, initially, on some servers not reporting VDA load to Citrix Cloud/Monitor I had some other CPU spikes present. These were fixed by rebuilding performance counters on them but the main 30 sec spikes remained.

At this stage, I think it is another 2203 LTSR VDA bug and there is nothing I can do about it.

Has anyone experienced similar issues?

Thanks for the help!


ENVIRONMENT:
- Citrix DaaS Service 2023 CU3
- Windows Server 2019
- multisession, persistent VDAs
- VMware

CPUSpikesTaskManager.png

 

 

WindowsProcesses.png

Link to comment

3 answers to this question

Recommended Posts

  • 0

Seen this, or something very similar at least, for a very long time, but don't remember exactly what version it started with...

We had to disable resource monitoring to clear it up. 

Citrix Policy - "Enable Resource Monitoring" = Disabled
Lose some metrics like CPU and Memory to Director, but we have other tools to monitor these. 

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...