<?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>WINRM</title><link>http://blogs.msdn.com/powershell/archive/2007/10/30/winrm-exe.aspx</link><description>WINRM is the CLI interface to our WS-MGMT protocol. The neat thing about this is that you can call it from PowerShell to manage remote systems that don't have PowerShell installed on them (including Server Core systems and Raw hardware). I was trying</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>MSDN Blog Postings  &amp;raquo; WINRM.exe</title><link>http://blogs.msdn.com/powershell/archive/2007/10/30/winrm-exe.aspx#5773732</link><pubDate>Tue, 30 Oct 2007 04:00:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5773732</guid><dc:creator>MSDN Blog Postings  » WINRM.exe</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://msdnrss.thecoderblogs.com/2007/10/29/winrmexe/"&gt;http://msdnrss.thecoderblogs.com/2007/10/29/winrmexe/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: WINRM.exe </title><link>http://blogs.msdn.com/powershell/archive/2007/10/30/winrm-exe.aspx#5775084</link><pubDate>Tue, 30 Oct 2007 05:28:42 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5775084</guid><dc:creator>jachymko</dc:creator><description>&lt;p&gt;Except that the WinRM executable is not an exe, but a HUGE (3270 line)VBScript :-)&lt;/p&gt;
&lt;p&gt;Just wondering how many lines would a WinRM.ps1 take... :-)&lt;/p&gt;</description></item><item><title>re: WINRM</title><link>http://blogs.msdn.com/powershell/archive/2007/10/30/winrm-exe.aspx#5775576</link><pubDate>Tue, 30 Oct 2007 06:21:27 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:5775576</guid><dc:creator>PowerShellTeam</dc:creator><description>&lt;p&gt;&amp;gt; Except that the WinRM executable is not an exe, but a HUGE (3270 line)VBScript :-)&lt;/p&gt;
&lt;p&gt;You are quite correct. &amp;nbsp;My error.&lt;/p&gt;
&lt;p&gt;I've updated the posting.&lt;/p&gt;
&lt;p&gt;Thanks for setting me straight!&lt;/p&gt;
&lt;p&gt;Jeffrey Snover [MSFT]&lt;/p&gt;
&lt;p&gt;Windows Management Partner Architect&lt;/p&gt;
</description></item><item><title>WS-Management или WinRM</title><link>http://blogs.msdn.com/powershell/archive/2007/10/30/winrm-exe.aspx#7199341</link><pubDate>Tue, 22 Jan 2008 19:03:57 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7199341</guid><dc:creator>Илья Сазонов</dc:creator><description>&lt;p&gt;Введение в WS-Management или WinRM&lt;/p&gt;
</description></item><item><title>limitations</title><link>http://blogs.msdn.com/powershell/archive/2007/10/30/winrm-exe.aspx#8466161</link><pubDate>Wed, 07 May 2008 19:58:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8466161</guid><dc:creator>not sure its enough</dc:creator><description>&lt;p&gt;In order to use the results, you still need a priori knowledge of the key properties so you can extract the values and create the EPR.&lt;/p&gt;
&lt;p&gt;How do you avoid having to know the concrete sub-class that will be returned in order to walk-through the returned instances in a loop?&lt;/p&gt;</description></item><item><title>re: WINRM</title><link>http://blogs.msdn.com/powershell/archive/2007/10/30/winrm-exe.aspx#9843920</link><pubDate>Wed, 22 Jul 2009 00:21:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9843920</guid><dc:creator>contriver</dc:creator><description>&lt;p&gt;this is also handy (needed) for running winrm on a system that a) doesnt have it and b) you dont have install privileges on, or alternately, a portable winrm on usb.&lt;/p&gt;</description></item></channel></rss>