KEMBAR78
PowerShell and the Future of Windows Automation | KEY
How to Script Automate Better,
     Faster, and More Efficiently
Don Jones • Concentrated Technology
The Past

• We had one server. Maybe a
 handful.

• We clicked buttons and
 checkboxes to manage them.

• We were happy, and Windows
 made networking and servers
 easier than ever.
The Now


• We’ve got a lot more servers.
• Next, Next, Finish is taking
 forever.

• We need a better way to manage
 lots of servers.
The Future

• Servers and services are going to
 become even more distributed.

• We won’t be able to lay hands
 on them all, or get access to a
 GUI on every one.

• So we need a better way that’s
 more distributed-friendly.
What is PowerShell?

• It isn’t a scripting language.
• It isn’t a command-line interface.
• It isn’t the Death of the GUI (altogether)
• It’s a way for Microsoft to give two very different
  audiences what they each need, with a single effort.
Windows “8” / PowerShell 3

• Microsoft has been promising:
 Someday, we’ll make everything do-able in
 PowerShell, and build GUIs on top of all that. Then
 you will have a choice of which to use.


• Windows 8 is the delivery on that promise.
Whats’ This Mean for You?

• For close to a decade, we’ve been managing Windows
 the only way we could: Mainly through the GUI.

• Management has put up with this. What choice did
 they have?

• Now they have a choice.
Choice.

• Given the choice, whatever’s more efficient will
 usually become the preference - and what’s rewarded.

• You’re welcome to continue using the GUI. In a very
 small org, it might not matter. It’ll be a career-
 limiting choice in larger orgs where inefficiency won’t
 be tolerated.
Choice.


• You can choose to learn
 PowerShell to become a more
 effective and efficient admin.

• Or you can learn to say, “would
 you like fries with that?”
No More Console.
• Microsoft is on a mission to
 remove the GUI from the
 server.

• You’ll still have a GUI on your
 client... but think of the “cloud”
 implications.

• And PowerShell is natively
 “cloud friendly” for
 administration.

• Stop logging onto your servers.
Change Happens

• We live in an industry that is based on change...
 sometimes disruptive change.

• The business drivers that made an all-GUI server OS
 attractive are no longer as strong...

• ...but the business drivers for better reach and
 efficiency are increasing.
Make a Battle Plan

• Start learning PowerShell.
• Start finding tasks to automate,
 instead of using the GUI.

• Invest the time.
• The worst-case scenario is that
 you learn a valuable new skill.
Here’s the Hurdle
• The GUI has taught us to click buttons to make things
 happen, but we don’t always pay attention to what’s
 going on underneath.

• Command-line administrators are better
 administrators... not because of the CLI, but
 because they know more of the underlying details.

• You’ll become better at troubleshooting, planning,
 architecting, and more, all as a side effect.
Places to Get Started
• Learn Windows PowerShell in a Month of Lunches (visit
 MoreLunches.com)

• Windows PowerShell Scripting and Toolmaking
 (also MoreLunches.com)

• PowerShellCommunity.org
• ShellHub.org
 (links to my blog and other resources)

• Microsoft and many others (InterfaceTT.com) offer
 classes - look for a great instructor.
And Let the Shell Teach You


• Let’s see a quick demo of how PowerShell itself can
  help you learn to use PowerShell...

• If you’re willing to...
  Read the Friendly Manual Help File
Time for Q&A


• Contact me via ITPro.ConcentratedTech.com
• Follow me on Twitter @concentratedDon
• Hit me on LinkedIn.com/in/ConcentratedDon

PowerShell and the Future of Windows Automation

  • 1.
    How to ScriptAutomate Better, Faster, and More Efficiently Don Jones • Concentrated Technology
  • 2.
    The Past • Wehad one server. Maybe a handful. • We clicked buttons and checkboxes to manage them. • We were happy, and Windows made networking and servers easier than ever.
  • 3.
    The Now • We’vegot a lot more servers. • Next, Next, Finish is taking forever. • We need a better way to manage lots of servers.
  • 4.
    The Future • Serversand services are going to become even more distributed. • We won’t be able to lay hands on them all, or get access to a GUI on every one. • So we need a better way that’s more distributed-friendly.
  • 6.
    What is PowerShell? •It isn’t a scripting language. • It isn’t a command-line interface. • It isn’t the Death of the GUI (altogether) • It’s a way for Microsoft to give two very different audiences what they each need, with a single effort.
  • 12.
    Windows “8” /PowerShell 3 • Microsoft has been promising: Someday, we’ll make everything do-able in PowerShell, and build GUIs on top of all that. Then you will have a choice of which to use. • Windows 8 is the delivery on that promise.
  • 13.
    Whats’ This Meanfor You? • For close to a decade, we’ve been managing Windows the only way we could: Mainly through the GUI. • Management has put up with this. What choice did they have? • Now they have a choice.
  • 15.
    Choice. • Given thechoice, whatever’s more efficient will usually become the preference - and what’s rewarded. • You’re welcome to continue using the GUI. In a very small org, it might not matter. It’ll be a career- limiting choice in larger orgs where inefficiency won’t be tolerated.
  • 16.
    Choice. • You canchoose to learn PowerShell to become a more effective and efficient admin. • Or you can learn to say, “would you like fries with that?”
  • 17.
    No More Console. •Microsoft is on a mission to remove the GUI from the server. • You’ll still have a GUI on your client... but think of the “cloud” implications. • And PowerShell is natively “cloud friendly” for administration. • Stop logging onto your servers.
  • 19.
    Change Happens • Welive in an industry that is based on change... sometimes disruptive change. • The business drivers that made an all-GUI server OS attractive are no longer as strong... • ...but the business drivers for better reach and efficiency are increasing.
  • 21.
    Make a BattlePlan • Start learning PowerShell. • Start finding tasks to automate, instead of using the GUI. • Invest the time. • The worst-case scenario is that you learn a valuable new skill.
  • 22.
    Here’s the Hurdle •The GUI has taught us to click buttons to make things happen, but we don’t always pay attention to what’s going on underneath. • Command-line administrators are better administrators... not because of the CLI, but because they know more of the underlying details. • You’ll become better at troubleshooting, planning, architecting, and more, all as a side effect.
  • 23.
    Places to GetStarted • Learn Windows PowerShell in a Month of Lunches (visit MoreLunches.com) • Windows PowerShell Scripting and Toolmaking (also MoreLunches.com) • PowerShellCommunity.org • ShellHub.org (links to my blog and other resources) • Microsoft and many others (InterfaceTT.com) offer classes - look for a great instructor.
  • 25.
    And Let theShell Teach You • Let’s see a quick demo of how PowerShell itself can help you learn to use PowerShell... • If you’re willing to... Read the Friendly Manual Help File
  • 26.
    Time for Q&A •Contact me via ITPro.ConcentratedTech.com • Follow me on Twitter @concentratedDon • Hit me on LinkedIn.com/in/ConcentratedDon