{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-248-choose-hyper-v-import-identity-and-running-file-locations/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-248-choose-hyper-v-import-identity-and-running-file-locations/", "slug": "dse-20260908-248-choose-hyper-v-import-identity-and-running-file-locations", "url": "https://update.dsesecurity.com/updates/dse-20260908-248-choose-hyper-v-import-identity-and-running-file-locations/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-248-choose-hyper-v-import-identity-and-running-file-locations.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-248-choose-hyper-v-import-identity-and-running-file-locations/" }, "title": "Choose Hyper-V import identity and running-file locations", "summary": "When should an imported virtual machine keep its identity or receive a new one?", "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:13:03+00:00", "modified_at": "2026-09-08T18:29:34+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 217, "potentially_affected": "Operators importing exported Hyper-V virtual machines into a host.", "dse_recommendation": "Write down the intended identity relationship between the original and imported machine, along with the final configuration and disk locations.", "primary_source": { "name": "Export and import virtual machines", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/Export-and-import-virtual-machines", "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

Registering a virtual machine in place preserves its identity and turns the export location into its running-file location. The copy import option lets the operator choose a file location and assigns a new virtual-machine identity, allowing repeated imports to the same host. Microsoft Learn.

\n

Applicability

\n

Decide whether the request is to register an existing workload or create a separate copy before choosing the import type. Identify any already-registered instance. Treat the export directory as potentially live storage until the selected import behavior is understood.

\n

DSE recommendation

\n

Write down the intended identity relationship between the original and imported machine, along with the final configuration and disk locations. Keep the source export under change control while the choice is reviewed. For a separate test copy, plan its network isolation and application identity handling with the workload owner. Do not remove an existing registration merely to clear an import error without that owner’s approval.

\n

Verification

\n

Inspect the imported machine identifier and all attached disk paths before starting it. Confirm that the running-file locations match the chosen import type. Mark any export directory now serving as live storage so it is not cleaned up as disposable transfer material. Start the workload only in its approved network context.

\n

Official references

\n

Microsoft Learn: Export and import virtual machines. Source reviewed September 8, 2026.

", "content_text": "Source facts\nRegistering a virtual machine in place preserves its identity and turns the export location into its running-file location. The copy import option lets the operator choose a file location and assigns a new virtual-machine identity, allowing repeated imports to the same host. Microsoft Learn.\nApplicability\nDecide whether the request is to register an existing workload or create a separate copy before choosing the import type. Identify any already-registered instance. Treat the export directory as potentially live storage until the selected import behavior is understood.\nDSE recommendation\nWrite down the intended identity relationship between the original and imported machine, along with the final configuration and disk locations. Keep the source export under change control while the choice is reviewed. For a separate test copy, plan its network isolation and application identity handling with the workload owner. Do not remove an existing registration merely to clear an import error without that owner’s approval.\nVerification\nInspect the imported machine identifier and all attached disk paths before starting it. Confirm that the running-file locations match the chosen import type. Mark any export directory now serving as live storage so it is not cleaned up as disposable transfer material. Start the workload only in its approved network context.\nOfficial references\nMicrosoft Learn: Export and import virtual machines. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nRegistering a virtual machine in place preserves its identity and turns the export location into its running-file location. The copy import option lets the operator choose a file location and assigns a new virtual-machine identity, allowing repeated imports to the same host. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/Export-and-import-virtual-machines).\n\n## Applicability\n\nDecide whether the request is to register an existing workload or create a separate copy before choosing the import type. Identify any already-registered instance. Treat the export directory as potentially live storage until the selected import behavior is understood.\n\n## DSE recommendation\n\nWrite down the intended identity relationship between the original and imported machine, along with the final configuration and disk locations. Keep the source export under change control while the choice is reviewed. For a separate test copy, plan its network isolation and application identity handling with the workload owner. Do not remove an existing registration merely to clear an import error without that owner’s approval.\n\n## Verification\n\nInspect the imported machine identifier and all attached disk paths before starting it. Confirm that the running-file locations match the chosen import type. Mark any export directory now serving as live storage so it is not cleaned up as disposable transfer material. Start the workload only in its approved network context.\n\n## Official references\n\n[Microsoft Learn: Export and import virtual machines](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/Export-and-import-virtual-machines). 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-248-choose-hyper-v-import-identity-and-running-file-locations/", "url": "https://update.dsesecurity.com/updates/dse-20260908-248-choose-hyper-v-import-identity-and-running-file-locations/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-248-choose-hyper-v-import-identity-and-running-file-locations/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Choose Hyper-V import identity and running-file locations", "item": "https://update.dsesecurity.com/updates/dse-20260908-248-choose-hyper-v-import-identity-and-running-file-locations/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-248-choose-hyper-v-import-identity-and-running-file-locations/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-248-choose-hyper-v-import-identity-and-running-file-locations/", "url": "https://update.dsesecurity.com/updates/dse-20260908-248-choose-hyper-v-import-identity-and-running-file-locations/", "headline": "Choose Hyper-V import identity and running-file locations", "description": "When should an imported virtual machine keep its identity or receive a new one?", "abstract": "When should an imported virtual machine keep its identity or receive a new one?", "articleBody": "Source facts\nRegistering a virtual machine in place preserves its identity and turns the export location into its running-file location. The copy import option lets the operator choose a file location and assigns a new virtual-machine identity, allowing repeated imports to the same host. Microsoft Learn.\nApplicability\nDecide whether the request is to register an existing workload or create a separate copy before choosing the import type. Identify any already-registered instance. Treat the export directory as potentially live storage until the selected import behavior is understood.\nDSE recommendation\nWrite down the intended identity relationship between the original and imported machine, along with the final configuration and disk locations. Keep the source export under change control while the choice is reviewed. For a separate test copy, plan its network isolation and application identity handling with the workload owner. Do not remove an existing registration merely to clear an import error without that owner’s approval.\nVerification\nInspect the imported machine identifier and all attached disk paths before starting it. Confirm that the running-file locations match the chosen import type. Mark any export directory now serving as live storage so it is not cleaned up as disposable transfer material. Start the workload only in its approved network context.\nOfficial references\nMicrosoft Learn: Export and import virtual machines. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:13:03+00:00", "dateModified": "2026-09-08T18:29:34+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-248-choose-hyper-v-import-identity-and-running-file-locations/" }, "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-248-choose-hyper-v-import-identity-and-running-file-locations/#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": "Choose Hyper-V import identity and running-file locations" }, "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": 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": "Export and import virtual machines", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/Export-and-import-virtual-machines" } } ] } }