What is the difference between IIS7 use and IIS6?

Intermediary transaction http://www.aliyun.com/zixun/aggregation/6858.html ">seo diagnose Taobao guest cloud host technology Hall

Windows 2008 Server has been out for a long time and wants to experience it.

Just a few days ago, there is a server hard drive a bit faulty, so bought a 256G solid state hard drive, intend to install windows2008.

Using Windows 2003 for the first time, Windows Server 2008 is a very uncomfortable experience. The first is to add the IIS service, looking for a long time in the feature, and no IIS found. The last online search, only to find to add to the role inside.

Here are some feelings about using IIS7.

1.IIS7 's operating interface differs greatly from IIS6. Personally think IIS6 interface is simple, convenient, all operations can be completed in a window, only need to switch different panels. IIS7 is very troublesome, is divided into many functional links. See the difference between IIS6 and IIS7 's operating interface.

The screenshot above is IIS6, you can see, all in a window, just want to switch in the panel. Very convenient, the image below is a screenshot of IIS7 's function.

When you double-click the function button, you cannot easily return it. Must go to the left to click on the site, the operation is very troublesome. And you can see the listed features, there is no binding site and the Web corresponding directory settings. So where do you go to set it up? Need to be in the site list, right click to operate. Please see the menu displayed after the site right button.

Where the web corresponds to the directory settings, you need to go to the advanced settings in the menu.

The default document settings for 2.IIS7 are problematic. The default document is saved in the corresponding web directory. If different domain names point to the same directory, then these domain names will share a default document. That would be inconvenient. For example stationmaster Helper net (www.linkhelper.cn/) http://i.xxxx.cn and http://pr.xxxxr.cn all point to e:\web\xxxx directory. However, the default document for http://i.xxxx.cn should be the site.asp,pr.xxxx.cn default document is querypr.asp. In this way, the use of IIS7 can not be achieved. Because if you specify the default document order for pr.xxxx.cn, the first is queypr.asp, then i.xxxx.cn's default document is changed as the configuration file is stored in the E:\web\xxxx directory, and IIS6 does not.

Some people will ask, since you want to share a directory, why use a different domain name? Very simple, because different domain names can correspond to different application pools, so that even if one of the application pool errors, it will not affect access to other sites.

Then there are those who would say, well, you can copy files and make a list again, but there's a problem. Because I do not pr.xxxx.cn or i.xxxx.cn, many of these files are shared, if you want to update, I have to update several directories, if the domain name more, the corresponding directory will be more, maintenance is very inconvenient.

Personally feel, IIS7 different domain name corresponding to the same directory, you must share a default document, this design is very unreasonable.