
Microsoft
®
Windows Server
™
2003 White Paper
Windows NT 4.0 Server Upgrade Guide 92
IIS 6.0 Security Changes
Perhaps the biggest change in Windows Server 2003 is that IIS 6.0 is not installed by default.
When IIS 6.0 is installed, ASP.NET support is enabled, but traditional ASP and ISAPI extensions
are disabled by default.
If you are upgrading a Windows NT Server 4.0 computer, you will not see these security settings,
because IIS is installed manually on Windows NT 4.0–based computers. You can continue to run
existing ASP Web applications and other ISAPI extensions that you have enabled. By
comparision, when upgrading a Windows 2000-based computer, IIS is installed by default but
disabled; consequently, ASP and ISAPI extensions are disabled.
It is recommended that you do not upgrade but rather perform a clean installation of the operating
system. After a clean installation, if you then install IIS, the Web Service Extensions are
configured as Figure 42 shows.
Figure 42. Default Web Service Extensions configuration folder in IIS 6.0
If you plan on running any earlier ASP applications, you should enable the ASP extension by using
the same Application Server window.
IIS 5.0 Isolation Mode
Another significant security change in IIS 6.0 is its use of the following two isolation modes: IIS 5.0
isolation mode and worker process isolation mode. IIS 5.0 isolation mode keeps your computer as
compatible as possible with older Web applications. It’s designed to help applications that are
dependent on the older memory model and process model of IIS 5.0 to run with success. This
isolation setting should be used only as long as it takes to fix the compatibility issues with the
Comentarios a estos manuales