I have a interesting question.
If an organization has 2000 servers, 2 Qualys scanners, what is the best scenario to complete the vulnerability scan within 5 nights?
It would be normal practice to assign your 2000 targets into smaller asset groups with some feature in common. For example Windows Server in US vs those in EU. You may also want to consider breaking down by Operating System so that you can apply the appropriate Authentication record for the OS in the Asset Group. This assumes you're maximising the performance of vulnerability scans by using authentication.
While you can create an authenticated scan Option Profile which has all authentication records selected this would not be ideal if you later run authentication reports (to see which systems fail authentication). If an auth record is part of an option profile but is not used then a new QID for "auth record not attempted" will be created and would clog up your report. Not a major issue but something to consider.
Another possibility is to create different asset groups for scanning and for reporting. This allows you to scan specific locations, platforms or functions at a time best suited for each group, but to report in different ways. Maybe scan windows servers on a monday, UNIX on tuesday, comms on wednesday etc. Then report once a week (on a Sunday for example). This also assists when the business queries whether you were scanning a system that encountered perfomance issues. You could quickly discount the scan process as the cause if you weren't scanning that platform type on that day of week.
If you assign both scanner appliances to each task (assuming both appliances can see all targets) then the scheduler will effectively load balance the requests resulting in faster scan times for each target asset group.
Every installation differs but you could read the Qualysguard Rollout Guide for more ideas.
Retrieving data ...