# Plan DFS client return after a target comes back online

> How should DFS failback be configured and tested after target maintenance?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-067-plan-dfs-client-return-after-a-target-comes-back-online/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:16:04+00:00
- Modified: 2026-09-08T18:20:22+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 1 minutes

## What you need to know

How should DFS failback be configured and tested after target maintenance?

## Potentially affected

Use this review when maintaining a DFS target that clients should use again afterward.

## DSE recommendation

Record the starting referral and failback settings before removing a target from service.

## Article

## Source facts

Disabling a DFS namespace-server or folder-target referral stops directing users to that target, which Microsoft identifies as useful for maintenance. Client failback can return clients to a restored target, subject to the documented client requirements. Folders with targets inherit failback settings from the namespace root, with configuration available at folder level. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/storage/dfs-namespaces/enable-or-disable-referrals-and-client-failback).

## Applicability

Use this review when maintaining a DFS target that clients should use again afterward. Identify the namespace root, folder settings, client versions, and intended preferred target. Review referral ordering as a separate input to the maintenance plan.

## DSE recommendation

Record the starting referral and failback settings before removing a target from service. Have the file-service owner define when the restored target should be accepted for use. Include both the outage period and the return-to-service period in the client test plan. Preserve the original settings and assign responsibility for checking that temporary maintenance choices are cleared.

## Verification

Observe representative client target selection while the approved target is unavailable and after it is restored. Record which clients meet the source’s failback requirements and whether they return as intended. Check inherited and explicit settings if behavior differs between folders. Resolve unexpected persistence on an alternate target before closing the maintenance record.

## Official references

[Microsoft Learn: Enable or Disable Referrals and Client Failback](https://learn.microsoft.com/en-us/windows-server/storage/dfs-namespaces/enable-or-disable-referrals-and-client-failback). Source reviewed September 8, 2026.

## Primary reference

- Name: Enable or Disable Referrals and Client Failback
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/storage/dfs-namespaces/enable-or-disable-referrals-and-client-failback
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Plan DFS client return after a target comes back online,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-067-plan-dfs-client-return-after-a-target-comes-back-online/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.