Find me in different places
« Configuring Exchange 2013 with Powershell- Part 1: Networking | Main | Designing for Exchange 2013 »

Why Use Powershell?

As I was working away the other day on my very long Exchange 2013 configuration Powershell script I was asked why I was spending so much time working on the script that I would only use one time, and that it would be 'faster' if I just did everything manually. This really started me thinking, "Why am I spending so much time on this script?" It came to me later in the day while I was trying to diagnose an issue in another system, that if that system was configured in PowerShell I could go back and see the steps that were taken and that would make finding the problem easier.
Another time last year I started getting complaints of problems with OWA in the 2010 deployment, I knew the problem had to due with the virtual directory somehow. But to find which server had the problem I had to stop IIS on each CAS and check until I figured out which one of the three was not working, the issue had to do with a step that was missed when it was first deployed, if it was configured using PowerShell all of the servers would have been configured exactly the same. 

This brings me to the current project that I am working on, I understand that I probably spent more time writing it then I would have saved if I had done everything manually. But if I ever leave the organization anyone can go back and see exactly how Exchange was deployed, and mostly it was a challenge I gave myself. I wanted to see if I could completly setup Exchange without needing to do anything manually; so far I am at 520 lines and I haven't found a single step that I couldn't find a work around for.

I think Powershell is a great tool that Microsoft has built, I have been really impressed with all of the changes they made in Powershell V3, it is a huge leap forward.

Last night I was watching Jeffrey Snover give the keynote at the NIC conference, I found what he said really interesting, he talked about how the industry is changing and how to be ahead of the curve. PowerShell is so powerful and how it has changed the way people do their jobs, it has changed my job. I really enjoyed his thought about how to stay relevant you have to constantly re-invent yourself.  You can watch it here. Thanks to everyone who posted the link on Twitter. If you want to learn more about PowerShell I recommend watching this, I have only watched half so far, but it is really good, there are a ton of things I didn't know it could do. Everyday I find a new awesome feature.

Have a favorite PowerShell feature or cmdlet? Post it in the comments or just tweet it with the hashtag #PowerShell

PrintView Printer Friendly Version

EmailEmail Article to Friend

Reader Comments (1)

Starting to look at "Workflows" in PowerShell v3.0, Looks great!

February 14, 2013 | Unregistered Commenterdvsit

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>