Does anyone know why the full "scan" folder is scanned upon completion of a repair?
I have configured my agents and scan and repair settings to only scan certain public folders. This was working great until I run repairs on the machine and it runs a scan of my entire "scan" folder upon the completion of the repair.
Just trying to understand if this behavior is correct and if it is why it would be this way.
I've confirmed that my agents are set to only scan the custom public group. I've also checked the scan repair settings and even went through and changes every one of our scan and repair settings to only scan the custom public groups but it still scans the full "scan" folder upon completion of a repair.
Everything seems to be normal in the vulscan log until I get to this point... which is just after the repair completes.
----------------------------------------------
....
Command Interpreter running
Executing C:\Program Files\LANDesk\LDClient\sdmcache\install_flash_player_ax_32bit_11.5.502.146.exe -install
Message returned from repair script was Repair is done.
Last status: Done
SendPatchStatus: patch 'install_flash_player_ax_32bit_11.5.502.146.exe' status Repair is done. at core. Result: 80004005. Adding to action history
Family install_flash_player_ax_32bit_11.5.502.146.exe, action 2, status Repair is done.
HKLM\Software\LANDesk\ManagementSuite\WinClient\VulscanReboot exists. reboot is required.
RunPatches completed. 1 processed. 1 installed. 0 failures.
Reboot action set to 'never.' Not rebooting.
Updates have been applied to this computer. Rescanning.
Loading MSI patch information
product {41785C66-90F2-40CE-8CB5-1C94BFC97280}
.....
----------------------------------------------
After this it runs through a long list and shows detections from the "scan" folder.