<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>Have your PowerShell and our Cmdlets too...</title><link>http://blogs.msdn.com/scshell/archive/2007/01/03/have-your-powershell-and-our-cmdlets-too.aspx</link><description>Adding the Operations Manager Snapin As you may already know, the PowerShell is an extensible environment, as such we have tried to create a useful starting point for you by loading the Operations Manager Cmdlets and functions within a PowerShell environment</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Have your PowerShell and our Cmdlets too...</title><link>http://blogs.msdn.com/scshell/archive/2007/01/03/have-your-powershell-and-our-cmdlets-too.aspx#1418007</link><pubDate>Sat, 06 Jan 2007 00:36:36 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1418007</guid><dc:creator>scshell</dc:creator><description>&lt;p&gt;I have updated this post several times because of your feedback. Please take the time to read the whole post as it will address issuses regarding the loading of Operations Manager functions like &amp;nbsp;Get-OperationsManagerCommand. I also added info on setting the correct provider location which is necessary before running any of the Operations Manager Cmdlets.&lt;/p&gt;
</description></item></channel></rss>