If the following features are not found in IIS7, check to see if it is installed in the Server Manager-role-role service.
Limit bandwidth usage
Select a site, in the right-hand interface, find "Configuration" and click "Limit" below. As you can see, not only can you limit the number of IIS connections, but you can also limit the bandwidth that this site allows:
This feature minimizes the impact on the server when it comes to a single site DDoS attack.
IIS6 only the ability to limit the number of connections.
Failed request tracking rules
I believe we all have encountered such a problem: the site can be accessed for a while, can not visit. The solution is just two: Keep following until the problem arises (annoying ...) Or a line to go over the log (tired ...) ）。 IIS7 gives us a third solution, which is failure request tracking. Setting up a failed request tracking rule for a specific Web site allows IIS to generate logs that the Web site cannot access and is saved separately in a specific directory for administrators to view. To set the method:
Select a site, in the right-hand interface, find "Configuration" and click "Fail Request Tracking" below:
Check enable and set the save path for the log file. The following number indicates the number of traces (a log file is generated at a time of tracing). Then go to the Setup interface for the failed Request tracking rule, click Add, and Install the wizard step-by-step.
The generated log file is. xml format and can be viewed from the browser.
IIS6 does not have this feature.
The compression feature in IIS7 contains static content compression and dynamic content compression, which means that the content of the page is compressed before being returned to the browser (when the browser initiates a GET request). Enable this feature, you can save bandwidth, improve access speed (pretty good features ...) ）。 Only dynamic content compression increases overhead and is not recommended, and static content compression is enabled by default.
IIS6 does not have this feature.
Dynamic IP restrictions, a similar function of a DDOS firewall! Enter the dynamic IP restrictions settings interface, you can see that not only for the number of concurrent connections, but also for a period of time, the number of access to an IP limit:
IIS6 can only be limited to specific IP (segment).
IIS7 creates a separate account for each program pool, which is used to identify the program pool. This kind of account belongs to the system built-in account, is not visible in the computer user management interface, collectively is applicationpoolidentity:
Although it all seems to be applicationpoolidentity, it is in fact a different account (one pool corresponds to one account).
You can use the IIS apppool\ application pool name for NTFS authorization:
For the sake of IIS6 compatibility, we can manually identify the program pool as Localservice,localsystem,networkservice or a specific account.
IIS6 does not exist in this type of account.
IIS7 provides a common command-line administration tool Appcmd.exe for all operations on IIS (including site management, FTP management, application pool management, virtual directory management, and so on) on the command line (script). This tool is located in C:\Windows\System32\inetsrv, please check the Help documentation for specific use:
Although IIS6 also provides a series of VBS (IISWEB.VBS, Iisftp.vbs, iisapp.vbs, etc.) to implement similar functions, such scripts are subordinate to Wscript.Shell, and Wscript.Shell is usually disabled (for security reasons) ...
Appcmd.exe obviously has no problem with this.
