- The files are not visibly changed.
- The "Last Modified" date was not changed.
- Files are moving to the DFSR ConflictedAndDeleted folder.
- Users may notice that their recent file changes are being removed, and the file seems to be an older version.
20090629 19:12:57.725 2532 USNC 2453 UsnConsumer::UpdateIdRecord ID record updated
+ RecordLength: 96
+ MajorVersion: 2
+ MinorVersion: 0
+ FileRefNumber: 0xF000000005E74
+ ParentFileRefNumber: 0x5000000000127
+ USN: 0x2ba89c0
+ TimeStamp: 20090629 19:12:57.709 Eastern Standard Time
+ Reason: Basic Info Change Close Named Data Extend Stream Change
+ SourceInfo: 0x0
+ SecurityId: 0x0
+ FileAttributes: 0x20
+ FileNameLength: 32
+ FileNameOffset: 60
+ FileName: samplefile.rtf
This behavior is by design.
If you use FSRM Classification Rules with DFSR replicated folders, we recommend that you configure the rules and run them before you configure DFSR. We also recommend that you only apply the rules to one server and not multiple servers. Scheduled FSRM rules should not run during regular working hours. FSRM Classification Rules should not be applied to latent DFSR servers where incoming changes are not yet replicated because in this case user file changes may be lost.
Article ID: 974774 - Last Review: Jan 26, 2010 - Revision: 1