<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>A Quick Look at the New PowerShell Activities in the DPM and VMM IPs</title><link>http://blogs.technet.com/b/orchestrator/archive/2012/05/09/a-quick-look-at-the-new-powershell-activities-in-the-dpm-and-vmm-ips.aspx</link><description>When we on the product team create an integration pack for a product, whether it’s for System Center or another Microsoft products, or even a 3rd-party product, our goal is not to try and replicate everything that product does in the form of runbook activities</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: A Quick Look at the New PowerShell Activities in the DPM and VMM IPs</title><link>http://blogs.technet.com/b/orchestrator/archive/2012/05/09/a-quick-look-at-the-new-powershell-activities-in-the-dpm-and-vmm-ips.aspx#3501409</link><pubDate>Thu, 31 May 2012 23:20:25 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3501409</guid><dc:creator>Robert_Hearn</dc:creator><description>&lt;p&gt;Yep. I agree. The issue is that only the VMM and DPM IP&amp;#39;s share the same PowerShell infrastructure behind the scenes, so it was easy to implement the activity on both of those. None of the other IPs share that infrastructure, so adding that capability to the other IPs becomes much more of an effort.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3501409" width="1" height="1"&gt;</description></item><item><title>re: A Quick Look at the New PowerShell Activities in the DPM and VMM IPs</title><link>http://blogs.technet.com/b/orchestrator/archive/2012/05/09/a-quick-look-at-the-new-powershell-activities-in-the-dpm-and-vmm-ips.aspx#3501404</link><pubDate>Thu, 31 May 2012 23:06:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3501404</guid><dc:creator>Brian Pavnick</dc:creator><description>&lt;p&gt;Me again. This would be extremely useful for pretty much any other IP, imo. I can think of many uses for this in SCOM. - vbpav&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3501404" width="1" height="1"&gt;</description></item><item><title>re: A Quick Look at the New PowerShell Activities in the DPM and VMM IPs</title><link>http://blogs.technet.com/b/orchestrator/archive/2012/05/09/a-quick-look-at-the-new-powershell-activities-in-the-dpm-and-vmm-ips.aspx#3501338</link><pubDate>Thu, 31 May 2012 19:17:51 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3501338</guid><dc:creator>Brian Pavnick</dc:creator><description>&lt;p&gt;Very clever idea! May I suggest carrying this same idea over to the VMware vCenter IP? By integrating the VMware vCenter IP with VMware&amp;#39;s PowerCLI, you can achieve the exact same functionality as this. That would be most excellent! - Brian Pavnick | Veeam Software | Solutions Architect&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3501338" width="1" height="1"&gt;</description></item></channel></rss>