The story about IIS 6.0 untold, if you've invested in IIS technology, IIS 6.0 is definitely a moving, listening-to topic. Given that the difference between IIS 6.0 and previous versions is too great to be exhaustive in just one article, this article first explores the installation of IIS 6.0, the architecture, and the new service capabilities that result from architectural differences, and then the next article introduces IIS 6.0 features- Some of them you may not have heard of, and there are some important changes in the default configuration, these changes may affect your migration plan.
First, install IIS 6.0
First, start with the basics. IIS 6.0 is included in four versions of the Windows Server 2003 server: Data center, Enterprise, Standard, and web. Also, by the way, answer one of the most common IIS 6.0 issues: IIS 6.0 cannot run on Windows XP, 2000, or NT.
Once you've installed Windows 2003, you'll soon see the difference in Windows 2003/iis 6.0, and one of the key changes is that, in addition to the Windows 2003 Web version, IIS is no longer installed by default for the rest of Windows 2003. According to Microsoft's past philosophy, the installation of the operating system while IIS also automatically started, for many Web applications to provide services, Windows 2003 is a major breakthrough in the practice. In Windows 2003, there are three ways to install IIS: Use the Manage Your Server Wizard to use the Add/Remove Windows Components feature of the Add or Remove Programs in Control Panel, or perform an unattended installation.
When you start the Windows 2003 System for the first time, the Manage Your Server Wizard starts automatically, as shown in figure.
screen.width-600) this.style.width=screen.width-600; "Border=0>
Figure I
Select the Add or remove role to see a list of configurable server roles in the Configure Server Wizard, where the application server (iis,asp) is available. NET) option, as shown in Figure two, after selecting this option and clicking Next, the wizard provides options for installing ASP.net and Microsoft FrontPage Server Extensions. As you can see, Microsoft has adopted a new type of "install any part before always
Ask for user comments "IIS installation strategy, for Microsoft, this is a radical change, that Microsoft is really serious about security issues."
screen.width-600) this.style.width=screen.width-600; "Border=0>
Figure II
Use the Add/Remove Windows Components feature in Control Panel to be flexible. In the wizard, select Application Server. Click "Details" and the wizard displays a list of components, including the Internet Information Services (IIS) option, and some options that were not provided by the previous Add/Remove Windows Components Wizard, which is a summary comparison of the IIS 6.0 and the main components of IIS 5.0. If you install IIS 6.0 from here, the resulting web server may only support static content (unless some of the extension components are selected during installation). Select the Internet Information Services option, and then click Details to see the subcomponents of IIS 6.0, as shown in Figure three.
screen.width-600) this.style.width=screen.width-600; "Border=0>
Figure Three
Table One: IIS 6.0 and IIS 5.0 component comparisons |
IIS 6.0 |
IIS 5.0 |
Application Server |
Internet Information Services |
Application Server Console |
Common Files |
asp.net |
Document |
Enable network COM + access |
File Transfer Protocol (FTP) service |
Enable Network DTC Access |
FrontPage 2000 Server Extensions |
Internet Information Services |
Internet Information Services Snap-in |
Background Intelligent Transfer Service (BITS) Server Extensions |
Internet Services Manager (HTML) |
BITS Management Console Snap-in |
NNTP |
BITS Server Extensions ISAPI |
Smtp |
Common Files |
World Wide Web Services |
File Transfer Protocol (FTP) service |
|
FrontPage 2002 Server Extensions |
|
Internet Information Services Manager |
|
Internet Printing |
|
NNTP Service |
|
SMTP Service |
|
World Wide Web Services |
|
Active Server Pages |
|
Internet Data connectors |
|
Remote Administration (HTML) |
|
Remote Desktop Web Connection |
|
Included files on the server side |
|
WebDAV Publishing |
|
World Wide Web Services |
|
Message Queuing |
|
Active Directory Integration |
|
Public |
|
Downlevel Client Support |
|
MSMQ HTTP Support |
|
Routing Support |
|
Trigger |
|
You may have noticed some of the new component options listed in table one, but did you notice anything missing from IIS 6.0? One of the most important items that is missing from IIS 6.0 is the documentation. In IIS 6.0, all documents are published in the form of Help files and no longer have iishelp virtual directories. In IIS 5.0, if you access the server from a local, the default Web site automatically opens the document for IIS, but in IIS 6.0, if you open the
Http://localhost ", you can only see a page that declares that the site is being built.
In addition, there are some error-handling pages in the IISHelp virtual directory of IIS 5.0, which are implemented in ASP. If you want to use custom (or modified) Help files, error-handling pages, you must create the directory yourself on the IIS 6.0 Web site.
Further analysis of the sub-component manifest for IIS 6.0 shows that Internet Service Manager (ISM), which was previously installed by default in IIS 5.0 and IIS 4.0, is gone. However, if you click on "World Wide Web Services" (one of the subcomponents of IIS 6.0, however, figure III does not show up), and then click "Details" to find out that the Web service for IIS 6.0 also has subcomponents, as shown in Figure four, which includes the original Internet Server Manager, but is now renamed " Remote administration (HTML), and the Windows 2003 and XP version of Terminal Services 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 connectors, server-side inclusion files, WebDAV publishing, and, of course, the World Wide Web service.
screen.width-600) this.style.width=screen.width-600; "Border=0>
Figure Four
The last way to install IIS 6.0 is an unattended installation. As before, this is still the only way to install a tool and a default Web site to another drive, rather than a system drive. The Windows 2003 unattended installation is still largely the same as win 2K, using sysocmgr and an answer file to implement the installation. Of course, new features require new parameters, options, and detailed instructions for this can be found in Windows 2003 Release Candidate 2 (RC2) at the address: http://www.microsoft.com/technet/ Treeview/default.asp?url=/technet/prodtechnol/windowsnetserver/proddocs/datacenter/gs_installingiis.asp.
If you upgrade the IIS 5.0 or IIS 4.0 Server to Windows 2003,iis 6.0, it will not be set to start automatically. That is, if you install in an upgraded manner, IIS 6.0 is disabled by default unless one of the following conditions is encountered:
The IIS Lockdown tool is already installed on the previous IIS server ⑴.
⑵ There are registered subkeys
Hkey_local_machine/system/currentcontrolset/services/w3svc/retainw3svcstatus, and it contains an arbitrary registration key. For example, you can create a key named EnableIIS6 that sets its value to 1 of the DWORD type.
⑶ in an unattended upgrade installation, there is a disablewebserviceonupgrade = True/false entry in the [InternetServer] section of the answer file.
Current 1/2 page
12 Next read the full text