Leave it up to MS...
To ruin something which has a tremendous potential. I consider myself a PowerShell fan, I'm really in favor of the environment because it's the best of both worlds... It mimics and feels like a Unix shell but has everything good about Windows on board. Referring to the entire .NET library. You can actually use .NET commands and routines straight from within PS.
If you're familiar with the Unix commandline you'll have everything you need to become familiar with PS. 'man man' works like a charm, the use of \ isn't mandatory ('cd /users/peter' works just as fine as 'cd \users\peter') and I love the command chaining. Because everything in PS is an object you can do some crazy things with the info you receive. And best yet: connecting to other servers isn't a problem either.
I used to have a PS script which would check the event logs on 4 different Windows servers and warn me when something odd was found. That is innovation for you.
Of course it started going downhill when they introduced mandatory translations. All of a sudden "man man" stopped working because I happened to be using a Dutch Windows version. My Windows 'culture' was nl-NL, so the help system looked for Dutch contents. Which unfortunately weren't made, and I couldn't force PS to use the English locale. Effectively rending the dynamic help system useless. It was made with help updates in mind, I think I never ever got one. So why did they need to break the help system in the first place?
Sure, I could use a hack (copy the English help into the Dutch help location), which I ended up doing, but ye gods... It's a really good way to make me lose interest in an environment: adding plain out sloppy and crappy updates. Even though I'm a big PS fan... Heck: you can even use PS to perform administration tasks for SharePoint, they're really taking it quite far.
And instead of learning from their mistakes they just keep blundering onwards while continuing to wonder why their user amounts keeps dropping and dropping.