<?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/b/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>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: WINRM</title><link>http://blogs.msdn.com/b/powershell/archive/2007/10/30/winrm-exe.aspx#10154354</link><pubDate>Fri, 15 Apr 2011 07:32:07 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10154354</guid><dc:creator>Pat</dc:creator><description>&lt;p&gt;Ha ha, I was once faced with what to call a formatting function in a python script I had years ago.&lt;/p&gt;
&lt;p&gt;The only thing I could think of was &amp;quot;PrettyPrint&amp;quot; :)&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10154354" width="1" height="1"&gt;</description></item><item><title>re: WINRM</title><link>http://blogs.msdn.com/b/powershell/archive/2007/10/30/winrm-exe.aspx#9957510</link><pubDate>Wed, 03 Feb 2010 12:31:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9957510</guid><dc:creator>Bill Sullens</dc:creator><description>&lt;p&gt;2 options were checked when I enyered this Module I checked 3 others - results areDisable Net Logon; Disable Smart Card; Memory dispaly Option; Increase Ocon Cache size; and Disable &amp;nbsp;Low Disk Space Warning WERE checked. I ran the module, which ran very long, infact I went to bed. I have second thoughts about. I now have 2nd thoughts about disabling the Low disk warning message, but when I check only this one option it says that no options will be changed. How do I leave the other 4 options as they now are and only enable the Low Disk Warning Message?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9957510" width="1" height="1"&gt;</description></item><item><title>re: WINRM</title><link>http://blogs.msdn.com/b/powershell/archive/2007/10/30/winrm-exe.aspx#9957505</link><pubDate>Wed, 03 Feb 2010 12:21:27 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9957505</guid><dc:creator>Bill Sullens</dc:creator><description>&lt;p&gt;Since I am in this check - uncheck WINRM loop this is maybe not important yet - but how do I exit the Start Up Command module?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9957505" width="1" height="1"&gt;</description></item><item><title>re: WINRM</title><link>http://blogs.msdn.com/b/powershell/archive/2007/10/30/winrm-exe.aspx#9957503</link><pubDate>Wed, 03 Feb 2010 12:18:28 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9957503</guid><dc:creator>Bill Sullens</dc:creator><description>&lt;p&gt;WINRM - I seem to be in a loop. When I click Apply in System Startup, when it is set (checked) the Program stops - implying uncheck it and vice-versa. It (WINRM)always seems to be associated with local drive K which is my 'C' drive from my previous computer - which is a Rocket Fish cabinet, which I maintain to not lose old data. But it can't be checked and unchechecked at the same time, and that seems to be the loop I am in. Help&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9957503" width="1" height="1"&gt;</description></item><item><title>re: WINRM</title><link>http://blogs.msdn.com/b/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;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9843920" width="1" height="1"&gt;</description></item><item><title>limitations</title><link>http://blogs.msdn.com/b/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;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8466161" width="1" height="1"&gt;</description></item><item><title>WS-Management или WinRM</title><link>http://blogs.msdn.com/b/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;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=7199341" width="1" height="1"&gt;</description></item><item><title>re: WINRM</title><link>http://blogs.msdn.com/b/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>PowerShell Team</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;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=5775576" width="1" height="1"&gt;</description></item><item><title>re: WINRM.exe </title><link>http://blogs.msdn.com/b/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;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=5775084" width="1" height="1"&gt;</description></item><item><title>MSDN Blog Postings  &amp;raquo; WINRM.exe</title><link>http://blogs.msdn.com/b/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;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=5773732" width="1" height="1"&gt;</description></item></channel></rss>