A user was having trouble running a scheduled scan for a specific device on ControlUp. Another user suggested checking if the last connection was successful and found that the VMware Tools update had failed. Upon installing and rebooting the tools, the scan was able to successfully run.
Read the entire ‘Troubleshooting Scheduled Scans on ControlUp’ thread below:
I have a template configured to check for vulnerabilities and patches for Windows systems from 4:30-5:30pm everyday. I have one device that shows the last scan was four days ago. I click the ellipsis for the device to start a scan, but it never seems to run. Is there a way to find out why the scan is not happening?
Can you confirm if the last connection was successful today or four days ago?
This VM failed the VMware Tools update and wasn’t running VMware tools. I got the VM tools installed and rebooted the VM and then it completed the scan. Last Scan was showing four days ago and Last Seen was three days ago. After the tools install and a reboot it seems to have corrected itself.
Continue reading and comment on the thread ‘Troubleshooting Scheduled Scans on ControlUp’. Not a member? Join Here!
Categories: All Archives, ControlUp for Compliance