The path is the IIS path of the metabase key. The path is required only in the root key node of the request. Child key nodes do not use path, and require name instead. This attribute is filled in on return for all keys. When creating a Web or FTP site, the provider will automatically choose a site number if the site number requested is * as shown in the example. On return, the path name will be filled in with the generated site number.

It is important to ensure path points to a valid, appropriate and trusted location. See the security note in IIS Provisioning Security Considerations for more details.

These properties are stored directly under the site key in the metabase. The minimum required properties and subkeys are shown in this example, but additional properties and subkeys may be supplied if desired.

• ServerComment - The name of the website as displayed in the Windows management user interface (UI).
• ServerBindings - A multi-valued property containing IP address, port number, and host header name separated by colons. IP address may be zero-length to represent all unassigned. Host header may be zero-length. Port number is mandatory.
• ServerAutoStart - (optional) Unless this value is 0, the site will start immediately upon creation. Defaults depends on the IIS installation, usually is 1. If the ServerState property is supplied, it overrides the start upon creation behavior of ServerAutoStart.
• ServerState - (optional) This property is given special handling by the provider to ensure that the site state transitions to the supplied value by calling the appropriate Start, Stop, Pause, and Continue methods. An apparent bug in IIS 5.0 causes the Start method to fail when called immediately upon site creation, so it may be necessary to set this property as a separate step in for IIS 5.0 servers. See the SetProperties (ControlSite) method for more detail about this property.

These properties are stored in the Root key, which lives under the site key in the metabase. The minimum required properties are shown in this example, but additional properties may be supplied if desired.

• Path - The root storage path for the website.
• UNCUserName - (optional) If the path is a Universal Naming Convention (UNC) name, this user name will be used with the UNCPassword to access the UNC resource.
• UNCPassword - (optional) Uses blank password if not supplied.
• AppFriendlyName - (optional) Sets the name of the IIS application (if any) that will be displayed by applications such as the IIS Management snap-in.
• AppIsolated - (optional) Specifies the degree of process isolation that the application is configured to run with: 0 - in-process; 1 - separate process for each app; 2 - pooled out-of-process. If this parameter is supplied, the virtual directory is created as an IIS application, and AccessFlags must be supplied also.
• AccessFlags - (optional) Specifies the access allowed for this virtual directory. If this parameter is supplied, the virtual directory is created as an IIS application, and AppIsolated must be supplied also. This value is a bit field. The values for the bit field are defined by IIS, and are repeated here for convenience:

  		MD_ACCESS_READ			0x0001
  		MD_ACCESS_WRITE			 0x0002 
  		MD_ACCESS_EXECUTE		 0x0004
  		MD_ACCESS_SOURCE			0x0010
  		MD_ACCESS_SCRIPT			0x0200
  		MD_ACCESS_NO_REMOTE_WRITE   0x0400
  		MD_ACCESS_NO_REMOTE_READ	0x1000
  		MD_ACCESS_NO_REMOTE_EXECUTE 0x2000
  		MD_ACCESS_NO_REMOTE_SCRIPT  0x4000