{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-044-separate-dhcp-migration-preparation-transfer-and-acceptance/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-044-separate-dhcp-migration-preparation-transfer-and-acceptance/", "slug": "dse-20260908-044-separate-dhcp-migration-preparation-transfer-and-acceptance", "url": "https://update.dsesecurity.com/updates/dse-20260908-044-separate-dhcp-migration-preparation-transfer-and-acceptance/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-044-separate-dhcp-migration-preparation-transfer-and-acceptance.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-044-separate-dhcp-migration-preparation-transfer-and-acceptance/" }, "title": "Separate DHCP migration preparation, transfer, and acceptance", "summary": "What evidence should be required before retiring a migrated DHCP server?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "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:27+00:00", "modified_at": "2026-09-08T18:17:14+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 217, "potentially_affected": "Use this review when replacing a DHCP server.", "dse_recommendation": "Create a checklist that keeps preparation and final acceptance as distinct decisions.", "primary_source": { "name": "Migrate DHCP server to Windows Server", "url": "https://learn.microsoft.com/en-us/windows-server/networking/technologies/dhcp/migrate-dhcp-server", "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

DHCP migration moves an existing server’s settings to a replacement, with the objective of continuing lease service without a noticeable client change. Microsoft separates preparation, export/import of role settings, verification of the replacement, and post-migration retirement or recovery. The procedure calls for permissions to authorize DHCP, administer both servers, and write to the migration store. Microsoft documentation.

\n

Applicability

\n

Use this review when replacing a DHCP server. Identify the source, destination, migration storage, and network segments served. Review a failover deployment through the separate failover-migration procedure before treating it as a single-server replacement.

\n

DSE recommendation

\n

Create a checklist that keeps preparation and final acceptance as distinct decisions. Have the network owner review the settings to be transferred and name the clients used for testing. Protect the migration store and assign responsibility for each server-side operation. Leave source retirement pending until the destination has been verified against the agreed service inventory.

\n

Verification

\n

Compare the imported configuration with the approved source inventory and test lease service on representative segments. Record the responding server, returned configuration, and any client impact. Reconcile missing settings or unexpected responses before accepting the replacement. Document the retirement decision and retain the migration evidence through the organization’s approved recovery period.

\n

Official references

\n

Microsoft Learn: Migrate DHCP server to Windows Server. Source reviewed September 8, 2026.

", "content_text": "Source facts\nDHCP migration moves an existing server’s settings to a replacement, with the objective of continuing lease service without a noticeable client change. Microsoft separates preparation, export/import of role settings, verification of the replacement, and post-migration retirement or recovery. The procedure calls for permissions to authorize DHCP, administer both servers, and write to the migration store. Microsoft documentation.\nApplicability\nUse this review when replacing a DHCP server. Identify the source, destination, migration storage, and network segments served. Review a failover deployment through the separate failover-migration procedure before treating it as a single-server replacement.\nDSE recommendation\nCreate a checklist that keeps preparation and final acceptance as distinct decisions. Have the network owner review the settings to be transferred and name the clients used for testing. Protect the migration store and assign responsibility for each server-side operation. Leave source retirement pending until the destination has been verified against the agreed service inventory.\nVerification\nCompare the imported configuration with the approved source inventory and test lease service on representative segments. Record the responding server, returned configuration, and any client impact. Reconcile missing settings or unexpected responses before accepting the replacement. Document the retirement decision and retain the migration evidence through the organization’s approved recovery period.\nOfficial references\nMicrosoft Learn: Migrate DHCP server to Windows Server. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nDHCP migration moves an existing server’s settings to a replacement, with the objective of continuing lease service without a noticeable client change. Microsoft separates preparation, export/import of role settings, verification of the replacement, and post-migration retirement or recovery. The procedure calls for permissions to authorize DHCP, administer both servers, and write to the migration store. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/networking/technologies/dhcp/migrate-dhcp-server).\n\n## Applicability\n\nUse this review when replacing a DHCP server. Identify the source, destination, migration storage, and network segments served. Review a failover deployment through the separate failover-migration procedure before treating it as a single-server replacement.\n\n## DSE recommendation\n\nCreate a checklist that keeps preparation and final acceptance as distinct decisions. Have the network owner review the settings to be transferred and name the clients used for testing. Protect the migration store and assign responsibility for each server-side operation. Leave source retirement pending until the destination has been verified against the agreed service inventory.\n\n## Verification\n\nCompare the imported configuration with the approved source inventory and test lease service on representative segments. Record the responding server, returned configuration, and any client impact. Reconcile missing settings or unexpected responses before accepting the replacement. Document the retirement decision and retain the migration evidence through the organization’s approved recovery period.\n\n## Official references\n\n[Microsoft Learn: Migrate DHCP server to Windows Server](https://learn.microsoft.com/en-us/windows-server/networking/technologies/dhcp/migrate-dhcp-server). 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-044-separate-dhcp-migration-preparation-transfer-and-acceptance/", "url": "https://update.dsesecurity.com/updates/dse-20260908-044-separate-dhcp-migration-preparation-transfer-and-acceptance/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-044-separate-dhcp-migration-preparation-transfer-and-acceptance/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Separate DHCP migration preparation, transfer, and acceptance", "item": "https://update.dsesecurity.com/updates/dse-20260908-044-separate-dhcp-migration-preparation-transfer-and-acceptance/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-044-separate-dhcp-migration-preparation-transfer-and-acceptance/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-044-separate-dhcp-migration-preparation-transfer-and-acceptance/", "url": "https://update.dsesecurity.com/updates/dse-20260908-044-separate-dhcp-migration-preparation-transfer-and-acceptance/", "headline": "Separate DHCP migration preparation, transfer, and acceptance", "description": "What evidence should be required before retiring a migrated DHCP server?", "abstract": "What evidence should be required before retiring a migrated DHCP server?", "articleBody": "Source facts\nDHCP migration moves an existing server’s settings to a replacement, with the objective of continuing lease service without a noticeable client change. Microsoft separates preparation, export/import of role settings, verification of the replacement, and post-migration retirement or recovery. The procedure calls for permissions to authorize DHCP, administer both servers, and write to the migration store. Microsoft documentation.\nApplicability\nUse this review when replacing a DHCP server. Identify the source, destination, migration storage, and network segments served. Review a failover deployment through the separate failover-migration procedure before treating it as a single-server replacement.\nDSE recommendation\nCreate a checklist that keeps preparation and final acceptance as distinct decisions. Have the network owner review the settings to be transferred and name the clients used for testing. Protect the migration store and assign responsibility for each server-side operation. Leave source retirement pending until the destination has been verified against the agreed service inventory.\nVerification\nCompare the imported configuration with the approved source inventory and test lease service on representative segments. Record the responding server, returned configuration, and any client impact. Reconcile missing settings or unexpected responses before accepting the replacement. Document the retirement decision and retain the migration evidence through the organization’s approved recovery period.\nOfficial references\nMicrosoft Learn: Migrate DHCP server to Windows Server. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:16:27+00:00", "dateModified": "2026-09-08T18:17:14+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-044-separate-dhcp-migration-preparation-transfer-and-acceptance/" }, "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-044-separate-dhcp-migration-preparation-transfer-and-acceptance/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Separate DHCP migration preparation, transfer, and acceptance" }, "articleSection": [ "IT", "Networks & Infrastructure" ], "keywords": [ "IT", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 217, "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": "Migrate DHCP server to Windows Server", "url": "https://learn.microsoft.com/en-us/windows-server/networking/technologies/dhcp/migrate-dhcp-server" } } ] } }