{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/validate-computer-clock-resets-to-a-previous-date-and-time-with-ad-dns-evidence/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/validate-computer-clock-resets-to-a-previous-date-and-time-with-ad-dns-evidence/",
        "slug": "validate-computer-clock-resets-to-a-previous-date-and-time-with-ad-dns-evidence",
        "url": "https://update.dsesecurity.com/updates/validate-computer-clock-resets-to-a-previous-date-and-time-with-ad-dns-evidence/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/validate-computer-clock-resets-to-a-previous-date-and-time-with-ad-dns-evidence.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/validate-computer-clock-resets-to-a-previous-date-and-time-with-ad-dns-evidence/"
        },
        "title": "Validate Computer clock resets to a previous date and time with AD/DNS evidence",
        "summary": "Use Computer clock resets to a previous date and time to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "checklist",
            "name": "Checklist"
        },
        "priority": {
            "slug": "advisory",
            "name": "Advisory"
        },
        "featured": false,
        "image": {
            "theme": "video-evidence",
            "label": "Video evidence & analytics",
            "alt": "Multiple synchronized camera views converging into a verifiable evidence frame.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/video-evidence-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/video-evidence-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/video-evidence-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:00:34+00:00",
        "modified_at": "2026-08-27T17:37:18+00:00",
        "reviewed_on": "2026-08-27",
        "reading_minutes": 3,
        "word_count": 579,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of Computer clock resets to a previous date and time",
        "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": "Computer clock resets to a previous date and time",
            "url": "https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/client-clock-reverts-to-previous-time",
            "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>Treat this document as a focused evidence review: Validate Computer clock resets to a previous date and time with AD/DNS evidence. 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/client-clock-reverts-to-previous-time\" target=\"_blank\" rel=\"noopener noreferrer\">Computer clock resets to a previous date and time</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>At Introduction below H1, Microsoft states: “This article provides workarounds for an issue in which the computer clock resets incorrectly if you restart the computer while it doesn&#8217;t have an internet connection.” The research record locates this support at <strong>Introduction below H1</strong>.</li>\n<li>At Symptoms, Microsoft states: “The system date and time setting on a computer that&#8217;s running Windows 10 or a later version incorrectly resets to a date and time that&#8217;s at least one day in the past.” The research record locates this support at <strong>Symptoms</strong>.</li>\n</ul>\n<p>Keep the evidence boundary at these traced claims. They support a review of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services; they do not support conclusions outside the source&#8217;s stated conditions.</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. No current deployment state or change approval follows from the source alone. Validate Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, and treat examples or options as conditional inputs rather than defaults.</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 owner can attest to the recorded state of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, including exceptions?</li>\n<li>What baseline for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials must accompany the source-specific observation?</li>\n<li>Which success, stop, and escalation criteria are written before testing begins?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>DSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. 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>An implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before and after the test, and store only sanitized operational evidence.</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-412</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/client-clock-reverts-to-previous-time\" target=\"_blank\" rel=\"noopener noreferrer\">Computer clock resets to a previous date and time</a> — Microsoft</li>\n</ul>",
        "content_text": "Treat this document as a focused evidence review: Validate Computer clock resets to a previous date and time with AD/DNS evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Computer clock resets to a previous date and time from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “This article provides workarounds for an issue in which the computer clock resets incorrectly if you restart the computer while it doesn’t have an internet connection.” The research record locates this support at Introduction below H1.\nAt Symptoms, Microsoft states: “The system date and time setting on a computer that’s running Windows 10 or a later version incorrectly resets to a date and time that’s at least one day in the past.” The research record locates this support at Symptoms.\n\nKeep the evidence boundary at these traced claims. They support a review of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services; they do not support conclusions outside the source’s stated conditions.\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. No current deployment state or change approval follows from the source alone. Validate Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, and treat examples or options as conditional inputs rather than defaults.\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 owner can attest to the recorded state of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, including exceptions?\nWhat baseline for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials must accompany the source-specific observation?\nWhich success, stop, and escalation criteria are written before testing begins?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. 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.\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before and after the test, and store only sanitized operational evidence.\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-412 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\nComputer clock resets to a previous date and time — Microsoft",
        "content_markdown": "Treat this document as a focused evidence review: Validate Computer clock resets to a previous date and time with AD/DNS evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [Computer clock resets to a previous date and time](https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/client-clock-reverts-to-previous-time) from Microsoft supports the following bounded statements:\n\n- At Introduction below H1, Microsoft states: “This article provides workarounds for an issue in which the computer clock resets incorrectly if you restart the computer while it doesn’t have an internet connection.” The research record locates this support at Introduction below H1.\n\n- At Symptoms, Microsoft states: “The system date and time setting on a computer that’s running Windows 10 or a later version incorrectly resets to a date and time that’s at least one day in the past.” The research record locates this support at Symptoms.\n\nKeep the evidence boundary at these traced claims. They support a review of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services; they do not support conclusions outside the source’s stated conditions.\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. No current deployment state or change approval follows from the source alone. Validate Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, and treat examples or options as conditional inputs rather than defaults.\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 owner can attest to the recorded state of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, including exceptions?\n\n- What baseline for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials must accompany the source-specific observation?\n\n- Which success, stop, and escalation criteria are written before testing begins?\n\n## DSE recommendation:\n\nDSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. 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\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before and after the test, and store only sanitized operational evidence.\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-412 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- [Computer clock resets to a previous date and time](https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/client-clock-reverts-to-previous-time) — 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/validate-computer-clock-resets-to-a-previous-date-and-time-with-ad-dns-evidence/",
                "url": "https://update.dsesecurity.com/updates/validate-computer-clock-resets-to-a-previous-date-and-time-with-ad-dns-evidence/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-27"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/validate-computer-clock-resets-to-a-previous-date-and-time-with-ad-dns-evidence/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Validate Computer clock resets to a previous date and time with AD/DNS evidence",
                        "item": "https://update.dsesecurity.com/updates/validate-computer-clock-resets-to-a-previous-date-and-time-with-ad-dns-evidence/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/validate-computer-clock-resets-to-a-previous-date-and-time-with-ad-dns-evidence/#article",
                "identifier": "https://update.dsesecurity.com/updates/validate-computer-clock-resets-to-a-previous-date-and-time-with-ad-dns-evidence/",
                "url": "https://update.dsesecurity.com/updates/validate-computer-clock-resets-to-a-previous-date-and-time-with-ad-dns-evidence/",
                "headline": "Validate Computer clock resets to a previous date and time with AD/DNS evidence",
                "description": "Use Computer clock resets to a previous date and time to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use Computer clock resets to a previous date and time to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Treat this document as a focused evidence review: Validate Computer clock resets to a previous date and time with AD/DNS evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Computer clock resets to a previous date and time from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “This article provides workarounds for an issue in which the computer clock resets incorrectly if you restart the computer while it doesn’t have an internet connection.” The research record locates this support at Introduction below H1.\nAt Symptoms, Microsoft states: “The system date and time setting on a computer that’s running Windows 10 or a later version incorrectly resets to a date and time that’s at least one day in the past.” The research record locates this support at Symptoms.\n\nKeep the evidence boundary at these traced claims. They support a review of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services; they do not support conclusions outside the source’s stated conditions.\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. No current deployment state or change approval follows from the source alone. Validate Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, and treat examples or options as conditional inputs rather than defaults.\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 owner can attest to the recorded state of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, including exceptions?\nWhat baseline for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials must accompany the source-specific observation?\nWhich success, stop, and escalation criteria are written before testing begins?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. 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.\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before and after the test, and store only sanitized operational evidence.\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-412 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\nComputer clock resets to a previous date and time — Microsoft",
                "datePublished": "2026-08-27T17:00:34+00:00",
                "dateModified": "2026-08-27T17:37:18+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/validate-computer-clock-resets-to-a-previous-date-and-time-with-ad-dns-evidence/"
                },
                "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/validate-computer-clock-resets-to-a-previous-date-and-time-with-ad-dns-evidence/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/video-evidence-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/video-evidence-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Validate Computer clock resets to a previous date and time with AD/DNS evidence"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure",
                    "Checklist",
                    "Advisory priority"
                ],
                "genre": "Checklist",
                "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": 579,
                "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": "Computer clock resets to a previous date and time",
                    "url": "https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/client-clock-reverts-to-previous-time"
                }
            }
        ]
    }
}