Getting group capacity expansion information by using XML

Use the GetWin2KCapacityExpansion procedure of the Managed Active Directory namespace to return the current group capacity expansion multiplier for a given organization and capacity type.

This procedure expects to be called with impersonate="1". The procedure impersonates the caller.

Example of a request that calls the GetWin2KCapacityExpansion procedure

<request>
  <procedure>
	<execute namespace="Managed Active Directory" 
		procedure="GetWin2KCapacityExpansion" impersonate="1">
	<executeData>
		<organization>LDAP://ou=Hosting,dc=contoso01,dc=com</organization>
		<capacityType>UserN</capacityType>
	</executeData>
	<after source="executeData" sourcePath="multiplier"
		destination="data"  />
	</execute> 
  </procedure>
</request>

Input for GetWin2KCapacityExpansion

The following input is valid for this request:

LDAP path of the organization
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>
```
Capacity type
Use the <capacityType> element to specify the capacity type of the group. Possible values are:
- UserN
  This type is used to limit the users per organization.
- ChildOrgN
  This type is used to limit the child organizations per organization.

<capacityType>UserN|ChildOrgN</capacityType>

Preferred domain controller (optional)
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>
```

Typical response for GetWin2KCapacityExpansion

This procedure returns the capacity expansion multiplier.

<response>
  <data>
	<multiplier>2</multiplier>
  </data>
</response>

Important

Although Active Directory is not case sensitive for elements such as the Lightweight Directory Access Protocol (LDAP) path, XML is case sensitive. To ensure that the procedure executes appropriately, specify all tags, elements, and data using uppercase and lowercase letters exactly as shown in the XML examples. For additional guidelines on how to use XML, see the Microsoft Web site (http://www.microsoft.com/).