Summary
This article discusses one of the reasons as to why the compliance import may take an extended period of time to complete for a limited number of imports, and then return to a normal duration afterwards.
Synopsis
The reconciliation run take a long time at our site. The average run time is around 13hours. If I have a look at the log file of the compliancereader it's always a tag which take hour to complete: WriteFileEvidence I know, that from SP3 onward the windows directory was excluded and we made a registry entry for our system to exclude the windows directory because of the bulk information for no use. However, I assume the tag in the log file is exactly about this issue. Am I right?
Discussion
The slow reconciliation is related to when we delete evidences that we no longer collect from the Windows directory. This should not be an issue after running the compliance import multiple times as this will clear out the evidences that are being deleted.
