Real time scanning of historical file versions cannot be skipped

Consider the scenario where you are using the SharePoint Object Model (OM) to update the file stream of a document stored in a SharePoint document library. You notice that while you can skip the real-time scanning of the current version of the document, you cannot do so for historical versions.
More information
This is an expected behavior at the time of creation of this article. Historical document versions are read-only from the SharePoint OM perspective and are managed internally by SharePoint.
historical; previous; version; real time; scanning
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Article ID: 2833712 - Last Review: 04/23/2013 05:40:00 - Revision: 3.0

Microsoft SharePoint Server 2010

  • KB2833712