Powershell processes running in the context of same user ID set in Exchange agent consume 100% CPU on monitored Exchange server
Exchange host does not have adequate number of CPUs allocated
allocate additioanl CPUs to monitored Exchange host. If the host is a virtual machine, reseve the CPU resources or move the vm to a less busy ESX host so it does not have to struggle for CPU cycles from parent host
Please refer to the “Resolved Issues” section of the Product Release Notes when new releases are available to identify if a fix for this defect has been implemented. Product Release Notes are available in the “Product Documentation” area of our Support Website at support.quest.com.