PowerShell: Return to the Command-line
- Details
- Category: Blog
- Created on Thursday, 01 September 2011 12:44
- Written by Ryan Hartwick
- Hits: 8159
For those who may not have encountered it, PowerShell is essentially a command-line and scripting tool developed by Microsoft. Some may argue that it represents a regression in the world of network management. While Server 2008 isn't dependent on Windows PowerShell for administration, there are other Microsoft products that are. I find myself wondering if we find ourselves in a transitional period back to a command-line style approach to administration.
Recently I've been spending a lot of time with Exchange 2010, and one of the things that is different between 2010 and 2007 is use of PowerShell. You see, with Exchange 2007 you had the option of using PowerShell (Exchange Management Shell. or the Graphical Console (Exchange Management Console) for all your Administrative needs. At that time it appeared to me as if MIcrosoft were trying to reach the world of Linux administrators who enjoy and thrive on the Shell environment. And why not, why alienate your software from a particular style of administration? It was a smart move. But then with Exchange 2010 we started to see numerous administrative tasks that can only be accomplished using PowerShell. In short, if you want to fully administer your exchange environment, you need to use PowerShell, period.
It got me thinking if we'll see a similar approach in the next iteration of Server. Will administration of Active Directory, DNS, or other roles be limited unless you develop your PowerShell chops? It very well could happen. But why would Microsoft move in this direction, doesn't this alienate those Administrators who prefer the graphical interface? To some extent I think that's a valid argument. I have my own theory as to why Microsoft seems to being putting more emphasis on command-line administration.
There are a lot of network and computer service people who are just flat out not qualified. But luckily for those people, GUI's (graphical user interfaces) are forgiving. You can often fumble around and find what you want. I think for some, it can become a crutch. Why do I need to learn the why when I can eventually just guess my way through the how. Personally, I think part of the reason for this transition back to the command-line has to do with Microsoft raising the bar for network administration. If Microsoft continues down this path, it's going to force us I.T. professionals to have a better understanding of the products we're working with. And while I find the command-line approach annoying at times, I'm glad it will separate the men from the boys so to speak.
So my advice is to start the process of learning about Powershell, you don't need to be a master (I know I'm not), but it's time to get comfortable with idea of the command-line again and start getting the basics down.
So while some my criticise Microsoft for returning to what some may feel is a dated approach to I.T. administration, I applaud them for raising the bar, and embracing a group of network administrators who prefer things through the good ol' command prompt.
