Scott Forsyth's Blog

Sometimes I want to place a shortcut or file on the desktop of a server and want all users of the server to see it.  By default, if you save a file or folders to the desktop, it is placed on only your desktop.

Outlook is one of those programs that's easy to have a love-hate relationship with. It offers so much, but the earlier versions have been plagued with stability and performance issues.

If you haven't properly utilized compression in IIS, you're missing out on a lot!  Compression is a trade-off of CPU for Bandwidth.  With the expense of bandwidth and relative abundance of CPU, it's an easy trade-off.  Yet, are you sure that your server is tuned optimally?  I wasn't, which is why I finally sat down to find out for sure.  I'll share the findings here.

Whether programmer or administrator, we're always looking for details on certain ASP.NET or IIS configuration settings, and sometimes we come up wanting because of lack of good documentation.

I work with web farms on a daily basis, and one of the requirements that I run into, for testing, troubleshooting and logging, is to tell which node is handling a specific request. 

I don’t tend to blog too much about myself personally, but I thought I would break my mold and start off the new year with an exciting non-technical project I worked on over Christmas. This will hopefully kick off a year of more consistent blogging since I’ve been pretty quiet the last year.

In IIS, you run into an interesting situation when you need to access another resource off of the IIS server and certain fairly common situations occur.  When using Integrated Security, anonymous access is disabled, and impersonation is turned on, a security measure kicks in and doesn't allow your site to access resources on any network servers.  This includes access to a UNC path directly from IIS or SQL Server using Windows authentication.

I've written a couple times about what configuration changes cause AppDomain recycles.  Most recently how the ASP.NET tab causes a server-wide AppDomain recycle, and previously about changes in ASP.NET 2.0.