<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.orcsweb.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Scott Forsyth's Blog</title><link>http://blogs.orcsweb.com/scott/default.aspx</link><description /><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.2)</generator><item><title>IIS, Windows Authentication and the Double Hop issue</title><link>http://blogs.orcsweb.com/scott/archive/2008/08/22/iis-windows-authentication-and-the-double-hop-issue.aspx</link><pubDate>Fri, 22 Aug 2008 20:33:00 GMT</pubDate><guid isPermaLink="false">2330e3f2-49bd-42cb-a16c-a9380a6a6a02:44246</guid><dc:creator>Scott Forsyth&amp;#39;s Blog</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.orcsweb.com/scott/comments/44246.aspx</comments><wfw:commentRss>http://blogs.orcsweb.com/scott/commentrss.aspx?PostID=44246</wfw:commentRss><description>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. The reason is because of a 'double hop' that authentication is doing. When you authenticate to the IIS server using Integrated Authentication, that uses up your first 'hop'. When IIS tries to access a network device, that would be the double or second hop which is not allowed. IIS cannot in turn pass on those...(&lt;a href="http://blogs.orcsweb.com/scott/archive/2008/08/22/iis-windows-authentication-and-the-double-hop-issue.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.orcsweb.com/aggbug.aspx?PostID=44246" width="1" height="1"&gt;</description><category domain="http://blogs.orcsweb.com/scott/archive/tags/IIS/default.aspx">IIS</category><category domain="http://blogs.orcsweb.com/scott/archive/tags/Windows+Server/default.aspx">Windows Server</category></item><item><title>Application Pool Recycles from IIS 7 Setting Changes</title><link>http://blogs.orcsweb.com/scott/archive/2008/08/11/application-pool-recycles-from-iis-7-setting-changes.aspx</link><pubDate>Mon, 11 Aug 2008 14:37:00 GMT</pubDate><guid isPermaLink="false">2330e3f2-49bd-42cb-a16c-a9380a6a6a02:42701</guid><dc:creator>Scott Forsyth&amp;#39;s Blog</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.orcsweb.com/scott/comments/42701.aspx</comments><wfw:commentRss>http://blogs.orcsweb.com/scott/commentrss.aspx?PostID=42701</wfw:commentRss><description>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 . Here I'm going to cover things that, when done in IIS 7, will cause a full application pool recycle. I obtained the following list from the Microsoft.com folk at Microsoft. They worked with the IIS team during IIS 7 development to get a complete list of all settings which cause full app pool recycles. What this means is that if you make changes to applicationHost.config that touches anything in the following list, the applicable application pool will be recycled. If you change other settings to applicationHost.config, the app pools on the...(&lt;a href="http://blogs.orcsweb.com/scott/archive/2008/08/11/application-pool-recycles-from-iis-7-setting-changes.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.orcsweb.com/aggbug.aspx?PostID=42701" width="1" height="1"&gt;</description><category domain="http://blogs.orcsweb.com/scott/archive/tags/IIS/default.aspx">IIS</category><category domain="http://blogs.orcsweb.com/scott/archive/tags/IIS7/default.aspx">IIS7</category></item><item><title>ASP.NET tab in IIS, more dangerous than it first appears!</title><link>http://blogs.orcsweb.com/scott/archive/2008/08/01/asp-net-tab-in-iis-more-dangerous-than-it-first-appears.aspx</link><pubDate>Fri, 01 Aug 2008 14:49:00 GMT</pubDate><guid isPermaLink="false">2330e3f2-49bd-42cb-a16c-a9380a6a6a02:40840</guid><dc:creator>Scott Forsyth&amp;#39;s Blog</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.orcsweb.com/scott/comments/40840.aspx</comments><wfw:commentRss>http://blogs.orcsweb.com/scott/commentrss.aspx?PostID=40840</wfw:commentRss><description>This blog post was a long time coming and fortunately doesn't apply to IIS7, but I thought I would finally take a few minutes and cover this shortcoming with the ASPNET tab that ASP.NET 2.0 introduced into IIS 6 and IIS 5. As I've covered in a previous post , only 1 version of ASP.NET can run at a time in each IIS Application Pool. When you want to target a newer or older version of the ASP.NET framework for a particular site or application, you must update that website or application. When ASP.NET 1.1 was released When ASP.NET 1.1 was released, the common way to do this was to use aspnet_regiis.exe from the command line. There was a serious shortcoming with that method though, as I detailed back in December of '03. (That article and attached...(&lt;a href="http://blogs.orcsweb.com/scott/archive/2008/08/01/asp-net-tab-in-iis-more-dangerous-than-it-first-appears.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.orcsweb.com/aggbug.aspx?PostID=40840" width="1" height="1"&gt;</description><category domain="http://blogs.orcsweb.com/scott/archive/tags/ASP.NET/default.aspx">ASP.NET</category><category domain="http://blogs.orcsweb.com/scott/archive/tags/IIS/default.aspx">IIS</category></item><item><title>Breaking changing in IIS 7.0 and ASP.NET</title><link>http://blogs.orcsweb.com/scott/archive/2008/07/11/breaking-changing-in-iis-7-0-and-asp-net.aspx</link><pubDate>Fri, 11 Jul 2008 17:32:00 GMT</pubDate><guid isPermaLink="false">2330e3f2-49bd-42cb-a16c-a9380a6a6a02:37651</guid><dc:creator>Scott Forsyth&amp;#39;s Blog</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.orcsweb.com/scott/comments/37651.aspx</comments><wfw:commentRss>http://blogs.orcsweb.com/scott/commentrss.aspx?PostID=37651</wfw:commentRss><description>This quick post is for my own sake so I can find it again later. :-) I refer to the following link often. Mike Volodarsky has put together a detailed list of breaking changes in IIS 7.0 and ASP.NET. For the most part IIS 7 has great compatibility with IIS 6 apps. The httpModules and httpHandlers section are two important web.config sections that need to be migrated from system.web to system.webServer in Integrated mode, but most other things will work without changes. There are exceptions though, which his blog post details well: http://mvolo.com/blogs/serverside/archive/2007/12/08/IIS-7.0-Breaking-Changes-ASP.NET-2.0-applications-Integrated-mode.aspx...(&lt;a href="http://blogs.orcsweb.com/scott/archive/2008/07/11/breaking-changing-in-iis-7-0-and-asp-net.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.orcsweb.com/aggbug.aspx?PostID=37651" width="1" height="1"&gt;</description><category domain="http://blogs.orcsweb.com/scott/archive/tags/ASP.NET/default.aspx">ASP.NET</category><category domain="http://blogs.orcsweb.com/scott/archive/tags/IIS7/default.aspx">IIS7</category></item><item><title>Graffiti CMS - VDirs - ISAPI Rewrite and Partial Trust</title><link>http://blogs.orcsweb.com/scott/archive/2008/06/05/graffiti-cms-vdirs-isapi-rewrite-and-partial-trust.aspx</link><pubDate>Thu, 05 Jun 2008 19:10:00 GMT</pubDate><guid isPermaLink="false">2330e3f2-49bd-42cb-a16c-a9380a6a6a02:34156</guid><dc:creator>Scott Forsyth&amp;#39;s WebLog</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.orcsweb.com/scott/comments/34156.aspx</comments><wfw:commentRss>http://blogs.orcsweb.com/scott/commentrss.aspx?PostID=34156</wfw:commentRss><description>I thought I would spend a few minutes today testing out Graffiti from Telligent . Graffiti is a fairly new blogging and content management system (CMS) which is meant to be very easy to install and setup. True to its word, it is impressively easy to get up and going. There are a few things that I found that are worth noting. I wanted to install this in a VDir on a shared server here at ORCS Web and use ISAPI Rewrite to make it appear to run in the root folder with its own domain name. In brief terms the install involved the following: Download Graffiti (it's less than 3MB for the limited non-commercial version that I downloaded.) Extract and save to disk FTP the web folder to the vdir on the server Mark the vdir as an application (assuming IIS...(&lt;a href="http://blogs.orcsweb.com/scott/archive/2008/06/05/graffiti-cms-vdirs-isapi-rewrite-and-partial-trust.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.orcsweb.com/aggbug.aspx?PostID=34156" width="1" height="1"&gt;</description><category domain="http://blogs.orcsweb.com/scott/archive/tags/ASP.NET/default.aspx">ASP.NET</category><category domain="http://blogs.orcsweb.com/scott/archive/tags/Graffiti/default.aspx">Graffiti</category></item><item><title>Upcoming Speaking Engagements</title><link>http://blogs.orcsweb.com/scott/archive/2008/05/05/upcoming-speaking-engagements.aspx</link><pubDate>Tue, 06 May 2008 03:47:00 GMT</pubDate><guid isPermaLink="false">2330e3f2-49bd-42cb-a16c-a9380a6a6a02:32497</guid><dc:creator>Scott Forsyth&amp;#39;s WebLog</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.orcsweb.com/scott/comments/32497.aspx</comments><wfw:commentRss>http://blogs.orcsweb.com/scott/commentrss.aspx?PostID=32497</wfw:commentRss><description>There are some exciting events coming up around the Charlotte area which I'll be speaking at. Next weekend is the Charlotte Code Camp Spring 2008. I'll be speaking on what is currently fresh on my mind, and what I believe is very applicable to developers today. The session is titled "What every developer needs to know about IIS 7". Here's the Code Camp agenda: http://www.developersguild.org/Default.aspx?tabid=248 For anyone in the area, I encourage you to register before it fills. IIS 7 has many new changes that affect the developer this time around. With IIS 6, mostly just the server administrator benefited. But, with IIS 7, there are many changes that apply to the developer. There are deployment changes, web.config configuration changes, the...(&lt;a href="http://blogs.orcsweb.com/scott/archive/2008/05/05/upcoming-speaking-engagements.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.orcsweb.com/aggbug.aspx?PostID=32497" width="1" height="1"&gt;</description></item><item><title>Enabling XP and Windows Server 2003 to Search All Files Types</title><link>http://blogs.orcsweb.com/scott/archive/2008/04/04/enabling-xp-and-windows-server-2003-to-search-all-files-types.aspx</link><pubDate>Fri, 04 Apr 2008 14:34:00 GMT</pubDate><guid isPermaLink="false">2330e3f2-49bd-42cb-a16c-a9380a6a6a02:32345</guid><dc:creator>Scott Forsyth&amp;#39;s WebLog</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.orcsweb.com/scott/comments/32345.aspx</comments><wfw:commentRss>http://blogs.orcsweb.com/scott/commentrss.aspx?PostID=32345</wfw:commentRss><description>Searching for file content on your computer or server is a common task and one where you would expect accurate results. You, like so many of us, may have assumed that but found different results. Within Windows 2000 Server, if you entered something in the windows search dialog and clicked "Find", it would find it. But, with Windows Server 2003 or Windows XP, there are a lot of searches that would come up empty, even if you were sure that you had files with the words in them that you were searching for. The reason that the results are different in Windows Server 2003 and Windows XP is because Microsoft decided to only include certain types of files in the search to speed up the search. Even if you set the file type as "All Files and Folders",...(&lt;a href="http://blogs.orcsweb.com/scott/archive/2008/04/04/enabling-xp-and-windows-server-2003-to-search-all-files-types.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.orcsweb.com/aggbug.aspx?PostID=32345" width="1" height="1"&gt;</description><category domain="http://blogs.orcsweb.com/scott/archive/tags/Windows+Server/default.aspx">Windows Server</category><category domain="http://blogs.orcsweb.com/scott/archive/tags/Windows+XP/default.aspx">Windows XP</category></item><item><title>tsadmin command change in Windows Server 2008</title><link>http://blogs.orcsweb.com/scott/archive/2008/04/03/tsadmin-command-change-in-windows-server-2008.aspx</link><pubDate>Thu, 03 Apr 2008 16:18:00 GMT</pubDate><guid isPermaLink="false">2330e3f2-49bd-42cb-a16c-a9380a6a6a02:32339</guid><dc:creator>Scott Forsyth&amp;#39;s WebLog</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.orcsweb.com/scott/comments/32339.aspx</comments><wfw:commentRss>http://blogs.orcsweb.com/scott/commentrss.aspx?PostID=32339</wfw:commentRss><description>I use Remote Desktop all the time to manage servers remotely, and often I join other people's sessions to troubleshoot something with them, or walk through something or other. In Windows Server 2003 (and Windows 2000 Server), the easy way to start up Terminal Services Manager is Start -&amp;gt; Run -&amp;gt; 'tsadmin' -&amp;gt; [Enter]. This calls us Terminal Services Manager where I can right-click on a user and click 'Remote Control', and if they approve, I can join their session. This doesn't work in Windows Server 2008 anymore. The change is ever so slight. In Windows Server 2003 the tool was tsadmin.exe, so typing 'tsadmin' was all that was required to start the tool. Now, in Windows Server 2008, this has been moved to a MMC snap-in and is called tsadmin.msc...(&lt;a href="http://blogs.orcsweb.com/scott/archive/2008/04/03/tsadmin-command-change-in-windows-server-2008.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.orcsweb.com/aggbug.aspx?PostID=32339" width="1" height="1"&gt;</description><category domain="http://blogs.orcsweb.com/scott/archive/tags/Remote+Desktop/default.aspx">Remote Desktop</category></item><item><title>IIS7 blocks viewing access to files in bin and other asp.net folders</title><link>http://blogs.orcsweb.com/scott/archive/2008/03/05/iis7-blocks-viewing-access-to-files-in-bin-and-other-asp-net-folders.aspx</link><pubDate>Wed, 05 Mar 2008 21:31:00 GMT</pubDate><guid isPermaLink="false">2330e3f2-49bd-42cb-a16c-a9380a6a6a02:32223</guid><dc:creator>Scott Forsyth&amp;#39;s WebLog</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.orcsweb.com/scott/comments/32223.aspx</comments><wfw:commentRss>http://blogs.orcsweb.com/scott/commentrss.aspx?PostID=32223</wfw:commentRss><description>I was just asked to help someone troubleshoot a site that worked fine on Windows Server 2003 / IIS6 but didn't work on Windows Server 2008 / IIS7. A file was in a folder under the bin folder on the site and displayed an error when trying to view the page. The path looked something like this: http://www.sitename.com/subfolder/bin/debug/file.xml The subfolder wasn't marked as an application, although that doesn't really matter. The point is that since /bin/ was in the path somewhere, IIS7 wouldn't allow the file.xml to be displayed. It served up a 404.2 error saying file or directory not found. 404 - File or directory not found. The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable. Since...(&lt;a href="http://blogs.orcsweb.com/scott/archive/2008/03/05/iis7-blocks-viewing-access-to-files-in-bin-and-other-asp-net-folders.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.orcsweb.com/aggbug.aspx?PostID=32223" width="1" height="1"&gt;</description><category domain="http://blogs.orcsweb.com/scott/archive/tags/IIS/default.aspx">IIS</category><category domain="http://blogs.orcsweb.com/scott/archive/tags/IIS7/default.aspx">IIS7</category></item><item><title>Professional IIS 7 - Best IIS 7.0 book</title><link>http://blogs.orcsweb.com/scott/archive/2008/02/18/professional-iis-7-best-iis-7-0-book.aspx</link><pubDate>Mon, 18 Feb 2008 17:41:00 GMT</pubDate><guid isPermaLink="false">2330e3f2-49bd-42cb-a16c-a9380a6a6a02:32181</guid><dc:creator>Scott Forsyth&amp;#39;s WebLog</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.orcsweb.com/scott/comments/32181.aspx</comments><wfw:commentRss>http://blogs.orcsweb.com/scott/commentrss.aspx?PostID=32181</wfw:commentRss><description>The title is a bit biased since I co-authored the book, but Professional IIS 7 will be out in print within a couple weeks and I highly recommend picking up a copy! I've had my head buried in this book for months — spending more time that I realized possible, but learning IIS 7 inside out and ultimately enjoying it. (Although I have to admit that sometimes at 4:00 in the morning, trying to hit deadlines, I'm not sure that I realized that I was enjoying it. :)) The book will be in bookstores and shipping online during the 2nd week of March 2008. You can order it directly from Wrox: http://www.wrox.com/WileyCDA/WroxTitle/productCd-0470097825.html or from Amazon.com . We had a great team of authors on this book, each writing in areas that they knew...(&lt;a href="http://blogs.orcsweb.com/scott/archive/2008/02/18/professional-iis-7-best-iis-7-0-book.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.orcsweb.com/aggbug.aspx?PostID=32181" width="1" height="1"&gt;</description><category domain="http://blogs.orcsweb.com/scott/archive/tags/IIS/default.aspx">IIS</category></item><item><title>Application vs. AppDomain</title><link>http://blogs.orcsweb.com/scott/archive/2007/09/02/application-vs-appdomain.aspx</link><pubDate>Sun, 02 Sep 2007 14:21:00 GMT</pubDate><guid isPermaLink="false">2330e3f2-49bd-42cb-a16c-a9380a6a6a02:5171</guid><dc:creator>Scott Forsyth&amp;#39;s WebLog</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.orcsweb.com/scott/comments/5171.aspx</comments><wfw:commentRss>http://blogs.orcsweb.com/scott/commentrss.aspx?PostID=5171</wfw:commentRss><description>A question was asked on a forum that I frequent which I thought was worth writting a blog about. Q: What is the difference between an application and an Appdomain? I understand from my research so far that an Appdomain is a container within which ASPX runs and that Apppool is a process that starts the w3wp.exe worker process within which ASP applications run. A: That's a good question. Here are some key differences: An application is an IIS term, but it's one that ASP.NET utilizes. Essentially it creates a sandbox, or a set of boundaries to separate different sites, or parts of sites, from the others. An AppDomain is a .NET term. (In IIS7, AppDomains play a larger role within IIS, but for the most part it's an ASP.NET term) An AppDomain contains...(&lt;a href="http://blogs.orcsweb.com/scott/archive/2007/09/02/application-vs-appdomain.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.orcsweb.com/aggbug.aspx?PostID=5171" width="1" height="1"&gt;</description><category domain="http://blogs.orcsweb.com/scott/archive/tags/ASP.NET/default.aspx">ASP.NET</category></item><item><title>VS 2008 and .NET 3.5 Beta 2 released</title><link>http://blogs.orcsweb.com/scott/archive/2007/07/26/vs-2008-and-net-3-5-beta-2-released.aspx</link><pubDate>Thu, 26 Jul 2007 21:42:00 GMT</pubDate><guid isPermaLink="false">2330e3f2-49bd-42cb-a16c-a9380a6a6a02:2497</guid><dc:creator>Scott Forsyth&amp;#39;s WebLog</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.orcsweb.com/scott/comments/2497.aspx</comments><wfw:commentRss>http://blogs.orcsweb.com/scott/commentrss.aspx?PostID=2497</wfw:commentRss><description>Beta 2 of VS 2008 and .NET 3.5 which was just released a few minutes ago and is available for download. I know I've been really quiet on my blog for a while. I'm still around, just haven't freed up my time enough to do the blogging that I know I should. I figured I would break my silence and mention this release. http://weblogs.asp.net/scottgu/archive/2007/07/26/vs-2008-and-net-3-5-beta-2-released.aspx Scott Guthrie's blog post is a must read. Some key features in VS 2008 and .NET 3.5 are: - LINQ - JavaScript IntelliSense and Debugging - AJAX integrated - Great CSS support - Development can target different versions of the framework - much more...(&lt;a href="http://blogs.orcsweb.com/scott/archive/2007/07/26/vs-2008-and-net-3-5-beta-2-released.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.orcsweb.com/aggbug.aspx?PostID=2497" width="1" height="1"&gt;</description></item><item><title>Registry change for perfmon and PID data</title><link>http://blogs.orcsweb.com/scott/archive/2007/03/19/registry-change-for-perfmon-and-pid-data.aspx</link><pubDate>Tue, 20 Mar 2007 02:34:00 GMT</pubDate><guid isPermaLink="false">2330e3f2-49bd-42cb-a16c-a9380a6a6a02:1075</guid><dc:creator>Scott Forsyth's WebLog</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.orcsweb.com/scott/comments/1075.aspx</comments><wfw:commentRss>http://blogs.orcsweb.com/scott/commentrss.aspx?PostID=1075</wfw:commentRss><description>Perfmon is a great tool for mining performance data on a server and has a slew of objects and counters to expose most any type of data. As nice as it is, there is one thing that can be difficult to do, and that is to view data for temporary objects. For example IIS worker processes only live until the next recycle or restart. If there are many worker processes on the server, the default view doesn&amp;#39;t allow you to tell which is which. Notice in the screenshot that there are three w3wp.exe worker processes on this server in the section on the right, but you can&amp;#39;t tell from this view which belongs to which worker process. A co-worker of mind pointed me to this great registry setting today that takes care of this. http://support.microsoft.com/kb/281884...(&lt;a href="http://blogs.orcsweb.com/scott/archive/2007/03/19/registry-change-for-perfmon-and-pid-data.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.orcsweb.com/aggbug.aspx?PostID=1075" width="1" height="1"&gt;</description><category domain="http://blogs.orcsweb.com/scott/archive/tags/Performance+Tuning/default.aspx">Performance Tuning</category></item><item><title>1000MB is not 1GB</title><link>http://blogs.orcsweb.com/scott/archive/2007/02/27/1000mb-is-not-1gb.aspx</link><pubDate>Tue, 27 Feb 2007 14:12:00 GMT</pubDate><guid isPermaLink="false">2330e3f2-49bd-42cb-a16c-a9380a6a6a02:895</guid><dc:creator>Scott Forsyth's WebLog</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.orcsweb.com/scott/comments/895.aspx</comments><wfw:commentRss>http://blogs.orcsweb.com/scott/commentrss.aspx?PostID=895</wfw:commentRss><description>I had an interesting situation come up yesterday that I thought would be worth writing about. As a web host here at www.orcsweb.com , we offer disk space, but obviously need to set some type of limits. One of our clients had an allotment of 1,140 MB. (That is an odd number, but that&amp;#39;s what it worked out to.) While working with him a couple of weeks ago, I checked his disk usage by right-clicking on the folder in windows explorer and clicking on properties. The space that it told me was 1.14GB, which I relayed on to the client. So far so good, it seemed that he was right at his limit. Yesterday, an automated process checked the disk usage on his site, calculated his usage at 1,170MB and sent him an email asking for him to address the disk...(&lt;a href="http://blogs.orcsweb.com/scott/archive/2007/02/27/1000mb-is-not-1gb.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.orcsweb.com/aggbug.aspx?PostID=895" width="1" height="1"&gt;</description><category domain="http://blogs.orcsweb.com/scott/archive/tags/General/default.aspx">General</category></item><item><title>PowerShell Cheat Sheet</title><link>http://blogs.orcsweb.com/scott/archive/2007/01/25/powershell-cheat-sheet.aspx</link><pubDate>Thu, 25 Jan 2007 21:50:00 GMT</pubDate><guid isPermaLink="false">2330e3f2-49bd-42cb-a16c-a9380a6a6a02:640</guid><dc:creator>Scott Forsyth's WebLog</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.orcsweb.com/scott/comments/640.aspx</comments><wfw:commentRss>http://blogs.orcsweb.com/scott/commentrss.aspx?PostID=640</wfw:commentRss><description>Here&amp;#39;s a must-have cheat sheet for PowerShell. Jeffrey Snover has put together an excellent doc that is well worth printing off and keeping handy for anyone working with PowerShell: http://blogs.msdn.com/powershell/archive/2007/01/24/powershell-cheat-sheet.aspx...(&lt;a href="http://blogs.orcsweb.com/scott/archive/2007/01/25/powershell-cheat-sheet.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.orcsweb.com/aggbug.aspx?PostID=640" width="1" height="1"&gt;</description><category domain="http://blogs.orcsweb.com/scott/archive/tags/PowerShell/default.aspx">PowerShell</category></item></channel></rss>