# Account for scope removal when migrating DHCP failover partners

> What must be checked before breaking a DHCP failover relationship during migration?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-060-account-for-scope-removal-when-migrating-dhcp-failover-partners/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:16:11+00:00
- Modified: 2026-09-08T18:20:21+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: IT, Networks & Infrastructure
- Reading time: 1 minutes

## What you need to know

What must be checked before breaking a DHCP failover relationship during migration?

## Potentially affected

Use this review when replacing both members of a DHCP failover arrangement.

## DSE recommendation

Prepare a partner-and-scope worksheet and have another administrator verify the side from which the relationship will be removed.

## Article

## Source facts

Microsoft’s failover-migration sequence breaks the existing relationship, exports and imports settings, and configures failover on the replacement servers. Deleting the relationship removes its member scopes from the partner DHCP server. The documented example moves a Windows Server 2022 failover deployment to Windows Server 2025, using specifically identified old and new servers. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/networking/technologies/dhcp/migrate-existing-dhcp-failover).

## Applicability

Use this review when replacing both members of a DHCP failover arrangement. Identify every relationship, partner, and member scope before adapting the sequence. Treat the source’s server names as an example rather than deployment inputs.

## DSE recommendation

Prepare a partner-and-scope worksheet and have another administrator verify the side from which the relationship will be removed. Assign owners for preserving settings, controlling the service transition, and testing the new pair. Record the expected scope inventory at each stage so deliberate removal is not confused with accidental loss. Keep the approved recovery decision available throughout the migration.

## Verification

After each approved stage, compare the observed scope and relationship state with the worksheet. Test client lease behavior before accepting the new relationship, and include the selected failover exercise. Retain evidence from both replacement servers. Investigate missing scopes or an unexpected serving partner before retiring either original server.

## Official references

[Microsoft Learn: Migrate existing DHCP failover deployment on Windows Server](https://learn.microsoft.com/en-us/windows-server/networking/technologies/dhcp/migrate-existing-dhcp-failover). Source reviewed September 8, 2026.

## Primary reference

- Name: Migrate existing DHCP failover deployment on Windows Server
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/networking/technologies/dhcp/migrate-existing-dhcp-failover
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Account for scope removal when migrating DHCP failover partners,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-060-account-for-scope-removal-when-migrating-dhcp-failover-partners/
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.