DFSR may not operate correctly when used in conjunction with FSRM file screens

Source: Microsoft Support

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

When using Distributed File System Replication (DFSR) and File Server Resource Manager (FSRM) file screens, the following symptoms may occur:

��������� Windows Server 2008 Domain Controllers may not successfully replicate SYSVOL when using a non-default path.

��������� Windows Server 2003 R2 or Windows Server 2008 DFSR participants may backlog replication and fail to stay in sync.

��������� DFSR debug logs may show 'disk space' or 'access denied' errors when replicating files inbound.

�

Example log 1:

20070605 09:33:36.440 5456 MEET 1243 <Meet::Install> -> WAIT Error processing update. updateName:664225.au uid:{3806F08C-5D57-41E9-85FF-99924DD0438F}-v333459 gvsn:{3806F08C-5D57-41E9-85FF-99924DD0438F}-v333459 connId:{6040D1AC-184D-49DF-8464-35F43218DB78} csName:Users csId:{C86E5BCE-7EBF-4F89-8D1D-387EDAE33002} code:5 Error:+ [Error:5(0x5) <Meet::InstallRename> meet.cpp:2244 5456 W66 Access is denied.]

�

Example log 2:

20071228 07:32:38.429 4344 MEET 1243 Meet::Install -> WAIT Error processing update. updateName:MyUser.doc uid:{03AEF357-60A4-4669-B6FE-6504AB90B164}-v711769 gvsn:{03AEF357-60A4-4669-B6FE-6504AB90B164}-v711769 connId:{4A1F7762-04C6-4E24-9DF5-17EDCFADD8ED} csName:UserData csId:{D340C004-EC83-4955-9258-C7B834810035} code:112 Error:

+ [Error:112(0x70) Meet::InstallRename meet.cpp:2244 4344 W832 There is

not enough space on the disk.]

+ [Error:112(0x70) NtfsFileSystem::Move ntfsfilesystem.cpp:925 4344

W831 There is not enough space on the disk.]

+ [Error:112(0x70) FileUtil::RenameByHandle fileutil.cpp:257 4344 W830

There is not enough space on the disk.]

�

FSRM allows administrators to create file screens to control the types of files that can be saved within a specified path. Based on how these configuration changes are made, DFSR may not correctly function.

To resolve this issue try one of the following methods:

��������� Do not configure FSRM to screen any paths being replicated by DFSR. This includes Windows Server 2008 SYSVOL if it is not in the default %systemroot%\sysvol path.

��������� If file screens are configured for DFSR replicated folder paths (including SYSVOL), do not block any file types being replicated. In the case of a domain controller this would include (but not be limited to) files with the extension INI, INF, POL, ADML, ADMX, and ADM.

��������� If screens are configured and file types being replicated are covered by FSRM, use passive mode notification rather than active blocking of files.

It is also possible to configure custom DFSR configurations to filter file types from being replicated. This way DFSR would not try to replicate excluded file types as long as they matched the FSRM screen rules. However, this cannot be done with the SYSVOL replicated folder.

FSRM has a hard-coded block in Windows Server 2008 to prevent active screens being set on the %systemroot% folder, so default SYSVOL configurations cannot be accidentally blocked.

How to use File Server Resource Manager (FSRM) to configure the notification feature for File Screening Management in Windows Server 2003 R2 -�http://support.microsoft.com/kb/926092

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE �MATERIALS�) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.