DFS-N: Client failback should be enabled on the following namespace

Updated: June 30, 2010

Applies To: Windows Server 2008 R2, Windows Server 2012

This topic is intended to address a specific issue identified by a Best Practices Analyzer scan. You should apply the information in this topic only to computers that have had the File Services Best Practices Analyzer run against them and are experiencing the issue addressed by this topic. For more information about best practices and scans, see Best Practices Analyzer.

Issue

Client failback is disabled on the following namespace:

Impact

Client computers could experience slower response times if they fail over to a remote folder target and do not fail back to the local folder target when it comes back online.

Resolution

Use DFS Management to enable client failback on the following namespace:

To do so, use one of the following procedures to enable client failback on the namespace.

• To enable client failback for a namespace root by using the Windows interface

• To enable client failback for a namespace root by using a command line

For failback to work, client computers must meet the requirements that are listed in the following topic: Review DFS Namespaces Client Requirements.

To enable client failback for a namespace root by using the Windows interface

1. Click Start, point to Administrative Tools, and then click DFS Management.

2. In the console tree, under the Namespaces node, right-click a namespace, and then click Properties.

3. On the Referrals tab, select the Clients fail back to preferred targets check box.

To enable client failback for a namespace root by using a command line

1. To open an elevated Command Prompt window, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

2. Type: **Dfsutil property targetfailback enable \\**namespace.