It's time to make the move from the PowerShell apprentice to the PowerShell master. In this 2-day demo-heavy seminar we will work together to give you the building blocks that you need to become the PowerShell expert that you have always wanted to be. We will start with a very brief overview of the basics then we will jump right into it. PowerShell is such a powerful tool that you can put in your toolbox. And while we won’t have time to cover everything, we will go over a few of the most important topics that you will need to start using PowerShell in your everyday job.

Part of being a PowerShell master is knowing how to write reusable code and how to share that with friends, coworkers, and the community. While we are together, we will go over best practices on sharing your code with others, including using GIT and unit testing. And we will also go over how best to handle errors in your code. Because yes you will have errors and you need to know how to take care of them.

This will be a PowerPoint light session with plenty of demos and hands-on labs to help you understand and master the topics that we are discussing. We will be using PowerShell 7 in this class and we will see a little bit of its cross-platform awesomeness.

You will learn:

• How to organize your scripts into reusable modules
• How to share them with others
• About error handling and why it's important
• How to manage multiple machines using remoting

Attendee Workstation Requirements:
You must provide your own computer (Windows or Mac) for this hands-on lab workshop with a camera, wired Internet connection, speakers, and a microphone. Your computer should be running windows 10, have PowerShell 7, and VSCode with the PowerShell extension installed. It is also recommended that the you have Windows Terminal installed and a GitHub account is recommended.

Access to a second windows 10 machine with internet access would be helpful for remoting labs but not required.

You should have the ability to run VSCode as an administrator on your computers. The Execution policy on your machine should at least be remote signed.