Follow these troubleshooting steps:
1. Make sure the GPOADmin Console is closed and remote clients are not currently working from their console.
2. Open Regedit.exe with admin privileges on the GPOADmin production server.
3. Go to the following registry key path:
HKEY_LOCAL_MACHINE\SOFTWARE\Quest\GPOADmin\VCConfig
4. Look for the registry key "ServerName" and check if it has an empty value. If this is not the case, do not continue to the next step and contact support for further assistance.
5. Look for the registry key "DataSource" and copy its value.
6. Modify the value of the "ServerName" key by pasting the "DataSource" copied value.
7. Close Regedit.exe and make sure the changes were saved.
8. Restart the "GPOADmin Service".
Monitor the GPOADMin Watcher Service behavior. If the issue persists, try restarting the GPOADmin server and check if the CPU utilization went back to normal.