Extending Microsoft.Web.Administration through PowerShell (Part II)

PowerShell and IIS 7

PowerShell for Everyone — Fri, 04 Jan 2008 10:06:51 GMT

The introduction of IIS 7 with Windows 2008 brings a managed code (.NET) API for IIS. This means we can administer it through PowerShell. Add the remoting features of V2 and you have a very powerful ...

【收藏】本周ASP.NET英文技术文章推荐[12/03 - 12/09]（

Jacky_xu — Wed, 31 Oct 2007 03:08:49 GMT

摘要

昨天诸事不顺，早晨起来肠胃开始不舒服。下午坚持写好本篇推荐文章之后，还没发布居然鬼使神差一般就把草稿删除了？！WindowsLiveWriter处理数据安全方面确实有一套，删除的草稿无论用...

IIS7 - post #27 - Powershell & Microsoft IIS Web.administration blog

Steve Schofield Weblog — Sun, 14 Jan 2007 05:59:35 GMT

Found this blog by Tobin Titus . Definitely check it out! http://blogs.iis.net/tobintitus/archive/2006/11/30/powershell-and-microsoft-web-administration.aspx

re: Extending Microsoft.Web.Administration through PowerShell (Part II)

TobinTitus — Sun, 03 Dec 2006 05:47:42 GMT

I've been playing around with the bugs in my PowerShell code and have made some updates to the article. If you are interested, aside from the problems I listed above, I was not getting good matches because the $args[0] inside the Where-Object statement are not honored. I changed function definition to:

function findsite { $name=$args[0]; (New-Object Microsoft.Web.Administration.ServerManager).Sites | Where-Object {$_.Name -match $name}; }

This appears to have fixed the problem.

I have got the power!!

Server: Microsoft-IIS/7.0\r\n — Sat, 02 Dec 2006 05:46:07 GMT

Hehe :) Not just me! You have got the power as well.... to manage IIS via PowerShell. Honestly, I'm not

re: Extending Microsoft.Web.Administration through PowerShell (Part II)

TobinTitus — Fri, 01 Dec 2006 20:47:29 GMT

In my haste to get this post out before a meeting, I neglected to make some disclaimers. While the code above is meant as an example of a few things you can do with IIS, this is by no means "production ready". In fact, I ran into a few problems last night with regards to the global variables. For instance, since we are assigning those variables when PowerShell starts, any changes we make to the objects may not be reflected in our output. The $iissites is a great addition if all we ever do in powershell is view site state. However, consider what would happen if you did the following:

(findsite default*).Name = "Test";$iismgr.CommitChanges();

Doing a search for the "Default Web Site" again would return the same website even though we've renamed it. That's because it still has the old cache. We might be better off defining findsite as:

function findsite { $iismgr.Sites | Where-Object {$_.Name -match $args[0]} }

Once again, this is conjecture and I haven't tested the code, so please do not consider this production-ready. Test your scripts thoroughly to validate that they are updating your data properly before you put your reputation behind them!