Powershell for Windows Server and Exchange Administration
If you have recently began using Windows 2008 servers and Exchange 2007 or 2010 then hopefully you are aware that these 2 products in particular are designed to be used with Powershell.
To become a proficient Exchange administrator you are going to have to learn Powershell. It’s a necessity to becoming an Exchange expert. If you wish to undertake Exchange certifications you are going to need to know Powershell because part of the exam will require you to answer questions on the Exchange management shell or EMS.
EMS is built upon Powershell, Powershell is fairly new on the scene. If you are using Exchange 2003 or are new to Exchange completely then you may not have had an opportunity to play around with Powershell.
Powershell is a scripting platform and command line platform. Different experts have different opinions but Powershell effectively does both and does it rather well.
There are 2 versions of Powershell currently. Version 2 includes lots of flexibility.
You can manage some aspect of Exchange 2007/2010 with the Exchange Management Console (EMC) but you can manage everything using the Exchange Management Shell (EMS), so there is a difference.
The console is actually a GUI version and Powershell commands and parameters are running in the background when you are making changes in Exchange using the console. You will notice when doing some tasks via the GUI that it will actually tell you the actual Powershell commands that when run to accomplish a task. Ideal if scripting is not your strongest subject.
Learning Powershell is not an option but a necessity. Not just from an exam perspective but as an administrator there are things that can only be done in PS.
Local Shell or Remote Shell
This is a new feature in 2010 and not available in 2007.