You should do it. I worked with PowerShell a few years ago and it was much better experience than shell scripting with bash or tcsh or others. Things I liked:
You get an IDE for free. It's quite usable out of the box and it's really nice for learning the language.
It's less reliant on punctuation. There are a few special symbols and they are highly regular in their usage. Syntax feels more readable (to me) than that of bash thanks to this.
You deal with objects. You can reflect on them (great for exploration), call methods on them, while still having generic ways for composing them and manipulating in large quantities. Yet the language itself is not object oriented, which makes it much simpler than it would be otherwise.
You get the whole .NET to use. Or most of it. You can basically instantiate and use any .NET class (and COM objects and other such things) without hassle.
There are a few concepts in the language which unify many concepts from the system. For example you can "cd" into a directory or a key in the registry or a network share or any number of other things which can be thought of as a listable resource.
This is coming from a programmer, so it's missing things probably important for sysadmins, like security management and built in process of signing and verifying scripts signatures before running them.
One think I didn't like: it was slow. The other: nothing worked on it (I mean things like python's virtualenv, which comes with .bat file, but not with .ps1 file), even Visual Studio command prompt. I ended up writing some PowerShell code for translating cmd.exe variables to PS ones.
And, of course, it's Microsoft, so forget about running it somewhere else. But, all in all, if you have to script something in Windows, it's by far better than any other tool.
You get an IDE for free. It's quite usable out of the box and it's really nice for learning the language.
It's less reliant on punctuation. There are a few special symbols and they are highly regular in their usage. Syntax feels more readable (to me) than that of bash thanks to this.
You deal with objects. You can reflect on them (great for exploration), call methods on them, while still having generic ways for composing them and manipulating in large quantities. Yet the language itself is not object oriented, which makes it much simpler than it would be otherwise.
You get the whole .NET to use. Or most of it. You can basically instantiate and use any .NET class (and COM objects and other such things) without hassle.
There are a few concepts in the language which unify many concepts from the system. For example you can "cd" into a directory or a key in the registry or a network share or any number of other things which can be thought of as a listable resource.
This is coming from a programmer, so it's missing things probably important for sysadmins, like security management and built in process of signing and verifying scripts signatures before running them.
One think I didn't like: it was slow. The other: nothing worked on it (I mean things like python's virtualenv, which comes with .bat file, but not with .ps1 file), even Visual Studio command prompt. I ended up writing some PowerShell code for translating cmd.exe variables to PS ones.
And, of course, it's Microsoft, so forget about running it somewhere else. But, all in all, if you have to script something in Windows, it's by far better than any other tool.