|
I've dabbled with powershell over the years and not really found a place where I couldn't do the job just a easily with a bit of python/cygwin/wmic/dos (read that last one as windows batch). It's probably just familiarity with these other tools but I've not seen anywhere its been a real NEED to use powershell. |
|||||
|
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, see the FAQ.
|
See this post on SO, which is slowly becoming the canonical answer to this question. |
|||
|
|
I've usually used VBScript for management tasks. However you end up relying on COM servers to do anything hard, many of which aren't standard on Windows so you have to buy (and remember to install) third party COM servers. In particular x64 causes problems because all my COM servers are 32 bit, so I end up having to run the x86 version of cscript from \windows\syswow64. I have played with using C#, but it's compiled not interpreted so it's more hassle, and there's a fair bit of (programmer) overhead for simple tasks. I'm far from up to speed with Powershell, but what it offers me is a one stop shop for doing everything. The standard commandlets are pretty comprehensive, and it intergrates with .Net pretty well for when you want something more unusual. Preet, in you post you refer to using "a bit of python/cygwin/wmic/dos". Well me too, but that's four solutions, and you can replace them all by learning Powershell. There will still be the complicated scripts that I'll probably do in VBScript, but Powershell can do that majority of what I need. JR |
|||||
|
|
If you're an admin and you're going to manage Microsoft server applications in the near future - you'll need to learn powershell. That's just how it is ^^ Most new systems they're releasing are managed using powershell and the slow-ass UIs built upon that are often pretty useless and they all work by issuing powershell cmdlets in the background. As RainyRat already pointed out about Exchange 2007 - apply this concept to any upcoming or newly released Microsoft system and the picture will become more clear. But sure, for regular maintenance scripting of old or existing systems today, it hasn't taken off yet. At least not in my book - mostly because you often want support for whatever you do in a lot of older systems like Windows 2003/XP without having to deploy a new "engine" as well. When platforms are upgraded to 2008+ and Win7+ it might become more useful in this regard as well. |
|||||
|
|
For regular admin stuff? No, not yet - .BATs or (at a stretch) VBScript still do the job for me. For managing Exchange 2007, however, it's rapidly becoming indispensable for me. There's a whole raft of things in Ex07 that you can't actually do any other way, because they haven't written the GUI bits for them yet. |
|||
|
|
