{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/raise-rid-pool-after-rollback/", "item": { "id": "https://update.dsesecurity.com/updates/raise-rid-pool-after-rollback/", "slug": "raise-rid-pool-after-rollback", "url": "https://update.dsesecurity.com/updates/raise-rid-pool-after-rollback/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/raise-rid-pool-after-rollback.md", "json": "https://update.dsesecurity.com/api/v1/posts/raise-rid-pool-after-rollback/" }, "title": "Raise the RID pool after rollback to prevent identifier reuse", "summary": "Use AD Forest Recovery - Raising RID pools 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": "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": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "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/" } ], "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:14:26+00:00", "modified_at": "2026-08-27T12:58:58+00:00", "reviewed_on": "2026-08-26", "reading_minutes": 3, "word_count": 507, "potentially_affected": "Teams, systems, services, or facilities within the stated scope of AD Forest Recovery - Raising RID pools", "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": "AD Forest Recovery - Raising RID pools", "url": "https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/forest-recovery-guide/ad-forest-recovery-raise-rid-pool", "published_on": "2025-05-12", "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": "

Keep this document to one review outcome: Raise the RID pool after rollback to prevent identifier reuse. Only the official source and traced locations below supply facts. Confirm applicability before acting.

\n

Source fact:

\n

The official AD Forest Recovery – Raising RID pools from Microsoft supports the following bounded statements:

\n\n

The source support ends with the statements listed above. Use them to examine forest recovery plans, trusted backups, isolated recovery networks, controller rebuild order, credential resets, and validation steps in the applicable environment, not to imply a wider guarantee.

\n

What the source does not establish

\n

Perform RID arithmetic exactly as documented and record the pre- and post-change values. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on offline credentials, Windows DNS, time, virtualization, storage, PKI, network isolation, and authorized recovery personnel and the environment’s recorded constraints.

\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 forest recovery plans, trusted backups, isolated recovery networks, controller rebuild order, credential resets, and validation steps, observed and expected states, owner, and reason for deviation.

\n

Translate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include offline credentials, Windows DNS, time, virtualization, storage, PKI, network isolation, and authorized recovery personnel, while excluding secrets and sensitive personal or topology data from ordinary tickets.

\n

Verification and evidence

\n

Tie each conclusion back to Opening overview; Section: Active Directory RID Pools and rIDAvailablePool and to observable material such as backup manifests, restore logs, isolation proof, recovery timing, role-transfer records, DNS validation, and exercise findings. Preserve provenance and stable identifiers without copying secrets into the evidence set.

\n

Retain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.

\n

Official references

\n", "content_text": "Keep this document to one review outcome: Raise the RID pool after rollback to prevent identifier reuse. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official AD Forest Recovery – Raising RID pools from Microsoft supports the following bounded statements:\n\nRaising available RID pools prevents a restored domain from reallocating a RID used after the backup point. The research record locates this support at Opening overview.\nThe domain-wide RID space is maintained in the RID Manager object’s rIDAvailablePool attribute. The research record locates this support at Section: Active Directory RID Pools and rIDAvailablePool.\n\nThe source support ends with the statements listed above. Use them to examine forest recovery plans, trusted backups, isolated recovery networks, controller rebuild order, credential resets, and validation steps in the applicable environment, not to imply a wider guarantee.\nWhat the source does not establish\nPerform RID arithmetic exactly as documented and record the pre- and post-change values. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on offline credentials, Windows DNS, time, virtualization, storage, PKI, network isolation, and authorized recovery personnel and the environment’s recorded constraints.\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 Section: Active Directory RID Pools and rIDAvailablePool, which observable configuration, record, or test can confirm applicability here?\nWhat inventory proves which parts of forest recovery plans, trusted backups, isolated recovery networks, controller rebuild order, credential resets, and validation steps are in and out of scope?\nWhich condition in offline credentials, Windows DNS, time, virtualization, storage, PKI, network isolation, and authorized recovery personnel 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 forest recovery plans, trusted backups, isolated recovery networks, controller rebuild order, credential resets, and validation steps, observed and expected states, owner, and reason for deviation.\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include offline credentials, Windows DNS, time, virtualization, storage, PKI, network isolation, and authorized recovery personnel, while excluding secrets and sensitive personal or topology data from ordinary tickets.\nVerification and evidence\nTie each conclusion back to Opening overview; Section: Active Directory RID Pools and rIDAvailablePool and to observable material such as backup manifests, restore logs, isolation proof, recovery timing, role-transfer records, DNS validation, and exercise findings. Preserve provenance and stable identifiers without copying secrets into the evidence set.\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\nOfficial references\n\nAD Forest Recovery – Raising RID pools — Microsoft", "content_markdown": "Keep this document to one review outcome: Raise the RID pool after rollback to prevent identifier reuse. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [AD Forest Recovery – Raising RID pools](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/forest-recovery-guide/ad-forest-recovery-raise-rid-pool) from Microsoft supports the following bounded statements:\n\n- Raising available RID pools prevents a restored domain from reallocating a RID used after the backup point. The research record locates this support at Opening overview.\n\n- The domain-wide RID space is maintained in the RID Manager object’s rIDAvailablePool attribute. The research record locates this support at Section: Active Directory RID Pools and rIDAvailablePool.\n\nThe source support ends with the statements listed above. Use them to examine forest recovery plans, trusted backups, isolated recovery networks, controller rebuild order, credential resets, and validation steps in the applicable environment, not to imply a wider guarantee.\n\n## What the source does not establish\n\nPerform RID arithmetic exactly as documented and record the pre- and post-change values. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on offline credentials, Windows DNS, time, virtualization, storage, PKI, network isolation, and authorized recovery personnel and the environment’s recorded constraints.\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 Section: Active Directory RID Pools and rIDAvailablePool, which observable configuration, record, or test can confirm applicability here?\n\n- What inventory proves which parts of forest recovery plans, trusted backups, isolated recovery networks, controller rebuild order, credential resets, and validation steps are in and out of scope?\n\n- Which condition in offline credentials, Windows DNS, time, virtualization, storage, PKI, network isolation, and authorized recovery personnel 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 forest recovery plans, trusted backups, isolated recovery networks, controller rebuild order, credential resets, and validation steps, observed and expected states, owner, and reason for deviation.\n\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include offline credentials, Windows DNS, time, virtualization, storage, PKI, network isolation, and authorized recovery personnel, while excluding secrets and sensitive personal or topology data from ordinary tickets.\n\n## Verification and evidence\n\nTie each conclusion back to Opening overview; Section: Active Directory RID Pools and rIDAvailablePool and to observable material such as backup manifests, restore logs, isolation proof, recovery timing, role-transfer records, DNS validation, and exercise findings. Preserve provenance and stable identifiers without copying secrets into the evidence set.\n\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\n\n## Official references\n\n- [AD Forest Recovery – Raising RID pools](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/forest-recovery-guide/ad-forest-recovery-raise-rid-pool) — 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/raise-rid-pool-after-rollback/", "url": "https://update.dsesecurity.com/updates/raise-rid-pool-after-rollback/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-08-26" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/raise-rid-pool-after-rollback/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Raise the RID pool after rollback to prevent identifier reuse", "item": "https://update.dsesecurity.com/updates/raise-rid-pool-after-rollback/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/raise-rid-pool-after-rollback/#article", "identifier": "https://update.dsesecurity.com/updates/raise-rid-pool-after-rollback/", "url": "https://update.dsesecurity.com/updates/raise-rid-pool-after-rollback/", "headline": "Raise the RID pool after rollback to prevent identifier reuse", "description": "Use AD Forest Recovery - Raising RID pools to review this narrow operational decision without extending the source beyond its stated scope.", "abstract": "Use AD Forest Recovery - Raising RID pools to review this narrow operational decision without extending the source beyond its stated scope.", "articleBody": "Keep this document to one review outcome: Raise the RID pool after rollback to prevent identifier reuse. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official AD Forest Recovery – Raising RID pools from Microsoft supports the following bounded statements:\n\nRaising available RID pools prevents a restored domain from reallocating a RID used after the backup point. The research record locates this support at Opening overview.\nThe domain-wide RID space is maintained in the RID Manager object’s rIDAvailablePool attribute. The research record locates this support at Section: Active Directory RID Pools and rIDAvailablePool.\n\nThe source support ends with the statements listed above. Use them to examine forest recovery plans, trusted backups, isolated recovery networks, controller rebuild order, credential resets, and validation steps in the applicable environment, not to imply a wider guarantee.\nWhat the source does not establish\nPerform RID arithmetic exactly as documented and record the pre- and post-change values. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on offline credentials, Windows DNS, time, virtualization, storage, PKI, network isolation, and authorized recovery personnel and the environment’s recorded constraints.\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 Section: Active Directory RID Pools and rIDAvailablePool, which observable configuration, record, or test can confirm applicability here?\nWhat inventory proves which parts of forest recovery plans, trusted backups, isolated recovery networks, controller rebuild order, credential resets, and validation steps are in and out of scope?\nWhich condition in offline credentials, Windows DNS, time, virtualization, storage, PKI, network isolation, and authorized recovery personnel 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 forest recovery plans, trusted backups, isolated recovery networks, controller rebuild order, credential resets, and validation steps, observed and expected states, owner, and reason for deviation.\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include offline credentials, Windows DNS, time, virtualization, storage, PKI, network isolation, and authorized recovery personnel, while excluding secrets and sensitive personal or topology data from ordinary tickets.\nVerification and evidence\nTie each conclusion back to Opening overview; Section: Active Directory RID Pools and rIDAvailablePool and to observable material such as backup manifests, restore logs, isolation proof, recovery timing, role-transfer records, DNS validation, and exercise findings. Preserve provenance and stable identifiers without copying secrets into the evidence set.\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\nOfficial references\n\nAD Forest Recovery – Raising RID pools — Microsoft", "datePublished": "2026-08-27T12:14:26+00:00", "dateModified": "2026-08-27T12:58:58+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/raise-rid-pool-after-rollback/" }, "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/raise-rid-pool-after-rollback/#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": "Raise the RID pool after rollback to prevent identifier reuse" }, "articleSection": [ "Business Continuity", "IT", "Microsoft 365 & Identity" ], "keywords": [ "Business Continuity", "IT", "Microsoft 365 & Identity", "Playbook", "Advisory priority" ], "genre": "Playbook", "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/" }, { "@type": "Thing", "name": "Microsoft 365 & Identity", "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/" } ], "wordCount": 507, "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": "AD Forest Recovery - Raising RID pools", "url": "https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/forest-recovery-guide/ad-forest-recovery-raise-rid-pool", "datePublished": "2025-05-12" } } ] } }