Adding IIS resources by using XML

Use the AddIISResources procedure of the IIS Resource Manager namespace to add IIS disk volumes, IP addresses, and possibly an computer running IIS to the pool of resources managed by IIS Resource Manager. If the computer running IIS specified by <serverName> does not exist, it will be added.

The HTTP and FTP ports of each IP address are tracked separately, but they are always added and removed from the resource pool as a single IP address. When volumes are added, the system creates a special hosting directory in each volume and applies appropriate permissions.

This procedure runs as the Microsoft Provisioning Framework service account for calls to the Resource Manager database, and it impersonates the caller when creating directories and when creating and setting Web and FTP site permissions.

Important

To run this procedure, you must be a member of the Domain Admins group or the local Administrators group on the server that is being provisioned.

Example of a request that calls the AddIISResources procedure

<<request>
 <procedure>
   <execute namespace="IIS Resource Manager" procedure="AddIISResources">
	 <executeData>
	 <owner>LDAP://ou=Hosting,dc=contoso,dc=com</owner>
	 <servers>
		 <server>
		 <serverName>machine01</serverName>
		 <volumes>
			 <volume>
			 <location>c:</location>
			 <megabytes>30000</megabytes>
			 </volume>
		 <volume>
			<location>d:</location>
			<megabytes>40000</megabytes>
		 </volume>
		</volumes>
		<IPAddresses>
			<IPAddress>allUnassigned</IPAddress>
			<IPAddress>157.60.0.1</IPAddress>
			<IPAddress>157.60.0.2</IPAddress>
			<IPAddress>157.60.0.3</IPAddress>
		</IPAddresses>
		</server>
		<server>
		<serverName>machine02</serverName>
		<volumes>
			<volume>
			<location>c:</location>
			<megabytes>30000</megabytes>
			</volume>
			<volume>
			<location>d:</location>
			<megabytes>40000</megabytes>
			</volume>
		</volumes>
		 <IPAddresses>
		 <IPAddress>157.60.0.4</IPAddress>
		 <IPAddress>157.60.0.5</IPAddress>
		 <IPAddress>1157.60.0.6</IPAddress>
		</IPAddresses>
	 </server>
	 </servers>
   </executeData>
  </execute>
 </procedure>
</request>>

Input for AddIISResources

You can supply input for more than one server in the same request by supplying multiple <server> tags. The following input is valid for this request:

LDAP path of the hosting organization (the organization that has been assigned full permissions to the created hosting directory).
In the <owner> element, enter the Lightweight Directory Access Protocol (LDAP) path of the hosting organization.
```
<owner>LDAP://LDAP path of the hosting organization</owner>
```
Server DNS name
In the <serverName> tag, you specify the internal Domain Name System (DNS) name of the server to add to the pool of servers managed by Resource Manager.
```
<serverName>DNS name of server</serverName>
```
Disk volumes (optional)
In the <volume> tag, specify the location and size of the disk volumes to add to the pool of disk resources managed by Resource Manager.
```
<volume>
	<location>drive letter:</path>
		<megabytes>size of volume</megabytes>
  </volume>
```
IP addresses (optional)
In the <IPAddress> tag, you can optionally specify the IP addresses to add to the pool of IP addresses managed by the Resource Manager. The computer called in this procedure must already own the IP address(es) specified above. Therefore, any IP addresses passed in this tag must be added to the computer before calling this procedure. Each IP address provides an HTTP port (80) and an FTP port (21). To specify an All Unassigned-type port, type a value of allUnassigned.
```
<IPAddress>IP address</IPAddress>
```

Typical response for AddIISResources

The response to this procedure does not contain significant data.

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/).

Note

The BlockModelRMO namespace tracks port 80 allocations as actual values, and port 21 allocations as virtual values. Therefore, although only one port 80 allocation and one port 21 allocation may be made against an IP address, Web sites that use host header names are able to share an IP address. To allow this behavior, the maximum allocation for the port 80 portion of an IP address is set to 1999 allocation units. When a Web site requests an IP for use without a host header name, it requests a quantity of 1000 allocation units. This ensures that no more than one non-host header site can use port 80 of the IP address. When a Web site requests an IP address for use with a host header name, the request is set to just 1 allocation unit. This allows up to 999 host header Web sites to share an IP address with a non-host header site. Because FTP sites do not use host header names, the maximum allocation for the port 21 portion of an IP address is set to 1, and allocation is straightforward.