Use the ExpandWin2KCapacity procedure of the Managed Active Directory namespace to implement group nesting to circumvent the Windows 2000 Server limitation of 5000 members per group. This implementation handles two types of limits: users per organization and child organizations per organization.
After this call is made, repeated calls to DistributeGroupMemberships must be made until all of the affected groups have had their memberships redistributed. Capacity reduction is not implemented.
This procedure expects to be called with impersonate="1". The procedure impersonates the caller. The procedure must be run as an administrator of the organization.
Important
<request>
<procedure>
<execute namespace="Managed Active Directory" procedure="ExpandWin2KCapacity"
impersonate="1">
<executeData>
<organization>LDAP://ou=Hosting,dc=contoso01,dc=com</organization>
<capacityType>UserN</capacityType>
<multiplier>2</multiplier>
</executeData>
<after source="executeData" destination="data" />
</execute>
</procedure>
</request>
The following input is valid for this request:
Use the <organization> element to specify the Lightweight Directory Access Protocol (LDAP) path of the organization for which you want the capacity multiplier.
<organization>LDAP://LDAP path of the organization</organization>
Use the <capacityType> element to specify the capacity type of the group. Possible values are:
This type is used to limit the users per organization.
This type is used to limit the child organizations per organization.
<capacityType>UserN|ChildOrgN</capacityType>
Use the <multiplier> element to specify the multiplier to be used. The supplied multiplier must be a power of two (2, 4, 8, 16, up to 2048). If the supplied multiplier is not greater than the present multiplier, the call will fail.
<multiplier>multiplier number for the organization</multiplier>
By using the <preferredDomainController> element, you can specify the domain controller that you want to use for this request. Using a single preferred domain controller eliminates replication delays that arise between multiple controllers.
<preferredDomainController>your domain controller</preferredDomainController>
The response to this procedure does not contain significant data.
Important