I have found how to schedule a scan in BD2012 on Windows7 and probably earlier Windows versions. I noticed several requests in this forum for the ability to schedule system scans. This facility has been removed in BD2012 and the vendors say that it is unnecessary because of the new continuous scanning feature - but BD2012 still forces a full system scan after 8 days, so the new continuous scan feature does not appear to make full scans redundant at all.
The problem with forcing a full scan on me every 8 days is that it is not necessarily convenient for me to do it then. If I defer it until the end of my working day, I then have to change the power options so the scan won't just get delayed by the system going into standby, thereby delaying the scan until the next time I want to do some work. The statement from BD that the full scan is unnecessary because of the continuous scan feature is disingenuous when they must know that the full scan is still forced every 8 days - the only difference is the user has not been given any way of scheduling it.
I have found the solution by examining the commandline of the running process when it is doing a full system scan - it runs odscanui. I found that if I set up a batch file containing the odscanui command I can then schedule a task to run with the "Wake the computer to run this task" option checked to force it to wake from standby if necessary.
The batch file contains these commands:
cd "C:\Program Files\Bitdefender\Bitdefender 2012\"
odscanui.exe /SystemScanTask dcf483c4-26d0-4e6f-ba28-6a53a00adae1
where dcf483c4-26d0-4e6f-ba28-6a53a00adae1 is the name of the profile directory located in C:\ProgramData\Bitdefender\Desktop\Profiles\Logs on my PC. Users must obtain the name of this directory on their own computer, it is not a constant. The odscanui program needs to know this directory so it can write the XML log in the right place. Without this parameter odscanui fails immediately.
Running this causes a window to pop up to run the scan, but it does not require user intervention, so it is perfect for overnight unattended running.
I note that elsewhere in these forums the BD batch scan utility bdc.exe has been suggested as a way to run a scan from the commandline. It's true this can be used, but it doesn't update the flag forcing a new full system scan after 8 days, so even though you run a full scan, BD doesn't know you have run it. However if you run odscanui then it will update the flag and BD then says the scan has been run today and does not require a scan for another 8 days. So if odscanui is scheduled to run every week, the problem is solved.
I have some questions from this:
- why do BD force a scan even though continuous real time scanning supposedly makes it redundant?
- why didn't BD document the odscanui feature so users could use it - why force users to reverse engineer the product to solve their problems?