One of the more astonishing things about PowerShell is its continued adoption among the many different product groups within Microsoft (and the entire IT community as well). This truly is a Cinderella story. The IIS7 group is to some extent also adopting PowerShell as a method for management. Now, I’m using the word adoption loosely as the IIS7 group has not (as of yet) taken the same approach as the Exchange 2007 product group. In other words, at the time of this blog, the IIS7 group has focused more effort on enhancing the manageability of IIS7. For example:
Where’s the cmdlets? As a 1980’s grandma once pointed out, there seems to be something missing. As you may have noticed in the above list, and my statement about the product group’s focus, there are (at this time) no default set of cmdlets that an IIS administrator can readily use to manage IIS7. This however, doesn’t mean that IIS7 cannot be managed by PowerShell. On the contrary, thanks to these new interfaces IIS7 is very manageable from PowerShell. The management methodology is just different then from what we have seen. Rather than just firing up a management shell like the Exchange Management Shell, administrators just need to construct their own PowerShell management/automation tools. These tools can be in the form of PowerShell scripts. Or, if you are feeling randy (and don’t want to wait for the IIS7 product team to code them) you can construct your own IIS7 PowerShell cmdlets. Chris Adams has a good blog series that shows you how to do this. link For all of today’s Microsoft news, visit Microsoft Subnet
