{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-239-check-both-ends-of-a-hyper-v-integration-service/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260908-239-check-both-ends-of-a-hyper-v-integration-service/",
        "slug": "dse-20260908-239-check-both-ends-of-a-hyper-v-integration-service",
        "url": "https://update.dsesecurity.com/updates/dse-20260908-239-check-both-ends-of-a-hyper-v-integration-service/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260908-239-check-both-ends-of-a-hyper-v-integration-service.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-239-check-both-ends-of-a-hyper-v-integration-service/"
        },
        "title": "Check both ends of a Hyper-V integration service",
        "summary": "Why can an integration feature remain unavailable when its host setting is enabled?",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "featured": false,
        "image": {
            "theme": "continuity-recovery",
            "label": "Continuity & recovery",
            "alt": "Paired infrastructure paths converging on a stable recovered service.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-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:12+00:00",
        "modified_at": "2026-09-08T18:29:34+00:00",
        "reviewed_on": "2026-09-08",
        "reading_minutes": 2,
        "word_count": 231,
        "potentially_affected": "Operators managing integration services in supported Windows or Linux Hyper-V guests.",
        "dse_recommendation": "Ask the workload owner which integration functions the guest requires.",
        "primary_source": {
            "name": "Manage Hyper-V Integration Services",
            "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/Manage-Hyper-V-integration-services",
            "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>Hyper-V integration services coordinate functions between the host and guest operating systems; the individual services can be controlled separately. For a service to function fully, its host-side setting must be enabled and the corresponding service must run inside the guest. Microsoft recommends controlling integration services from Hyper-V. Outdated guest integration services can prevent features from working correctly; Microsoft documents checking their Windows version from inside the guest. <a href=\"https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/Manage-Hyper-V-integration-services\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>Use this review for one named integration feature, not as a reason to enable every available service. Identify the guest operating system and its documented service-management method. Separate the virtual machine setting from the service state observed within that guest.</p>\n<h2>DSE recommendation</h2>\n<p>Ask the workload owner which integration functions the guest requires. For a failing function, pair the host setting with the corresponding guest service and version evidence before changing either side. Keep unnecessary services outside the approved scope. If an update or service change is proposed, arrange a guest maintenance window and preserve the previous setting so the owner can reverse that individual change.</p>\n<h2>Verification</h2>\n<p>Exercise the selected function from its normal management path. Record the host enablement state, guest service state, guest integration version, and observed result together. If the result still fails, retain the two-sided evidence for investigation rather than repeatedly toggling unrelated integration features.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/Manage-Hyper-V-integration-services\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Manage Hyper-V Integration Services</a>. Source reviewed September 8, 2026.</p>",
        "content_text": "Source facts\nHyper-V integration services coordinate functions between the host and guest operating systems; the individual services can be controlled separately. For a service to function fully, its host-side setting must be enabled and the corresponding service must run inside the guest. Microsoft recommends controlling integration services from Hyper-V. Outdated guest integration services can prevent features from working correctly; Microsoft documents checking their Windows version from inside the guest. Microsoft Learn.\nApplicability\nUse this review for one named integration feature, not as a reason to enable every available service. Identify the guest operating system and its documented service-management method. Separate the virtual machine setting from the service state observed within that guest.\nDSE recommendation\nAsk the workload owner which integration functions the guest requires. For a failing function, pair the host setting with the corresponding guest service and version evidence before changing either side. Keep unnecessary services outside the approved scope. If an update or service change is proposed, arrange a guest maintenance window and preserve the previous setting so the owner can reverse that individual change.\nVerification\nExercise the selected function from its normal management path. Record the host enablement state, guest service state, guest integration version, and observed result together. If the result still fails, retain the two-sided evidence for investigation rather than repeatedly toggling unrelated integration features.\nOfficial references\nMicrosoft Learn: Manage Hyper-V Integration Services. Source reviewed September 8, 2026.",
        "content_markdown": "## Source facts\n\nHyper-V integration services coordinate functions between the host and guest operating systems; the individual services can be controlled separately. For a service to function fully, its host-side setting must be enabled and the corresponding service must run inside the guest. Microsoft recommends controlling integration services from Hyper-V. Outdated guest integration services can prevent features from working correctly; Microsoft documents checking their Windows version from inside the guest. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/Manage-Hyper-V-integration-services).\n\n## Applicability\n\nUse this review for one named integration feature, not as a reason to enable every available service. Identify the guest operating system and its documented service-management method. Separate the virtual machine setting from the service state observed within that guest.\n\n## DSE recommendation\n\nAsk the workload owner which integration functions the guest requires. For a failing function, pair the host setting with the corresponding guest service and version evidence before changing either side. Keep unnecessary services outside the approved scope. If an update or service change is proposed, arrange a guest maintenance window and preserve the previous setting so the owner can reverse that individual change.\n\n## Verification\n\nExercise the selected function from its normal management path. Record the host enablement state, guest service state, guest integration version, and observed result together. If the result still fails, retain the two-sided evidence for investigation rather than repeatedly toggling unrelated integration features.\n\n## Official references\n\n[Microsoft Learn: Manage Hyper-V Integration Services](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/Manage-Hyper-V-integration-services). 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-239-check-both-ends-of-a-hyper-v-integration-service/",
                "url": "https://update.dsesecurity.com/updates/dse-20260908-239-check-both-ends-of-a-hyper-v-integration-service/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-08"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-239-check-both-ends-of-a-hyper-v-integration-service/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Check both ends of a Hyper-V integration service",
                        "item": "https://update.dsesecurity.com/updates/dse-20260908-239-check-both-ends-of-a-hyper-v-integration-service/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260908-239-check-both-ends-of-a-hyper-v-integration-service/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260908-239-check-both-ends-of-a-hyper-v-integration-service/",
                "url": "https://update.dsesecurity.com/updates/dse-20260908-239-check-both-ends-of-a-hyper-v-integration-service/",
                "headline": "Check both ends of a Hyper-V integration service",
                "description": "Why can an integration feature remain unavailable when its host setting is enabled?",
                "abstract": "Why can an integration feature remain unavailable when its host setting is enabled?",
                "articleBody": "Source facts\nHyper-V integration services coordinate functions between the host and guest operating systems; the individual services can be controlled separately. For a service to function fully, its host-side setting must be enabled and the corresponding service must run inside the guest. Microsoft recommends controlling integration services from Hyper-V. Outdated guest integration services can prevent features from working correctly; Microsoft documents checking their Windows version from inside the guest. Microsoft Learn.\nApplicability\nUse this review for one named integration feature, not as a reason to enable every available service. Identify the guest operating system and its documented service-management method. Separate the virtual machine setting from the service state observed within that guest.\nDSE recommendation\nAsk the workload owner which integration functions the guest requires. For a failing function, pair the host setting with the corresponding guest service and version evidence before changing either side. Keep unnecessary services outside the approved scope. If an update or service change is proposed, arrange a guest maintenance window and preserve the previous setting so the owner can reverse that individual change.\nVerification\nExercise the selected function from its normal management path. Record the host enablement state, guest service state, guest integration version, and observed result together. If the result still fails, retain the two-sided evidence for investigation rather than repeatedly toggling unrelated integration features.\nOfficial references\nMicrosoft Learn: Manage Hyper-V Integration Services. Source reviewed September 8, 2026.",
                "datePublished": "2026-09-08T18:13:12+00:00",
                "dateModified": "2026-09-08T18:29:34+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260908-239-check-both-ends-of-a-hyper-v-integration-service/"
                },
                "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-239-check-both-ends-of-a-hyper-v-integration-service/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Check both ends of a Hyper-V integration service"
                },
                "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": 231,
                "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": "Manage Hyper-V Integration Services",
                    "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/Manage-Hyper-V-integration-services"
                }
            }
        ]
    }
}