2016 Servers Showing High CPU During Patching
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(259.20000000000005, 75%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDE%3C/text%3E%3C/svg%3E)
Dolle, Edward
81
Reputation points
There are four servers - three AD servers and the WSUS server. All are Win2016. We run production patching on Monday and Tuesday at 3:00AM. These servers install their patches on Tuesday. I do not see anything running on these systems at that time.
Two of the servers (AD & WSUS) have been spiking the CPU for the last three patch windows (June, July, August).
One of the AD server has been spiking the CPU only during the last two patch windows (July & August).
The last AD server spiked its CPU this morning.
I can probably understand the WSUS server but we have not seen this happen before June.
Would anyone know why just the 2016 servers would show high CPU during that time, and just these?
Windows for business | Windows Server | User experience | Other
Sign in to answer