In-depth analysis of IIS 6.0 (a)

The story about IIS 6.0 is hard to say, if you have invested in IIS technology, IIS 6.0 is undoubtedly a moving, inaudible topic. Given that the difference between IIS 6.0 and the previous version is too big, it is difficult to do everything with just one article, so this article first discusses the installation, architecture, and new service features brought about by the differences in architecture. An article goes on to introduce the new features of IIS 6.0 - some of which you may not have heard of, and some important changes in the default configuration that may affect your migration plan.

First, install IIS 6.0

Let's start with the most basic. IIS 6.0 is included in four versions of the Windows Server 2003 server: Data Center Edition, Enterprise Edition, Standard Edition, and Web Edition. Also, by the way, answer one of the most common IIS 6.0 issues: IIS 6.0 does not work on Windows XP, 2000 or NT.

After installing Windows 2003, you can see the difference between Windows 2003/IIS 6.0. One of the key changes is that, with the exception of Windows 2003 Web Edition, the rest of Windows 2003 defaults. IIS is no longer installed. According to Microsoft's past philosophy, IIS also automatically starts when the operating system is installed, providing services for many web applications. Windows 2003 is a breakthrough. In Windows 2003, there are three ways to install IIS: use the "Manage Your Server" wizard, use the "Add/Remove Windows Components" feature in the Control Panel "Add or Remove Programs", or perform an unattended installation.

When you first start your Windows 2003 system, the Manage Your Server wizard starts automatically
Selects the Add or Remove role, and you can see a series of configurable in the Configure Server wizard The server role, which has the "application server (IIS, ASP.NET)" option, as shown in Figure 2, select this option and click "Next", the wizard provides the option to install ASP.NET and Microsoft FrontPage server extensions. It can be seen that Microsoft has adopted a new type of IIS installation strategy that always asks users for comments before installing any components. For Microsoft, this is a complete change, which proves that Microsoft is really taking security seriously.

Figure III
You may have noticed some new component options listed in a table, but you notice what you missing IIS 6.0? One of the most important projects that disappeared in IIS 6.0 was the documentation. In IIS 6.0, all documents are published as help files, no longer having the IISHelp virtual directory. In IIS 5.0, if you access the server locally, the default Web site automatically opens the IIS documentation, but in IIS 6.0, if you open http://localhost, you will only see a page stating that the site is being built. BR> In addition, there are some error handling pages in the IISHelp virtual directory of IIS 5.0. These error handling pages are implemented in ASP mode. If you want to use custom (or modified) help files, error handling pages, in IIS The 6.0 website must create this directory yourself.

Further analysis of the IIS 6.0 sub-component list, you can find that the original Internet Service Manager (ISM) installed in IIS 5.0 and IIS 4.0 has disappeared. If you click on "World Wide Web Service" (one of the sub-components of IIS 6.0, but Figure 3 does not show it), then click on "Details", you can find the IIS 6.0 Web Services and subcomponents, as shown in Figure 4. This includes the original Internet Server Manager, but has now been renamed "Remote Management (HTML)"; there are also Windows 2003 and XP versions of the terminal Advanced Client (TSAC) - now called "Remote Desktop Web Connection." Now, we can not only easily add or remove these two subcomponents, but also other subcomponents, including: ASP, Internet Data Connector, On the server side of the include files, WebDAV release, and of course the World Wide Web service.

Figure 4

The last way to install IIS 6.0 is unattended installation. As before, This is still the only way to install tools and default Web sites to other drives (rather than system drives). Windows 2003 unattended installations are still largely the same as Win 2K, with Sysocmgr and a response. File implementation installation. Of course, new features require new parameters, options, and detailed instructions on this can be found in Windows 2003 Release Candidate 2 (RC2) at http://www.microsoft.com/technet/treeview /default.asp?url=/technet/prodtechnol/windowsnetserver/proddocs/datacenter/gs_installingiis.asp.
If you upgrade IIS 5.0 or IIS 4.0 server Level to Windows 2003, IIS 6.0 will not be set to start automatically. That is, if installed in an upgraded way, IIS 6.0 is disabled by default unless one of the following conditions is encountered:
(1) On the previous IIS server The IIS Lockdown tool has been installed.

