<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments on: Windows PowerShell for Administrators</title>
	<atom:link href="http://4sysops.com/archives/windows-powershell-for-administrators/feed/" rel="self" type="application/rss+xml" />
	<link>http://4sysops.com/archives/windows-powershell-for-administrators/</link>
	<description>For Windows Administrators</description>
	<lastBuildDate>Sun, 21 Mar 2010 23:51:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Michael</title>
		<link>http://4sysops.com/archives/windows-powershell-for-administrators/comment-page-1/#comment-17121</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Wed, 30 May 2007 20:16:15 +0000</pubDate>
		<guid isPermaLink="false">http://4sysops.com/archives/windows-powershell-for-administrators/#comment-17121</guid>
		<description></description>
		<content:encoded><![CDATA[<p>Jeffrey, I agree, it is often just a matter of taste when it comes to using a GUI or the CLI. It is certainly a good move to ensure that everything can be done via CLI. However, I think, the main reason why Microsoft introduced PowerShell doesn&#8217;t have much to do with making things automated. This was already possible in the past to a relatively high degree. We have plenty of scripts in different scripting languages here doing just that with many Microsoft products. I admit, PowerShell probably will even improve the situation. However, the main reason for introducing PowerShell has something to do with marketing. Microsoft wants to persuade Unix admins to move to Windows. And those guys love hacking on the command line. There is no doubt about it. I guess Don is one of them <img src='http://4sysops.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />  Actually, I enjoy that too whenever I logon on a Linux box. So, I know exactly where they are coming from. I just wish I had more time for this. I havenâ€™t. So, I use GUI tools when I work with Windows.</p>
<p>Don, if you always know which lines â€œto bang outâ€? youâ€™re certainly faster. However, first you have to invest quite some time to learn PowerShell. I suppose, many Windows admins simply donâ€™t have the time for this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Don</title>
		<link>http://4sysops.com/archives/windows-powershell-for-administrators/comment-page-1/#comment-16826</link>
		<dc:creator>Don</dc:creator>
		<pubDate>Thu, 24 May 2007 21:53:49 +0000</pubDate>
		<guid isPermaLink="false">http://4sysops.com/archives/windows-powershell-for-administrators/#comment-16826</guid>
		<description>I guess my take is this: I&#039;d rather have a command-line environment where I can bang out a line or two to administer a dozen machines... than have to hunt down a third-party GUI to do it. MS is bad about giving us multi-machine admin GUIs... maybe if they weren&#039;t, I&#039;d feel differently!! I&#039;m just adept with command-lines - always have been - and feel they get me &quot;closer&quot; to the guts of whatever I&#039;m trying to run. Plus, unlike Mr. Snover, I really don&#039;t like GUIs for administrative stuff .</description>
		<content:encoded><![CDATA[<p>I guess my take is this: I&#8217;d rather have a command-line environment where I can bang out a line or two to administer a dozen machines&#8230; than have to hunt down a third-party GUI to do it. MS is bad about giving us multi-machine admin GUIs&#8230; maybe if they weren&#8217;t, I&#8217;d feel differently!! I&#8217;m just adept with command-lines &#8211; always have been &#8211; and feel they get me &#8220;closer&#8221; to the guts of whatever I&#8217;m trying to run. Plus, unlike Mr. Snover, I really don&#8217;t like GUIs for administrative stuff .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeffrey Snover</title>
		<link>http://4sysops.com/archives/windows-powershell-for-administrators/comment-page-1/#comment-16787</link>
		<dc:creator>Jeffrey Snover</dc:creator>
		<pubDate>Wed, 23 May 2007 21:40:15 +0000</pubDate>
		<guid isPermaLink="false">http://4sysops.com/archives/windows-powershell-for-administrators/#comment-16787</guid>
		<description>We don&#039;t view this as a GUI vs CLI (Command Line Interface).  We LOVE GUIs.  We view this as a GUI AND CLI story.  Someones you want one, sometimes you&#039;ll want the other.  Our goal is to layer all the GUIs over CLI so that we ensure that everything can be done via that CLI and thus everything can be automated.

Jeffrey Snover [MSFT]
Windows Management Partner Architect
Visit the Windows PowerShell Team blog at:    http://blogs.msdn.com/PowerShell
Visit the Windows PowerShell ScriptCenter at:  http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx</description>
		<content:encoded><![CDATA[<p>We don&#8217;t view this as a GUI vs CLI (Command Line Interface).  We LOVE GUIs.  We view this as a GUI AND CLI story.  Someones you want one, sometimes you&#8217;ll want the other.  Our goal is to layer all the GUIs over CLI so that we ensure that everything can be done via that CLI and thus everything can be automated.</p>
<p>Jeffrey Snover [MSFT]<br />
Windows Management Partner Architect<br />
Visit the Windows PowerShell Team blog at:    <a href="http://blogs.msdn.com/PowerShell" rel="nofollow">http://blogs.msdn.com/PowerShell</a><br />
Visit the Windows PowerShell ScriptCenter at:  <a href="http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx" rel="nofollow">http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
