I just found this blog post on iis.net and applied it to my WordPress site. The site does seem a lot faster but it could be the car wash effect. You know, when you get your car washed and somehow it makes it faster. Also known as the gas tank effect.
http://blogs.iis.net/ruslany/archive/2010/03/05/make-wordpress-faster-on-iis-with-wincache-1-1.aspx
I’m testing an install of DotNetNuke on IIS 7 and ran into an error when trying to start the site.
The WebResource.axd handler must be registered
I tried following some guides online to add the handlers to the >system.webserver> section which is there for IIS in the web.config but I couldn’t get them to work so I just switched the application pool to classic mode. I’d rather run in integrated, I hate running something as up to date as DNN on an IIS 7 server in basically IIS 6 mode; but for now this works. So to get around this error just switch your app pool in IIS 7 to classic mode and then restart it. Below is a guide on how to do that.
http://support.gearhost.com/KB/a381/change-managed-pipeline-mode-in-iis-7.aspx
Recently we got a customer who wanted an inexpensive high availability solution. To keep costs down we decided to utilize NLB within Windows Server 2008 and load balance two IIS web servers. The issue we ran into was getting multiple sites to balance. It actually turned out be a very simple issue. When a request is passed to IIS it looks at the header for the site and then passes that request to the site with the same binding. I had setup the bindings in IIS 7 for the sites to the local IP addresses on each server. When our sys admin setup NLB and tried the sites one each server through the NLB public facing IP we got a 404.
Our sys admin gave me a quick crash course in NLB so I could get a simple understanding of how it worked and was setup. After watching the setup I suddenly realized what was going on. It was a great eureka moment. I knew what I had to do to fix it but I was hoping for a work around because I wanted ot keep it simple for the customer. In the end all I had to do was assign the bindings with the public facing IP of the NLB cluster, not the IP’s on the local machines. After doing this the sites worked great.
The servers we are load balancing are virtual so we simply paused one and made sure the site still worked. It worked great. If one of the servers goes down the other will take over requests. This is very simple setup. If you want to get a little more complicated and really dig into high avialability I suggest looking into ARR. Here is a link, Microsoft Application Request Routing with NLB for high availability. Have fun with that one 
I'm Mike Kauspedas - working in IT for a small web hosting company called GearHost who loves to cycle and has to eat gluten-free. Most of my posts will focus on gluten-free foods and restaurants around Denver Colorado with a sprinkling of cycling in between some posts about technology, guides, and how-to's for web hosting.
