When IIS 7 was introduced one of the key features I dug in to was the Windows Event Log.   The Windows Event Log is the new version of Event Viewer.  The Event Viewer is a record of the activities on the server.  One key attribute I like about the Windows Event Log is the Filter feature.  At first glance the Filter feature appears similar to the old Event Viewer’s View/Find feature.  It has the same criteria to choose from.  Personally I found it limiting.  But with IIS 7, the find and filter feature is XML based.  This means you can access the XML query string and modify it to be more specific to your needs.  Very Nice!

By default Windows Event Log has more logs than its predecessors, but if you wish you can define your own logs for the OS to track.  Windows Event Log still records three of the core activities of the operating system; they are Application, Security, and System.

To me, the coolest thing about Windows Event Log is the XML base which you can access and modify.  Here is an example.  Say you want to find a specific instance in the System Log.  You know the event ID and the text (could be a word or phrase in the body of the log).  In the default Filter options it gives you the option to look for it with the event ID but not narrow it down to what is inside the body of the log.  This is where you will go to the ‘XML’ tab click on ‘Edit Query Manually’ and type your specified query.  Here is an example.

 <QueryList>
   <Query Id="0" Path="System">
     <Select Path="System">*[System[(EventID=1234)]] and *[EventData[Data="Some phrase"]]</Select>
   </Query>
 </QueryList>

The Path=”System” will query the System log.  If you change it to Security or Application it will query those logs.  The System[(EventID)] element is the event ID element, and of course the EventData[Data] element is the body of the text within the specific log.

If you want to look at all the XML elements attribute within the log, simply open one of the logs, click on one of the entries that is recorded, and then click on the Details tab.  You’ll get two options; either Friendly View or XML View.  If you choose XML view you will see the elements within that XML query and you can use those elements to define your specified query.

Also pay attention to the word ‘and’ in my query.  That lets you specify multiple elements so that you can pin point the records you are looking for in the Windows Event Log.  Then you can save your filter for later use.

Now, isn’t that nifty?

Raymond Penalosa
Technical Support

At DiscountASP.NET, we set up your web site to handle both www.YourHostedDomainName.com and YourHostedDomainName.com.  By having both hostnames (with or without www) bring up your web site, you don’t risk losing potential visitors.  This setup, however, is not favored by search engines.  According to many Search Engine Optimization experts, search engine bots will penalize you for duplicate content if you have multiple hostnames pointing to the same content.  SEO experts recommend the server returns a 301 permanent redirect to avoid getting penalized on your search engine ranking.

In this post, I am going to discuss a very simple technique for configuring your site to redirect YourHostedDomainName.com to www.YourHostedDomainName.com using the URLRewrite module.  Note that this feature is only supported on the IIS 7.x platform.

1. Download and install IIS Manager.  See our Knowledge Base for more information.
2. Connect to your site using the instructions listed in the above KB article.
3. Navigate to the URLRewrite section.
4. Click on “Add Rules” in the Action pane.
5. Configure the rules as below.  I am using IIS7hosting.com for this example; make sure you replace iis7hosting.com with your own domain name.

6. Click “Apply” in the Actions pane.
7. IIS should now issue a 301 redirect for all requests going to iis7hosting.com and redirect them to www.iis7hosting.com.
8. Note that the URLRewrite rule is written to your web site’s web.config file.  If you update your site in the future, your web.config file may be overwritten.  I recommend that you add the URLRewrite rule to your local development web.config file.

Here’s the result of an HTTP header check to show that the rule is working properly:

Server Response: http://iis7hosting.com
HTTP Status Code: HTTP/1.1 301 Moved Permanently
Content-Type: text/html; charset=UTF-8
Location: http://www.iis7hosting.com/
Server: Microsoft-IIS/7.0
X-Powered-By: ASP.NET
Date: Tue, 09 Feb 2010 09:05:42 GMT
Connection: close
Content-Length: 150
Redirect Target: http://www.iis7hosting.com/

Frank Cheung
CTO