(2) There is a registration subkey HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\W3SVC\\RetainW3SVCStatus, and it contains an arbitrary registration key. For example, you can create a key called EnableIIS6 and set its value to 1 for the DWORD type.

(3) In the unattended upgrade installation, the DisableWebServiceOnUpgrade = True/False entry exists in the [InternetServer] section of the answer file.

Second, support services

Since the release of IIS 6.0, some of its new features have been the focus of attention and discussion, and have become the star of everyone, but other Internet support services, although It's not always talked about, but it's also worth paying attention to. One of them is the POP3 service and the POP3 service web manager. We have no way of knowing why Microsoft is not listing POP3 services in the "Application Server" component list, but after the SMTP service (SMTP service is installed with the POP3 service), administrators have been looking forward to POP3 services for a long time, they have been looking forward to Replace the huge Microsoft Exchange Server with a simple POP3 service.

The Unified Description, Discovery, and Integration (UDDI) service is another new feature provided by Windows 2003. It is also related to IIS, but it is not installed by default (note) Windows 2003 Web Edition cannot install UDDI). UDDI is an industry standard (that is, not Microsoft's invention). It can publish Web services provided by IIS server through advertisements. The meaning of the word "advertising" here is different from the advertisement in daily life. It refers to a kind of client program. (usually a web browser) A way to learn the details of a Web service (usually an ASP.NET application). UDDI is still evolving, but some companies have adopted UDDI internally so that developers can post their own code to other collaborative developers. More information about UDDI can be found at http://www.uddi-china.org/(Chinese) http://www.uddi.org (English) http://www.uddicentral.com (English) ).

The last important support service is the Background Intelligent Transfer Service, Background Intelligent Transfer Service or BITS. BITS is a background file transfer mechanism and queue manager, also known as a throttling service. BITS controls file requests, reducing bandwidth consumption and improving the end user experience. Enabling BITS for IIS guarantees the quality of service of the Web server. Without BITS, when 100 users download a 500 MB file at the same time, the bandwidth of the server may be exhausted, causing other users accessing the Web service to frequently encounter timeouts. error. If BITS is as effective as the ad says, it can be expected to be a very useful service. After the release of Windows 2003, BITS will be ported to Win2K as planned. For more information on BITS, please visit http://www.microsoft.com/windows.netserver/techinfo/overview/bits.mspx.

Third, the new kernel

From an architectural point of view, IIS 5.0 and IIS 4.0 are actually the same: they are all applications that publish web content running in user mode, or Run as a System account within the Inetinfo process, or as an IWAM user outside the Inetinfo process. Although under heavy load, IIS 5.0 has a very good performance; but from IIS 6.0, our view of the IIS infrastructure should change. In order to enable IIS to easily support 1000 Web sites, and to support 10,000 or more websites, and to improve the security and reliability of Web servers, Microsoft abandoned the original IIS kernel and reconstructed a new one. .

Another reason for Microsoft to rebuild the IIS kernel is that Microsoft (and other vendors) recognize that the performance and reliability issues of Web servers are mostly due to poor quality Web applications. IIS 5.0 mitigates this problem with the Out of Process container with a buffer pool. In IIS 5.0, once an application running in the Out of Process pool crashes, it generally does not affect IIS itself, because the application runs in a process other than Inetinfo, but all web applications running inside the Out of Process pool are terminated. -- By default, all applications run in this pool. In this case, troubleshooting is not easy, because it is very difficult to determine which application is causing the problem. IIS 6.0 isolates the different tasks of listening to requests, creating and monitoring Web sites, and running Web services. This new system is expected to solve the problems of IIS 5.0. In theory, the new system will greatly improve usability, security and performance; from a practical point of view, according to reports from Microsoft and Beta testers, the new system has dramatically improved stability and performance. The kernel system of IIS 6.0 is mainly built on three components: W3SVC, http.sys, and W3Core.