Forum Discussion
Performance in scanning
We are trying to search for CUI data on internal file stores. Last week, I decided to run another discovery scan, this time using ALL instead of Policy Only. It took much longer and left the scanner server in an almost unusable state and didn’t give really any more information than the first one did.
Based on my research, we need to define and set the policy before we run scans. This is the information tip from the Purview scanner settings:
Scan started at: 2026-05-20 22:54:06Z
Scan ended at: 2026-05-24 16:16:51Z
Scan duration: 3 days, 17 hours, 22 minutes, 45 seconds
Scan id: 93acb922-e2ac-4fb7-b259-d6184e7aa434
Repository: \\cab-filesrv-01.fg.com\Departments. Enforce mode is Off
Scanned files:3509640
Actions:
Classified:3369456
Classified as Public:14
Classified as Fg Private:3369442
Labeled:0
Remove label:0
Protected:0
Remove protection:0
Files with matched information types:572895
Skipped due to - No match:0
Skipped due to - Not supported:0
Skipped due to - Already labeled:0
Skipped due to - Already scanned:0
Skipped due to - Require justification:0
Skipped due to - Unknown reason:0
Skipped due to - Excluded:98833
Skipped due to - Attribute:0
Failed:41318