{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-026-plan-storage-migration-service-cutover-around-the-server-identity-handoff/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260908-026-plan-storage-migration-service-cutover-around-the-server-identity-handoff/",
        "slug": "dse-20260908-026-plan-storage-migration-service-cutover-around-the-server-identity-handoff",
        "url": "https://update.dsesecurity.com/updates/dse-20260908-026-plan-storage-migration-service-cutover-around-the-server-identity-handoff/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260908-026-plan-storage-migration-service-cutover-around-the-server-identity-handoff.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-026-plan-storage-migration-service-cutover-around-the-server-identity-handoff/"
        },
        "title": "Plan Storage Migration Service cutover around the server identity handoff",
        "summary": "What must be accepted when Storage Migration Service transfers a server identity?",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "featured": false,
        "image": {
            "theme": "identity-cloud",
            "label": "Identity & cloud",
            "alt": "Governed cloud identity system with connected service and lifecycle nodes.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-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:45+00:00",
        "modified_at": "2026-09-08T18:17:14+00:00",
        "reviewed_on": "2026-09-08",
        "reading_minutes": 1,
        "word_count": 219,
        "potentially_affected": "Use this review when the inventory and transfer work has reached an approved identity-handoff decision.",
        "dse_recommendation": "Prepare an endpoint worksheet and have a second administrator check it against the migration plan.",
        "primary_source": {
            "name": "How cutover works in Storage Migration Service",
            "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/cutover",
            "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": "<h2>Source facts</h2>\n<p>Cutover transfers the source computer&#8217;s network identity to the destination. Microsoft states that the source retains its files afterward but is no longer available to users and applications. Before cutover, the administrator supplies the destination network configuration and can select a unique replacement name for the source. The service exposes progress descriptions for the individual cutover stages. <a href=\"https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/cutover\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft documentation</a>.</p>\n<h2>Applicability</h2>\n<p>Use this review when the inventory and transfer work has reached an approved identity-handoff decision. Identify both computers, their intended final names, and the users and applications that must reach the destination.</p>\n<h2>DSE recommendation</h2>\n<p>Prepare an endpoint worksheet and have a second administrator check it against the migration plan. Name the person who will authorize the handoff and the workload owners who will accept it. Communicate the interruption window and preserve the pre-cutover state needed by the approved recovery procedure. Keep the retained source files under controlled ownership while acceptance remains open.</p>\n<h2>Verification</h2>\n<p>Record the reported cutover stages and verify the resulting names and network configuration. Test the actual client paths and application operations selected in advance. Confirm that users reach the intended destination and that the source is handled according to the approved plan. Investigate partial completion before declaring the migration accepted.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/cutover\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: How cutover works in Storage Migration Service</a>. Source reviewed September 8, 2026.</p>",
        "content_text": "Source facts\nCutover transfers the source computer’s network identity to the destination. Microsoft states that the source retains its files afterward but is no longer available to users and applications. Before cutover, the administrator supplies the destination network configuration and can select a unique replacement name for the source. The service exposes progress descriptions for the individual cutover stages. Microsoft documentation.\nApplicability\nUse this review when the inventory and transfer work has reached an approved identity-handoff decision. Identify both computers, their intended final names, and the users and applications that must reach the destination.\nDSE recommendation\nPrepare an endpoint worksheet and have a second administrator check it against the migration plan. Name the person who will authorize the handoff and the workload owners who will accept it. Communicate the interruption window and preserve the pre-cutover state needed by the approved recovery procedure. Keep the retained source files under controlled ownership while acceptance remains open.\nVerification\nRecord the reported cutover stages and verify the resulting names and network configuration. Test the actual client paths and application operations selected in advance. Confirm that users reach the intended destination and that the source is handled according to the approved plan. Investigate partial completion before declaring the migration accepted.\nOfficial references\nMicrosoft Learn: How cutover works in Storage Migration Service. Source reviewed September 8, 2026.",
        "content_markdown": "## Source facts\n\nCutover transfers the source computer’s network identity to the destination. Microsoft states that the source retains its files afterward but is no longer available to users and applications. Before cutover, the administrator supplies the destination network configuration and can select a unique replacement name for the source. The service exposes progress descriptions for the individual cutover stages. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/cutover).\n\n## Applicability\n\nUse this review when the inventory and transfer work has reached an approved identity-handoff decision. Identify both computers, their intended final names, and the users and applications that must reach the destination.\n\n## DSE recommendation\n\nPrepare an endpoint worksheet and have a second administrator check it against the migration plan. Name the person who will authorize the handoff and the workload owners who will accept it. Communicate the interruption window and preserve the pre-cutover state needed by the approved recovery procedure. Keep the retained source files under controlled ownership while acceptance remains open.\n\n## Verification\n\nRecord the reported cutover stages and verify the resulting names and network configuration. Test the actual client paths and application operations selected in advance. Confirm that users reach the intended destination and that the source is handled according to the approved plan. Investigate partial completion before declaring the migration accepted.\n\n## Official references\n\n[Microsoft Learn: How cutover works in Storage Migration Service](https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/cutover). 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-026-plan-storage-migration-service-cutover-around-the-server-identity-handoff/",
                "url": "https://update.dsesecurity.com/updates/dse-20260908-026-plan-storage-migration-service-cutover-around-the-server-identity-handoff/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-08"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-026-plan-storage-migration-service-cutover-around-the-server-identity-handoff/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Plan Storage Migration Service cutover around the server identity handoff",
                        "item": "https://update.dsesecurity.com/updates/dse-20260908-026-plan-storage-migration-service-cutover-around-the-server-identity-handoff/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-026-plan-storage-migration-service-cutover-around-the-server-identity-handoff/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260908-026-plan-storage-migration-service-cutover-around-the-server-identity-handoff/",
                "url": "https://update.dsesecurity.com/updates/dse-20260908-026-plan-storage-migration-service-cutover-around-the-server-identity-handoff/",
                "headline": "Plan Storage Migration Service cutover around the server identity handoff",
                "description": "What must be accepted when Storage Migration Service transfers a server identity?",
                "abstract": "What must be accepted when Storage Migration Service transfers a server identity?",
                "articleBody": "Source facts\nCutover transfers the source computer’s network identity to the destination. Microsoft states that the source retains its files afterward but is no longer available to users and applications. Before cutover, the administrator supplies the destination network configuration and can select a unique replacement name for the source. The service exposes progress descriptions for the individual cutover stages. Microsoft documentation.\nApplicability\nUse this review when the inventory and transfer work has reached an approved identity-handoff decision. Identify both computers, their intended final names, and the users and applications that must reach the destination.\nDSE recommendation\nPrepare an endpoint worksheet and have a second administrator check it against the migration plan. Name the person who will authorize the handoff and the workload owners who will accept it. Communicate the interruption window and preserve the pre-cutover state needed by the approved recovery procedure. Keep the retained source files under controlled ownership while acceptance remains open.\nVerification\nRecord the reported cutover stages and verify the resulting names and network configuration. Test the actual client paths and application operations selected in advance. Confirm that users reach the intended destination and that the source is handled according to the approved plan. Investigate partial completion before declaring the migration accepted.\nOfficial references\nMicrosoft Learn: How cutover works in Storage Migration Service. Source reviewed September 8, 2026.",
                "datePublished": "2026-09-08T18:16:45+00:00",
                "dateModified": "2026-09-08T18:17:14+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260908-026-plan-storage-migration-service-cutover-around-the-server-identity-handoff/"
                },
                "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-026-plan-storage-migration-service-cutover-around-the-server-identity-handoff/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Plan Storage Migration Service cutover around the server identity handoff"
                },
                "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": 219,
                "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": "How cutover works in Storage Migration Service",
                    "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/cutover"
                }
            }
        ]
    }
}