Article ID: 944508
Article Last Modified on 11/12/2007
APPLIES TO
- Microsoft Windows Server 2003 R2 Datacenter Edition (32-Bit x86)
- Microsoft Windows Server 2003 R2 Datacenter x64 Edition
- Microsoft Windows Server 2003 R2 Enterprise Edition (32-Bit x86)
- Microsoft Windows Server 2003 R2 Enterprise x64 Edition
- Microsoft Windows Server 2003 R2 Standard Edition (32-bit x86)
- Microsoft Windows Server 2003 R2 Standard x64 Edition
SYMPTOMS
Consider the following scenario:
- You use the File Screening Management feature to manage folders in Windows Server 2003 R2.
- You create a file-screening policy for a destination folder. For example, you create a file-screening policy for folder A. This policy allows for only text files to be saved in folder A.
- You create another folder on the same volume. For example, you create folder B. This folder is not configured to use the file-screening policy. Or, the folder is configured to use a file-screening exception policy that allows for file types other than text files.
- You save some files in folder B. These files include text files and other types of files.
- You drag folder B into folder A.
In this scenario, you expect only the text files in folder B to be saved in folder A. Instead, all the files in folder B are saved in folder A.
Note This issue does not occur in the following situations:
- You copy folder B into folder A instead of dragging the folder.
- You copy and paste files from folder B into folder A.
CAUSE
If a folder is dragged to another location on the same volume, the file-screening driver does not scan files in the folder. Therefore, the configured file-screening policies are not applied to the dragged folder. This functionality is by design. Performance during a folder-dragging operation decreases significantly if all files are scanned when you perform this operation.
WORKAROUND
To work around this issue, save the destination folder and the source folder on different volumes. In the scenario that is described in the "Symptoms" section, save folder A and folder B on different volumes.
STATUS
This behavior is by design.
Keywords: kbtshoot kbprb KB944508
