{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/review-when-you-run-an-ldap-query-against-a-windows-server-2008-based-domain-controller-you-obtain/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/review-when-you-run-an-ldap-query-against-a-windows-server-2008-based-domain-controller-you-obtain/",
        "slug": "review-when-you-run-an-ldap-query-against-a-windows-server-2008-based-domain-controller-you-obtain",
        "url": "https://update.dsesecurity.com/updates/review-when-you-run-an-ldap-query-against-a-windows-server-2008-based-domain-controller-you-obtain/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/review-when-you-run-an-ldap-query-against-a-windows-server-2008-based-domain-controller-you-obtain.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/review-when-you-run-an-ldap-query-against-a-windows-server-2008-based-domain-controller-you-obtain/"
        },
        "title": "Review When you run an LDAP query against a Windows Server 2008-based domain controller, you obtain a partial attribute list",
        "summary": "Use When you run an LDAP query against a Windows Server 2008-based domain controller, you obtain a partial attribute list to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "playbook",
            "name": "Playbook"
        },
        "priority": {
            "slug": "advisory",
            "name": "Advisory"
        },
        "featured": false,
        "image": {
            "theme": "managed-it",
            "label": "Managed IT operations",
            "alt": "A controlled technology lifecycle progressing from assessment to approved production.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/managed-it-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/managed-it-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            },
            {
                "slug": "microsoft-365-identity",
                "name": "Microsoft 365 & Identity",
                "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/"
            },
            {
                "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-08-27T17:01:41+00:00",
        "modified_at": "2026-08-27T17:29:41+00:00",
        "reviewed_on": "2026-08-27",
        "reading_minutes": 3,
        "word_count": 601,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of When you run an LDAP query against a Windows Server 2008-based domain controller, you obtain a partial attribute list",
        "dse_recommendation": "Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards.",
        "primary_source": {
            "name": "When you run an LDAP query against a Windows Server 2008-based domain controller, you obtain a partial attribute list",
            "url": "https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/ldap-query-against-domain-controller-partial-attribute",
            "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": "<p>Keep this document to one review outcome: Review When you run an LDAP query against a Windows Server 2008-based domain controller, you obtain a partial attribute list. Only the official source and traced locations below supply facts. Confirm applicability before acting.</p>\n<h2>Source fact:</h2>\n<p>The official <a href=\"https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/ldap-query-against-domain-controller-partial-attribute\" target=\"_blank\" rel=\"noopener noreferrer\">When you run an LDAP query against a Windows Server 2008-based domain controller, you obtain a partial attribute list</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>At Introduction below H1, Microsoft states: “This article provides workarounds for the issue when you run an LDAP query against a domain controller, you obtain a partial attribute list.” The research record locates this support at <strong>Introduction below H1</strong>.</li>\n<li>At Symptoms, Microsoft states: “When you run a Lightweight Directory Access Protocol (LDAP) request against a Windows Server 2008-based domain controller, you obtain a partial attribute list.” The research record locates this support at <strong>Symptoms</strong>.</li>\n</ul>\n<p>The source support ends with the statements listed above. Use them to examine Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services in the applicable environment, not to imply a wider guarantee.</p>\n<h2>What the source does not establish</h2>\n<p>The cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials and the environment&#8217;s recorded constraints.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>Introduction below H1</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>Symptoms</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Which deployed instance of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services will be compared with the source, and why that instance?</li>\n<li>How will the review distinguish a source mismatch from a failure in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials?</li>\n<li>Who approves the conclusion, exception, test window, and rollback threshold?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>DSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.</p>\n<p>If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials and sanitize protected material before retention.</p>\n<h2>Verification and evidence</h2>\n<p>Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations <strong>Introduction below H1</strong>; <strong>Symptoms</strong>. Favor sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state, linked to stable identifiers, time, and operator.</p>\n<p>Label this evidence set <strong>DSE-20260827-345</strong> so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.</p>\n<p>Preserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/ldap-query-against-domain-controller-partial-attribute\" target=\"_blank\" rel=\"noopener noreferrer\">When you run an LDAP query against a Windows Server 2008-based domain controller, you obtain a partial attribute list</a> — Microsoft</li>\n</ul>",
        "content_text": "Keep this document to one review outcome: Review When you run an LDAP query against a Windows Server 2008-based domain controller, you obtain a partial attribute list. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official When you run an LDAP query against a Windows Server 2008-based domain controller, you obtain a partial attribute list from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “This article provides workarounds for the issue when you run an LDAP query against a domain controller, you obtain a partial attribute list.” The research record locates this support at Introduction below H1.\nAt Symptoms, Microsoft states: “When you run a Lightweight Directory Access Protocol (LDAP) request against a Windows Server 2008-based domain controller, you obtain a partial attribute list.” The research record locates this support at Symptoms.\n\nThe source support ends with the statements listed above. Use them to examine Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services in the applicable environment, not to imply a wider guarantee.\nWhat the source does not establish\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials and the environment’s recorded constraints.\nApplicability questions\n\nFor source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Symptoms, which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services will be compared with the source, and why that instance?\nHow will the review distinguish a source mismatch from a failure in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials?\nWho approves the conclusion, exception, test window, and rollback threshold?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials and sanitize protected material before retention.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Introduction below H1; Symptoms. Favor sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state, linked to stable identifiers, time, and operator.\nLabel this evidence set DSE-20260827-345 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\nOfficial references\n\nWhen you run an LDAP query against a Windows Server 2008-based domain controller, you obtain a partial attribute list — Microsoft",
        "content_markdown": "Keep this document to one review outcome: Review When you run an LDAP query against a Windows Server 2008-based domain controller, you obtain a partial attribute list. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [When you run an LDAP query against a Windows Server 2008-based domain controller, you obtain a partial attribute list](https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/ldap-query-against-domain-controller-partial-attribute) from Microsoft supports the following bounded statements:\n\n- At Introduction below H1, Microsoft states: “This article provides workarounds for the issue when you run an LDAP query against a domain controller, you obtain a partial attribute list.” The research record locates this support at Introduction below H1.\n\n- At Symptoms, Microsoft states: “When you run a Lightweight Directory Access Protocol (LDAP) request against a Windows Server 2008-based domain controller, you obtain a partial attribute list.” The research record locates this support at Symptoms.\n\nThe source support ends with the statements listed above. Use them to examine Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services in the applicable environment, not to imply a wider guarantee.\n\n## What the source does not establish\n\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials and the environment’s recorded constraints.\n\n## Applicability questions\n\n- For source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Symptoms, which observable configuration, record, or test can confirm applicability here?\n\n- Which deployed instance of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services will be compared with the source, and why that instance?\n\n- How will the review distinguish a source mismatch from a failure in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials?\n\n- Who approves the conclusion, exception, test window, and rollback threshold?\n\n## DSE recommendation:\n\nDSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.\n\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials and sanitize protected material before retention.\n\n## Verification and evidence\n\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Introduction below H1; Symptoms. Favor sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state, linked to stable identifiers, time, and operator.\n\nLabel this evidence set DSE-20260827-345 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\n\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\n\n## Official references\n\n- [When you run an LDAP query against a Windows Server 2008-based domain controller, you obtain a partial attribute list](https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/ldap-query-against-domain-controller-partial-attribute) — Microsoft"
    },
    "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/review-when-you-run-an-ldap-query-against-a-windows-server-2008-based-domain-controller-you-obtain/",
                "url": "https://update.dsesecurity.com/updates/review-when-you-run-an-ldap-query-against-a-windows-server-2008-based-domain-controller-you-obtain/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-27"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/review-when-you-run-an-ldap-query-against-a-windows-server-2008-based-domain-controller-you-obtain/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Review When you run an LDAP query against a Windows Server 2008-based domain controller, you obtain a partial attribute list",
                        "item": "https://update.dsesecurity.com/updates/review-when-you-run-an-ldap-query-against-a-windows-server-2008-based-domain-controller-you-obtain/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/review-when-you-run-an-ldap-query-against-a-windows-server-2008-based-domain-controller-you-obtain/#article",
                "identifier": "https://update.dsesecurity.com/updates/review-when-you-run-an-ldap-query-against-a-windows-server-2008-based-domain-controller-you-obtain/",
                "url": "https://update.dsesecurity.com/updates/review-when-you-run-an-ldap-query-against-a-windows-server-2008-based-domain-controller-you-obtain/",
                "headline": "Review When you run an LDAP query against a Windows Server 2008-based domain controller, you obtain a partial attribute list",
                "description": "Use When you run an LDAP query against a Windows Server 2008-based domain controller, you obtain a partial attribute list to review this narrow…",
                "abstract": "Use When you run an LDAP query against a Windows Server 2008-based domain controller, you obtain a partial attribute list to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Keep this document to one review outcome: Review When you run an LDAP query against a Windows Server 2008-based domain controller, you obtain a partial attribute list. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official When you run an LDAP query against a Windows Server 2008-based domain controller, you obtain a partial attribute list from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “This article provides workarounds for the issue when you run an LDAP query against a domain controller, you obtain a partial attribute list.” The research record locates this support at Introduction below H1.\nAt Symptoms, Microsoft states: “When you run a Lightweight Directory Access Protocol (LDAP) request against a Windows Server 2008-based domain controller, you obtain a partial attribute list.” The research record locates this support at Symptoms.\n\nThe source support ends with the statements listed above. Use them to examine Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services in the applicable environment, not to imply a wider guarantee.\nWhat the source does not establish\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials and the environment’s recorded constraints.\nApplicability questions\n\nFor source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Symptoms, which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services will be compared with the source, and why that instance?\nHow will the review distinguish a source mismatch from a failure in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials?\nWho approves the conclusion, exception, test window, and rollback threshold?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials and sanitize protected material before retention.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Introduction below H1; Symptoms. Favor sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state, linked to stable identifiers, time, and operator.\nLabel this evidence set DSE-20260827-345 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\nOfficial references\n\nWhen you run an LDAP query against a Windows Server 2008-based domain controller, you obtain a partial attribute list — Microsoft",
                "datePublished": "2026-08-27T17:01:41+00:00",
                "dateModified": "2026-08-27T17:29:41+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/review-when-you-run-an-ldap-query-against-a-windows-server-2008-based-domain-controller-you-obtain/"
                },
                "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/review-when-you-run-an-ldap-query-against-a-windows-server-2008-based-domain-controller-you-obtain/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Review When you run an LDAP query against a Windows Server 2008-based domain controller, you obtain a partial attribute list"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure",
                    "Playbook",
                    "Advisory priority"
                ],
                "genre": "Playbook",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Microsoft 365 & Identity",
                        "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 601,
                "timeRequired": "PT3M",
                "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": "When you run an LDAP query against a Windows Server 2008-based domain controller, you obtain a partial attribute list",
                    "url": "https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/ldap-query-against-domain-controller-partial-attribute"
                }
            }
        ]
    }
}