Compensating for Changes to IIS Components

  • Article

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

Because of increased security measures, which remove any unnecessary Web sites or configuration settings from the Web server, the upgrade process can remove or change the existing IIS configuration. The upgrade process ensures that you take the necessary steps to accommodate these changes so that your applications run as they did before the upgrade.

The following table lists the changes in the behavior, administration, and support of IIS 6.0

Changes to IIS Components After Upgrade

Before Upgrade After Upgrade

The IISAdmin virtual directory exists.

The IISAdmin virtual directory is removed and a default Web page is placed in the directory. 1

Web service extensions are mapped to 404.dll. 2

All extensions mapped to 404.dll are disabled. All other extensions are enabled.

Web Distributed Authoring and Versioning (WebDAV) is disabled by using NTFS file system permissions. 3

WebDAV permissions are changed to allow proper operation, and WebDAV is added to the Web service extensions list as prohibited.

Indexing Service is disabled by using NTFS permissions. 3

Indexing Service remains disabled with the same NTFS permissions.

Web services hosted on IIS 5.0 are enabled.

Web services supported by the WWW service are disabled. 4

FrontPage 2000 Server Extensions included lightweight server support.

FrontPage 2002 Server Extensions does not include lightweight server support.

FrontPage 2000 Server Extensions support.

FrontPage 2000 Server Extensions is not supported. Upgrade all Web sites to FrontPage 2002 Server Extensions.

1 Directory is removed if the IIS Lockdown Tool is run before upgrade.

2 The IIS Lockdown Tool maps all Web service extensions, used by IIS, to 404.dll to disable the extensions. Additional Web service extensions installed beyond the default IIS Web service extensions are not mapped to 404.dll.

3 The IIS Lockdown Tool disables WebDAV and the Indexing Service by changing the permissions.

4 If the IIS Lockdown Tool runs before upgrade or the appropriate registry modifications are made, the Web services remain enabled after upgrade. For more information about preventing the Web services from being disabled, see Preventing the WWW Service from Being Disabled.

As a part of the architectural changes to IIS 6.0, many of the features that were previously implemented as Internet Server API (ISAPI) filters are now integrated into IIS directly. The following table lists the ISAPI filters that have been removed and have the functionality of the ISAPI filter implemented in IIS 6.0

ISAPI Filters Removed During Upgrade

ISAPI Filter Removed ISAPI Filter File Name Implemention in IIS 6.0

SSL encryption

Sspifilt.dll

Integrated into IIS 6.0 directly

Compression

Compfilt.dll

Integrated into IIS 6.0 directly

Kerberos authentication

Md5filt.dll

Integrated into IIS 6.0 directly