Discussion on:

10 PowerShell commands every Windows admin should know

Indispensable for obtaining the methods and events of an object.

As in:
get-process|get-member

I'm looking for recommended manuals or downloads. This article is a start, but I'm looking for something both meatier and more introductory.

Thanks.

powersell.com

Depending on how in depth you want to get there are many resources.. if you want just a simple introduction just google "powershell tutorial" and pick one.

If however you want a more in depth primer that will take some time to work through i suggest the Powershell Owners Manual on technet:
http://technet.microsoft.com/en-us/library/ee221100.aspx

BOOM

The 'book is available for free' link returns a 404. I can find links to the second book referenced (PowerShell for servers), but apparently the first one has gone the way of out own "E Lie" discussion.

Thanks anyway.

Go to the second blog entry (for the server stuff) and download from there. It includes the first (general) book as well as the second (server) book.

The article states that the default execution policy is Restricted. I think that statement is only true for PS 1.0 I believe in PS 2.0 the default execution policy is RemoteSigned.

Brian - ok... I'll admit that I'm not in mainstream IT anymore, but still maintain a finger or 2 in it...
So pardon my ignorance if it shows...but I don't get this. Why is the GUI King MS switching gears and going the way of Unix, Linux - ala cmd line for admins?? This seems totally against everything the've stood for since the dying dos days... and gui took over. This seems like a step back. Why is everyone ok with this? Seems like a pain in the ass!

Microsoft finally recognised that some System Admins weren't limited to the GUI and wanted a tool that could really allow us to administrate. It was also obvious that the various GUI management tools lacked scope as the systems became more complex and that there was a need for consistency.

I'm more that "OK" with PowerShell. I can use PowerShell command line for those things that I'd normally do with the management GUI and I can also write and reuse scripts to do more complex tasks. And I can do it for Exchange, SQL server, AD, VMware, Operations Manager, MS Clustering, WMI...

WITH A SINGLE TOOL.

I could go on but you probably get the point.

When you posted the same opinion here:

http://techrepublic.com.com/5208-13583-0.html?forumID=102&threadID=318613&messageID=3406483&tag=content;leftCol

As Neil pointed out, MS is making PowerShell the main management interface across most of its products. One CLI is easier to learn than multiple GUIs.

Still trying to figure out how to export to pst from windows 7 though.