Pdq inventory enterprise5/31/2023 ![]() If a large number of devices were to come online simultaneously a similar outcome to the above examples could be expected. These examples can also apply should you have many of your scan profiles configured with Heartbeat schedules. If the scan interval is less than 3.2 hours, scanning will never seem to complete. Since these types of scans take significantly longer, up to several minutes per machine, a scan for PST files averaged 87 seconds, or around 3.2 hours to complete. In another example, a registry or file scan is run against the same 4,000 machines. If you have a standard scan interval within that time, scanning will never seem to complete. Assuming the same default of 32 concurrent scans, it will take approximately 1 hour and 40 minutes to scan all 4,000 machines. ![]() ![]() In another example, a Standard Scan is run against 4,000 computers, with an average run time in our test environment of 48 seconds per scan. If the scan interval is set to less than 23 minutes, scanning will never seem to complete. If the default Preferences > Performance settings are default at 32 concurrent scans, it will take approximately 23 minutes to scan all of the machines. You have set a very aggressive scan interval with a more intensive scan.įor example, if a simplified scan such as Computer Info is run against 1,000 computers the average run in a test environment is around 44 seconds.There can be a few reasons why this is happening: The computers listed in PDQ Inventory are scanning continuously.
0 Comments
Leave a Reply. |