Comparing Programmatic Administration Methods for IIS 6.0

  • Article

Applies To: Windows Server 2003, Windows Server 2003 with SP1

IIS 6.0 can be configured programmatically from standalone scripts or applications. Table 9.3 describes these methods of configuring IIS, and lists some of the advantages and disadvantages of using each method.

Table 9.3 Comparison of Programmatic Administration Methods for IIS 6.0

Configuration Method Advantages Disadvantages

Command-line tools included with IIS
  • Provides solutions to the most common administration tasks.
  • Some tools are not available on earlier versions of IIS.

Active Directory Service Interfaces (ADSI)
  • Can configure large sites and multiple servers.

  • Supports scripting.

  • Applies changes immediately without restarting the server.

  • Supports IIS 4.0 through IIS 6.0.
  • Requires knowledge of which supporting properties need to be created and set.

  • Some functionality is missing when using the IIS ADSI provider from System.DirectoryServices.

Windows Management Instrumentation (WMI)
  • Can configure large sites and multiple servers

  • Supports scripting.

  • Applies changes immediately without restarting the server.
  • Requires knowledge of which supporting properties need to be created and set.

  • Cannot be used when you are configuring a server running IIS 5.1 or earlier.

Admin Base Objects (ABO)
  • Provides a faster method of configuring IIS than ADSI or WMI.
  • Requires knowledge of which supporting properties need to be created and set.

  • Does not support scripting.

  • Only supports applications written in C++ or Visual Basic 6.0.

  • Is more difficult to use than ADSI or WMI.

  • Provides no safeguards to prevent configuration of invalid settings.

For more detailed information about the programmatic administration methods described in Table 9.3, see the IIS Software Development Kit on MSDN.