{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/capture-adac-actions-as-reusable-powershell/", "item": { "id": "https://update.dsesecurity.com/updates/capture-adac-actions-as-reusable-powershell/", "slug": "capture-adac-actions-as-reusable-powershell", "url": "https://update.dsesecurity.com/updates/capture-adac-actions-as-reusable-powershell/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/capture-adac-actions-as-reusable-powershell.md", "json": "https://update.dsesecurity.com/api/v1/posts/capture-adac-actions-as-reusable-powershell/" }, "title": "Capture AD Administrative Center actions as reusable PowerShell", "summary": "Use Use the Active Directory Administrative Center Windows PowerShell History Viewer in Windows Server to review this narrow operational decision without extending the source beyond its stated scope.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "advisory", "name": "Advisory" }, "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": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "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-27T12:15:17+00:00", "modified_at": "2026-08-27T12:56:25+00:00", "reviewed_on": "2026-08-26", "reading_minutes": 3, "word_count": 497, "potentially_affected": "Teams, systems, services, or facilities within the stated scope of Use the Active Directory Administrative Center Windows PowerShell History Viewer in Windows Server", "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": "Use the Active Directory Administrative Center Windows PowerShell History Viewer in Windows Server", "url": "https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/get-started/adac/use-active-directory-administrative-center-powershell-history", "published_on": "2024-09-05", "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": "

Use this document to connect an official requirement or behavior to observable evidence: Capture AD Administrative Center actions as reusable PowerShell. Only the official source and traced locations below supply facts. Confirm applicability before acting.

\n

Source fact:

\n

The official Use the Active Directory Administrative Center Windows PowerShell History Viewer in Windows Server from Microsoft supports the following bounded statements:

\n\n

The source support ends with the statements listed above. Use them to examine forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles in the applicable environment, not to imply a wider guarantee.

\n

What the source does not establish

\n

Recorded commands still require review, least privilege, and testing before automation. No current deployment state or change approval follows from the source alone. Validate Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity, and treat examples or options as conditional inputs rather than defaults.

\n

Applicability questions

\n\n

DSE recommendation:

\n

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 forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles, observed and expected states, owner, and reason for deviation.

\n

Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity. Handle credentials, keys, recovery data, and personal information through approved secure channels.

\n

Verification and evidence

\n

Tie each conclusion back to Opening overview; Opening overview and to observable material such as directory and policy exports, replication and locator tests, event logs, trust state, role ownership, and controlled authentication tests. Preserve provenance and stable identifiers without copying secrets into the evidence set.

\n

Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.

\n

Official references

\n", "content_text": "Use this document to connect an official requirement or behavior to observable evidence: Capture AD Administrative Center actions as reusable PowerShell. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Use the Active Directory Administrative Center Windows PowerShell History Viewer in Windows Server from Microsoft supports the following bounded statements:\n\nAD Administrative Center records the PowerShell cmdlets it runs together with arguments and values. The research record locates this support at Opening overview.\nAdministrators can copy and filter the history for learning, modification, and reuse. The research record locates this support at Opening overview.\n\nThe source support ends with the statements listed above. Use them to examine forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles in the applicable environment, not to imply a wider guarantee.\nWhat the source does not establish\nRecorded commands still require review, least privilege, and testing before automation. No current deployment state or change approval follows from the source alone. Validate Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity, and treat examples or options as conditional inputs rather than defaults.\nApplicability questions\n\nFor source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Opening overview, which observable configuration, record, or test can confirm applicability here?\nWhat inventory proves which parts of forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles are in and out of scope?\nWhich condition in Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity must be healthy before evidence is trustworthy?\nWhat result would disprove the working assumption and return the issue to the owner?\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 forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles, observed and expected states, owner, and reason for deviation.\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nTie each conclusion back to Opening overview; Opening overview and to observable material such as directory and policy exports, replication and locator tests, event logs, trust state, role ownership, and controlled authentication tests. Preserve provenance and stable identifiers without copying secrets into the evidence set.\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\nOfficial references\n\nUse the Active Directory Administrative Center Windows PowerShell History Viewer in Windows Server — Microsoft", "content_markdown": "Use this document to connect an official requirement or behavior to observable evidence: Capture AD Administrative Center actions as reusable PowerShell. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [Use the Active Directory Administrative Center Windows PowerShell History Viewer in Windows Server](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/get-started/adac/use-active-directory-administrative-center-powershell-history) from Microsoft supports the following bounded statements:\n\n- AD Administrative Center records the PowerShell cmdlets it runs together with arguments and values. The research record locates this support at Opening overview.\n\n- Administrators can copy and filter the history for learning, modification, and reuse. The research record locates this support at Opening overview.\n\nThe source support ends with the statements listed above. Use them to examine forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles in the applicable environment, not to imply a wider guarantee.\n\n## What the source does not establish\n\nRecorded commands still require review, least privilege, and testing before automation. No current deployment state or change approval follows from the source alone. Validate Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity, and treat examples or options as conditional inputs rather than defaults.\n\n## Applicability questions\n\n- For source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Opening overview, which observable configuration, record, or test can confirm applicability here?\n\n- What inventory proves which parts of forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles are in and out of scope?\n\n- Which condition in Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity must be healthy before evidence is trustworthy?\n\n- What result would disprove the working assumption and return the issue to the owner?\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 forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles, observed and expected states, owner, and reason for deviation.\n\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity. Handle credentials, keys, recovery data, and personal information through approved secure channels.\n\n## Verification and evidence\n\nTie each conclusion back to Opening overview; Opening overview and to observable material such as directory and policy exports, replication and locator tests, event logs, trust state, role ownership, and controlled authentication tests. Preserve provenance and stable identifiers without copying secrets into the evidence set.\n\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\n\n## Official references\n\n- [Use the Active Directory Administrative Center Windows PowerShell History Viewer in Windows Server](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/get-started/adac/use-active-directory-administrative-center-powershell-history) — 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/capture-adac-actions-as-reusable-powershell/", "url": "https://update.dsesecurity.com/updates/capture-adac-actions-as-reusable-powershell/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-08-26" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/capture-adac-actions-as-reusable-powershell/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Capture AD Administrative Center actions as reusable PowerShell", "item": "https://update.dsesecurity.com/updates/capture-adac-actions-as-reusable-powershell/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/capture-adac-actions-as-reusable-powershell/#article", "identifier": "https://update.dsesecurity.com/updates/capture-adac-actions-as-reusable-powershell/", "url": "https://update.dsesecurity.com/updates/capture-adac-actions-as-reusable-powershell/", "headline": "Capture AD Administrative Center actions as reusable PowerShell", "description": "Use Use the Active Directory Administrative Center Windows PowerShell History Viewer in Windows Server to review this narrow operational decision…", "abstract": "Use Use the Active Directory Administrative Center Windows PowerShell History Viewer in Windows Server to review this narrow operational decision without extending the source beyond its stated scope.", "articleBody": "Use this document to connect an official requirement or behavior to observable evidence: Capture AD Administrative Center actions as reusable PowerShell. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Use the Active Directory Administrative Center Windows PowerShell History Viewer in Windows Server from Microsoft supports the following bounded statements:\n\nAD Administrative Center records the PowerShell cmdlets it runs together with arguments and values. The research record locates this support at Opening overview.\nAdministrators can copy and filter the history for learning, modification, and reuse. The research record locates this support at Opening overview.\n\nThe source support ends with the statements listed above. Use them to examine forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles in the applicable environment, not to imply a wider guarantee.\nWhat the source does not establish\nRecorded commands still require review, least privilege, and testing before automation. No current deployment state or change approval follows from the source alone. Validate Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity, and treat examples or options as conditional inputs rather than defaults.\nApplicability questions\n\nFor source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Opening overview, which observable configuration, record, or test can confirm applicability here?\nWhat inventory proves which parts of forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles are in and out of scope?\nWhich condition in Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity must be healthy before evidence is trustworthy?\nWhat result would disprove the working assumption and return the issue to the owner?\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 forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles, observed and expected states, owner, and reason for deviation.\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nTie each conclusion back to Opening overview; Opening overview and to observable material such as directory and policy exports, replication and locator tests, event logs, trust state, role ownership, and controlled authentication tests. Preserve provenance and stable identifiers without copying secrets into the evidence set.\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\nOfficial references\n\nUse the Active Directory Administrative Center Windows PowerShell History Viewer in Windows Server — Microsoft", "datePublished": "2026-08-27T12:15:17+00:00", "dateModified": "2026-08-27T12:56:25+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/capture-adac-actions-as-reusable-powershell/" }, "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/capture-adac-actions-as-reusable-powershell/#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": "Capture AD Administrative Center actions as reusable PowerShell" }, "articleSection": [ "IT", "Microsoft 365 & Identity", "Networks & Infrastructure" ], "keywords": [ "IT", "Microsoft 365 & Identity", "Networks & Infrastructure", "Guide", "Advisory priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@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": 497, "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": "Use the Active Directory Administrative Center Windows PowerShell History Viewer in Windows Server", "url": "https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/get-started/adac/use-active-directory-administrative-center-powershell-history", "datePublished": "2024-09-05" } } ] } }