You cannot create users, computers, or groups in a domain that has exhausted its global RID pool

Vrijedi za: Windows Server 2019Windows Server 2016Windows Server 2012 R2

Symptoms


Assume that the global relative identifier (RID) pool in a very large forest that contains millions of objects is exhausted. In this situation, you cannot create security principals on any domain controller that has also exhausted its local RID pool. For example, you cannot create users, computers, or groups.

Note When the RID pool is exhausted, you do not receive warnings, and no logs are logged on the domain controller.

This hotfix adds the ability to unlock the 31st bit to expand the size of the global RID pool to 2 billion objects. Support of expanding the size of the global RID pool to 2 billion objects is included in the RTM release of Windows Server 2012, 2012 R2, 2016, 2019 and later versions.

Cause


This issue occurs because only 30 bits of RID are available.

Resolution


To resolve this issue, install the latest monthly update that is released after (September 2016, KB3185278) on the domain controller, and then unlock the thirty-first bit of RID. To do this, follow these steps:
  1. On the domain controller, click Start, click Run, type ldp.exe, and then click OK.
  2. On the Connection menu, click Connect, and then connect locally by using an enterprise administrator account.
  3. Click Modify on the Browse menu.
  4. Change the sidCompatibilityVersion attribute to 1 by adding the following entry to the Edit Entry Attribute box:
    [Add] sidCompatibilityVersion: 1
  5. Press Enter, and then click Run.
Notes
  • When you unlock the thirty-first bit of RID, the RID pool-size limit expands to two billion.
  • To configure the RID pool-size limit, edit the RID block size value on the domain controller under the following registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\RID Values\

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Registry information

To apply the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

 

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.