Best Practices Analyzer for File Services: Operation

Updated: April 27, 2010

Applies To: Windows Server 2008 R2, Windows Server 2012

Topics in this section can help you bring File Services running on Windows Server 2008 R2 into compliance with operation best practices. Content in this section is most valuable to administrators who have completed a Best Practices Analyzer scan of File Services, and who want information about how to interpret and resolve the scan results that identify areas of File Services that are noncompliant with operation best practices.

Best Practices Analyzer and operation rules

Operation rules are applied to identify possible causes for a role failing to complete its prescribed tasks in the enterprise. An example of a violation of operation rules that a Best Practices Analyzer scan might find is a service that is paused or stopped.

For more information about Best Practices Analyzer and scans, see Best Practices Analyzer.

Topics in this section

• DFS-N: The DFS Namespace service should be started

• DFS-R: The read-only mini-filter driver must always be loaded on servers that have read-only DFS replicated folders

• DFS-R: The DFS Replication service needs sufficient disk space to store replication conflicts for the replicated folder

• DFS-R: There should not be a large number of replication conflicts in the replicated folder '{0}'

• DFS-R: Volumes hosting replicated folders should have sufficient free disk space

• DFS-R: The staging folder for the replicated folder should not require frequent cleanup

• FSRM: Log files for file management tasks should be properly deleted

• FSRM: All nodes in a failover cluster should be reachable

• FSRM: The File Server Resource Manager service should be running

See Also

Concepts

Best Practices Analyzer for File Services: Configuration
Best Practices Analyzer for File Services: Performance
Best Practices Analyzer for File Services: Security