IIS uses ten Principles

IIS has a very simple custom error page, but only a few administrators can use it effectively. An administrator can image an HTTP error message in an MMC to an absolute URL or a file on the server, and more detailed information can be found here. If you think this is too much trouble, want a simpler approach, or you want the developer to define the error pages themselves without having permission to use MMC, you can use a tool like customer error.

2. Metabase Research

If you think Apache is powerful because it has a configuration file, you should look at how good IIS metabase is. With metabase, an administrator can complete all work on IIS, such as establishing a virtual directory, stopping, starting, or pausing a Web site, establishing, deleting, banning, or enabling applications. Microsoft provides a visual tool MetaEdit help you read and write metabase, where you can download the latest version of it. To make more effective use of metabase, you should try the command-line interface---IIS administration Script, referred to as adsutil.vbs, you can C:\inetpub\adminscripts or%systemroot Find it under the%\system32\inetsrv\adminsamples directory.
Note: Metabase is important to the normal work of the Web site, do not destroy it. Remember: You must back up before making any changes.

3. Automatically correct spelling errors for URLs

Apache advocates are always boasting some of Apache's small features, of which the coolest number "automatically corrected URL spelling errors", now, IIS administrators can play with these small features, using Urlspellcheck, automatically correct the URL spelling error is a piece of cake. To do a trial: Www.urlspellcheck.com/fak.htm and Www.urlspellcheck.com/faq1.htm, and the second wrong spelling will be corrected automatically.

4. Rewriting URLs

Apache advocates have been bragging about the power of mod_rewrite, and now there's a dozen of these products for IIS, much better than mod_rewrite, because using mod_rewrite, you have to be familiar with regular expressions. Try this: Iiswrite or ISAPI rewrite.

5. Probe browser

Assuming that everyone browsing the site is using the same browser or screen size is obviously stupid, you can use JavaScript to detect the visitor's browser. If you are using IIS, you will have a better choice---cyscape Company's Browserhawk,apache world is not compared to its products. Cyscape company recently launched a new product called Cuntryhawk, which can be used to explore the region (country) where visitors are located. Unfortunately, I still have no language sensitive or area sensitive content to use it.