PowerShell is our newest and coolest command line shell and scripting language. It is built on the .Net Framework and introduces features that enable command-line users and script writers to leverage the power of that foundation. It introduces a number of powerful new concepts, but it enables you to reuse both the knowledge you have gained and the scripts you have created within the Windows Command Prompt and Windows Script Host environments.
There are over 130 standard commandlets ("cmdlets") for completing common system administration tasks such as working with the registry. Exchange 2007 was the first team that worked with PowerShell and created over 350 cmdlets to manage an Exchange 2007 environment. Other products like Operations Manager 2007, Virtual Machine Manager are also leveraging the power of PowerShell. PowerShell is a verb-noun based scripting language for example the help command is Get-Help.
With Vista now released we also introduced 13 new WMI providers like Bitlocker, TPM, IIS7, .... we are also able to query those WMI providers trough PowerShell. Lot's of customers ask us questions like do I have to learn .Net, I have a set of tools do I need to rewrite them? ...
Well the good news is that you don't need to learn .Net and you can still use your existing tools. It's really easy to start with PowerShell you can learn on your own pace and there is online help available. What I personally do like about this shell is that it's very easy to try a script out, you can actually execute line by line and then put it in a script. This was rather difficult with for example VBScript where you had to debug the script.
It's also easy to access your files and even registry from within the shell - "cd HKCU". With this simple command you just have access to the HKEY_CURRENT_USER hive in the registry.
There are some third parties that leverages the power of Powershell:
NetCmdlets PowerGadgets (tutorial for IT Pro's)
PowerGadgets (tutorial for IT Pro's)
And I am sure that there are many other tools available today.
Channel 9 tag: http://channel9.msdn.com/tags/Monad Team blog: http://blogs.msdn.com/PowerShell/O Mark van Orsouw’s blog: http://thepowershellguy.com Arul Kumaravel's Blog: http://blogs.msdn.com/arulk Lee Holmes' Blog: http://www.leeholmes.com/blog Abhishek Agrawal’s Blog: http://abhishek225.spaces.msn.com/PersonalSpace.aspx MshAnalyzer tool: http://www.karlprosser.com/coder/?cat=8
Channel 9 tag: http://channel9.msdn.com/tags/Monad
Team blog: http://blogs.msdn.com/PowerShell/O
Mark van Orsouw’s blog: http://thepowershellguy.com
Arul Kumaravel's Blog: http://blogs.msdn.com/arulk
Lee Holmes' Blog: http://www.leeholmes.com/blog
Abhishek Agrawal’s Blog: http://abhishek225.spaces.msn.com/PersonalSpace.aspx
MshAnalyzer tool: http://www.karlprosser.com/coder/?cat=8
I can't share a lot of information with you about how PowerShell and Longhorn server will work together but as soon as I know I will post it onto this blog.
By the way there are two PowerShell sessions planned during the Dev & IT Pro Days 2007 - Bruce Payette will deliver them.
I have a little comment about your post. The right command to be able to browse the registry is "cd HKCU:" (without quotes). You must put : after HKCU.
There are meny other Drives, like the certificate store, another drive for functions and variables avaliable in the shell, Sharepoint (under development on CodePlex), and so on...
Congratulations for your blog!
Brazilian Scripting MVP
Bach. Ciencias da Computação - USP S. Carlos
Scripting blog: http://viniciuscanto.blogspot.com
Thanks for pointing that out it's indeed cd HKCU: without quotes, I will change that on the post.
Maybe you should mentionned that it's not a new feature for Longhorn as this shell is already available for Windows XP, Windows Server 2003 and Windows Vista. Then, why is this a reason to look at Longhorn if it's already available... ? I guess they will integrate more cmdlet concerning Longhorn management but it's not mentionned in your blog if that's the case.
That could indeed be the case but I don't have any details that I can share right now. But as soon as I can I will share details.
Just wanted to make a point that PowerShell will be important in Longhorn.
Well, what I believe is if you are going to install Longhorn core, best way it can be managed is, by using command line and command line's best tool is powershell. So more familiar you get with powershell, more easilu,you will able to manage longhorn-Core, and if hypervisor also comes in it, then powershell would be best way to work on VM mgmt, Of course it would require addition of lots CMDlets.
You are right PowerShell is the shell and scripting tool to manage your environment unfortunately PowerShell will not run on a server core box. Because server core doesn't have the CLR (no .NET) we cannot support PowerShell. We cannot add the CLR because everything else would be added if we did that.
We are working with the CLR team to make this more modular and to be able in the future (don't know when) to have PowerShell as the shell in server core.
However PowerShell can be used to manage VM environment.
This week I was preparing for my TechNet evening session about longhorn server and I was looking at what
With Windows Vista we've improved the security of the platform dramatically, because Windows Vista and
When I talked about the server management improvements in the first part of this series I explained that
poki co tylko trzy, ale w przyszlosci bedzie wiecej: Server Management Improvements PowerShell IIS7.o
It has been quite a while now since I wrote part 8 of this series. I must admit I tried to start this
Arlindo Alves the Belgian IT Pro Evangelist wrote a blogpost series about 10 Reasons you want to look