{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-067-plan-dfs-client-return-after-a-target-comes-back-online/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-067-plan-dfs-client-return-after-a-target-comes-back-online/", "slug": "dse-20260908-067-plan-dfs-client-return-after-a-target-comes-back-online", "url": "https://update.dsesecurity.com/updates/dse-20260908-067-plan-dfs-client-return-after-a-target-comes-back-online/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-067-plan-dfs-client-return-after-a-target-comes-back-online.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-067-plan-dfs-client-return-after-a-target-comes-back-online/" }, "title": "Plan DFS client return after a target comes back online", "summary": "How should DFS failback be configured and tested after target maintenance?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-08T18:16:04+00:00", "modified_at": "2026-09-08T18:20:22+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 218, "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.", "primary_source": { "name": "Enable or Disable Referrals and Client Failback", "url": "https://learn.microsoft.com/en-us/windows-server/storage/dfs-namespaces/enable-or-disable-referrals-and-client-failback", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

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.

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official references

\n

Microsoft Learn: Enable or Disable Referrals and Client Failback. Source reviewed September 8, 2026.

", "content_text": "Source facts\nDisabling 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.\nApplicability\nUse 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.\nDSE recommendation\nRecord 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.\nVerification\nObserve 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.\nOfficial references\nMicrosoft Learn: Enable or Disable Referrals and Client Failback. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nDisabling 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).\n\n## Applicability\n\nUse 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.\n\n## DSE recommendation\n\nRecord 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.\n\n## Verification\n\nObserve 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.\n\n## Official references\n\n[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." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260908-067-plan-dfs-client-return-after-a-target-comes-back-online/", "url": "https://update.dsesecurity.com/updates/dse-20260908-067-plan-dfs-client-return-after-a-target-comes-back-online/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-067-plan-dfs-client-return-after-a-target-comes-back-online/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Plan DFS client return after a target comes back online", "item": "https://update.dsesecurity.com/updates/dse-20260908-067-plan-dfs-client-return-after-a-target-comes-back-online/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-067-plan-dfs-client-return-after-a-target-comes-back-online/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-067-plan-dfs-client-return-after-a-target-comes-back-online/", "url": "https://update.dsesecurity.com/updates/dse-20260908-067-plan-dfs-client-return-after-a-target-comes-back-online/", "headline": "Plan DFS client return after a target comes back online", "description": "How should DFS failback be configured and tested after target maintenance?", "abstract": "How should DFS failback be configured and tested after target maintenance?", "articleBody": "Source facts\nDisabling 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.\nApplicability\nUse 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.\nDSE recommendation\nRecord 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.\nVerification\nObserve 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.\nOfficial references\nMicrosoft Learn: Enable or Disable Referrals and Client Failback. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:16:04+00:00", "dateModified": "2026-09-08T18:20:22+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-067-plan-dfs-client-return-after-a-target-comes-back-online/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260908-067-plan-dfs-client-return-after-a-target-comes-back-online/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Plan DFS client return after a target comes back online" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 218, "timeRequired": "PT1M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Enable or Disable Referrals and Client Failback", "url": "https://learn.microsoft.com/en-us/windows-server/storage/dfs-namespaces/enable-or-disable-referrals-and-client-failback" } } ] } }