{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-016-register-a-manually-installed-mobility-agent-without-discovery-credentials/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-016-register-a-manually-installed-mobility-agent-without-discovery-credentials/", "slug": "dse-20260909-016-register-a-manually-installed-mobility-agent-without-discovery-credentials", "url": "https://update.dsesecurity.com/updates/dse-20260909-016-register-a-manually-installed-mobility-agent-without-discovery-credentials/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-016-register-a-manually-installed-mobility-agent-without-discovery-credentials.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-016-register-a-manually-installed-mobility-agent-without-discovery-credentials/" }, "title": "Register a manually installed Mobility agent without discovery credentials", "summary": "How should a modernized Site Recovery agent be registered when machine and virtualization discovery credentials cannot be supplied?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "physical-security", "label": "Physical security", "alt": "Integrated video surveillance and controlled entry at a modern commercial facility.", "card_url": "https://update.dsesecurity.com/assets/editorial/physical-security-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/physical-security-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/physical-security-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-10T00:31:40+00:00", "modified_at": "2026-09-10T00:32:00+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 229, "potentially_affected": "Consider this workflow for on-premises VMware or physical-machine protection using the modernized architecture. Establish which appliance should own the registration, and confirm the source operating system and installation permissions before choosing the manual path.", "dse_recommendation": "Document the machine-to-appliance pairing before distributing installation material.", "primary_source": { "name": "About the Mobility service for disaster recovery of VMware VMs and physical servers with Azure Site Recovery - Azure Site Recovery | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/site-recovery/vmware-physical-mobility-service-overview", "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

Modernized Azure Site Recovery offers credential-less discovery when the machine and vCenter or ESXi credentials cannot be provided. This path requires manually installing the Mobility service and enabling its credential-less discovery option. Registration uses a configuration file generated on the chosen appliance from the source machine’s unique details string. The configuration file is then supplied to the agent on that source machine. Microsoft Learn.

\n

Applicability

\n

Consider this workflow for on-premises VMware or physical-machine protection using the modernized architecture. Establish which appliance should own the registration, and confirm the source operating system and installation permissions before choosing the manual path.

\n

DSE recommendation

\n

Document the machine-to-appliance pairing before distributing installation material. Keep each source identifier associated with its own generated configuration file; do not circulate one convenient file as a fleet-wide registration package. Separate approval to install the service from the decision to supply discovery credentials, and record which documented installation mode was selected.

\n

Verification

\n

On a controlled candidate machine, verify the identifier used to generate the file, the intended appliance, and the registration result. Reconcile the registered source with the inventory before enabling replication. Treat a completed software installation as an intermediate checkpoint: do not close onboarding until the correct machine has registered through the chosen workflow.

\n

Official references

\n

Microsoft Learn: About the Mobility service for disaster recovery of VMware VMs and physical servers with Azure Site Recovery.

", "content_text": "Source facts\nModernized Azure Site Recovery offers credential-less discovery when the machine and vCenter or ESXi credentials cannot be provided. This path requires manually installing the Mobility service and enabling its credential-less discovery option. Registration uses a configuration file generated on the chosen appliance from the source machine’s unique details string. The configuration file is then supplied to the agent on that source machine. Microsoft Learn.\nApplicability\nConsider this workflow for on-premises VMware or physical-machine protection using the modernized architecture. Establish which appliance should own the registration, and confirm the source operating system and installation permissions before choosing the manual path.\nDSE recommendation\nDocument the machine-to-appliance pairing before distributing installation material. Keep each source identifier associated with its own generated configuration file; do not circulate one convenient file as a fleet-wide registration package. Separate approval to install the service from the decision to supply discovery credentials, and record which documented installation mode was selected.\nVerification\nOn a controlled candidate machine, verify the identifier used to generate the file, the intended appliance, and the registration result. Reconcile the registered source with the inventory before enabling replication. Treat a completed software installation as an intermediate checkpoint: do not close onboarding until the correct machine has registered through the chosen workflow.\nOfficial references\nMicrosoft Learn: About the Mobility service for disaster recovery of VMware VMs and physical servers with Azure Site Recovery.", "content_markdown": "## Source facts\n\nModernized Azure Site Recovery offers credential-less discovery when the machine and vCenter or ESXi credentials cannot be provided. This path requires manually installing the Mobility service and enabling its credential-less discovery option. Registration uses a configuration file generated on the chosen appliance from the source machine’s unique details string. The configuration file is then supplied to the agent on that source machine. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/site-recovery/vmware-physical-mobility-service-overview).\n\n## Applicability\n\nConsider this workflow for on-premises VMware or physical-machine protection using the modernized architecture. Establish which appliance should own the registration, and confirm the source operating system and installation permissions before choosing the manual path.\n\n## DSE recommendation\n\nDocument the machine-to-appliance pairing before distributing installation material. Keep each source identifier associated with its own generated configuration file; do not circulate one convenient file as a fleet-wide registration package. Separate approval to install the service from the decision to supply discovery credentials, and record which documented installation mode was selected.\n\n## Verification\n\nOn a controlled candidate machine, verify the identifier used to generate the file, the intended appliance, and the registration result. Reconcile the registered source with the inventory before enabling replication. Treat a completed software installation as an intermediate checkpoint: do not close onboarding until the correct machine has registered through the chosen workflow.\n\n## Official references\n\n[Microsoft Learn: About the Mobility service for disaster recovery of VMware VMs and physical servers with Azure Site Recovery](https://learn.microsoft.com/en-us/azure/site-recovery/vmware-physical-mobility-service-overview)." }, "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-20260909-016-register-a-manually-installed-mobility-agent-without-discovery-credentials/", "url": "https://update.dsesecurity.com/updates/dse-20260909-016-register-a-manually-installed-mobility-agent-without-discovery-credentials/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-016-register-a-manually-installed-mobility-agent-without-discovery-credentials/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Register a manually installed Mobility agent without discovery credentials", "item": "https://update.dsesecurity.com/updates/dse-20260909-016-register-a-manually-installed-mobility-agent-without-discovery-credentials/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-016-register-a-manually-installed-mobility-agent-without-discovery-credentials/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-016-register-a-manually-installed-mobility-agent-without-discovery-credentials/", "url": "https://update.dsesecurity.com/updates/dse-20260909-016-register-a-manually-installed-mobility-agent-without-discovery-credentials/", "headline": "Register a manually installed Mobility agent without discovery credentials", "description": "How should a modernized Site Recovery agent be registered when machine and virtualization discovery credentials cannot be supplied?", "abstract": "How should a modernized Site Recovery agent be registered when machine and virtualization discovery credentials cannot be supplied?", "articleBody": "Source facts\nModernized Azure Site Recovery offers credential-less discovery when the machine and vCenter or ESXi credentials cannot be provided. This path requires manually installing the Mobility service and enabling its credential-less discovery option. Registration uses a configuration file generated on the chosen appliance from the source machine’s unique details string. The configuration file is then supplied to the agent on that source machine. Microsoft Learn.\nApplicability\nConsider this workflow for on-premises VMware or physical-machine protection using the modernized architecture. Establish which appliance should own the registration, and confirm the source operating system and installation permissions before choosing the manual path.\nDSE recommendation\nDocument the machine-to-appliance pairing before distributing installation material. Keep each source identifier associated with its own generated configuration file; do not circulate one convenient file as a fleet-wide registration package. Separate approval to install the service from the decision to supply discovery credentials, and record which documented installation mode was selected.\nVerification\nOn a controlled candidate machine, verify the identifier used to generate the file, the intended appliance, and the registration result. Reconcile the registered source with the inventory before enabling replication. Treat a completed software installation as an intermediate checkpoint: do not close onboarding until the correct machine has registered through the chosen workflow.\nOfficial references\nMicrosoft Learn: About the Mobility service for disaster recovery of VMware VMs and physical servers with Azure Site Recovery.", "datePublished": "2026-09-10T00:31:40+00:00", "dateModified": "2026-09-10T00:32:00+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-016-register-a-manually-installed-mobility-agent-without-discovery-credentials/" }, "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-20260909-016-register-a-manually-installed-mobility-agent-without-discovery-credentials/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Register a manually installed Mobility agent without discovery credentials" }, "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": 229, "timeRequired": "PT2M", "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": "About the Mobility service for disaster recovery of VMware VMs and physical servers with Azure Site Recovery - Azure Site Recovery | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/site-recovery/vmware-physical-mobility-service-overview" } } ] } }