VirusScan 8.8 scheduled as Below Normal but Normal process is using CPU
I'm currently testing a small deployment of VirusScan 8.8 and we're doing a full scan to check these new priority settings. However, while I see that scan32.exe is set to Below Normal priority as per policy, it's the McShield.exe process which is using all the CPU.
Is this expected behaviour? It makes me wonder what the point of prioritising the scan is when the process you prioritise doesn't seem to be the one which has an impact.