rakkimk

As you know IIS 7.0 configuration system is huge, broad, or whatever you feel like calling it. It no longer just exist in its main configuration file applicationHost.config (like Metabase.XML in IIS 6.0). It can be widely spread in any of the web.config files in the virtual directories, or applications.

You would have already read IIS support team’s blog about configuring IIS to send an additional header to the client which would make IE to run under EmulateIE7 mode. I would also suggest you to read this MSDN article which talks about the various IE8 display modes available, and their corresponding functionality.

It is a while that I wrote something as crazy as this one is. This is basically a windows service running in your web server which would tweet often about the heart beat of the web server and posts its status messages. For example, v1.0 of this application will tweet the below (you can configure the time interval on the config file):

In IIS6 manager, you see a green arrow icon and a red icon against the ISAPI Filter’s list to indicate if the ISAPI Filter is loaded or not. That was possible because FilterStatus metabase key was updated after the ISAPI Filter is loaded inside the process.

Copying a website (to another exact copy)

Logparser is a powerful utility which comes handy for me whenever I’m helping my customers facing a problem with slow running pages, frequently hit pages, post mortem analysis to find what went wrong on IIS, et al. You can use Logparser to parse your IIS logs to health check the state of your server, and the requests it had served. Below are few LogParser scripts, and their corresponding output in chart format – you can choose your own format, but isn’t a picture worth a 1000 words?

If you are a Server Core fan, and wished you could host ASP.NET websites in Server Core, then feel better, you wish had come true. Windows Server 2008 R2’s Server Core will have .NET Framework which means, ASP.NET too. This is a big news for all those wanted to deploy Server Core, but stopped because .NET Fx wasn’t there in the RTM release.

Office 14 will have an online version – which can work seamlessly with the desktop version