Celoxocis · February 6, 2018 10:59
diff --git a/RID check b/RID check
 dcdiag /test:ridmanager /v

 danach runter scrollen zu:
 Starting test: RidManager

    * Available RID Pool for the Domain is 2100 to 1073741823
    * NE-DC1.adatum.com is the RID Master
    * DsBind with RID Master was successful
    * rIDAllocationPool is 1600 to 2099
    * rIDPreviousAllocationPool is 1600 to 2099
    * rIDNextRID: 1605
    
 Technet Note:
 RIDs are never recycled, but always incremented. This is because the RID can't be reclaimed after a security principal is deleted.
 Reusing a RID could cause unauthorized access to resources if the access control settings referred to previously issued RIDs. 
 The RID master gives every DC a pool of 500 RIDs at a time. If DC has used all RIDs in its local RID pool and can't obtain a new pool from the RID master, it won't be able to create new security principals.
	dcdiag /test:ridmanager /v

	danach runter scrollen zu:
	Starting test: RidManager

	* Available RID Pool for the Domain is 2100 to 1073741823
	* NE-DC1.adatum.com is the RID Master
	* DsBind with RID Master was successful
	* rIDAllocationPool is 1600 to 2099
	* rIDPreviousAllocationPool is 1600 to 2099
	* rIDNextRID: 1605

	Technet Note:
	RIDs are never recycled, but always incremented. This is because the RID can't be reclaimed after a security principal is deleted.
	Reusing a RID could cause unauthorized access to resources if the access control settings referred to previously issued RIDs.
	The RID master gives every DC a pool of 500 RIDs at a time. If DC has used all RIDs in its local RID pool and can't obtain a new pool from the RID master, it won't be able to create new security principals.