Managing Windows Server 2016 With PowerShell Cookbook
This repository contains an updated and revised library of scripts to accompany Thomas Lee's Managing Windows Server 2016 with PowerShell Cookbook. See Amazon for more details of the book itself.
The book has 13 chapters and each chapter has a number of recipes. Each recipe is planned to be included in this repository. Read the book for more details on pre-requisites for each chapter.
The purpose of these scripts is two fold: First, these scripts are a companion for the book. Feel free to leverage the scripts - this repo makes it easier for you to avoid having to do a lot of retyping. Also, the scripts demonstrate techniques you can use and approaches to follow when you develop scripts. At the same time, there are some less than great practices which are employed to simplify the script. For example, storing things in the root folder of a server is probably not a great idea, but it's simpler than using a huge long path' If you use these scripts, please customise them for our own use.
- Chapter 1 - What's New in PowerShell and Windows Server 2016
- Chapter 2 - Implementing Nano Server
- Chapter 3 - Managing Windows Update
- Chapter 4 - Managing Printers
- Chapter 5 - Managing Windows Server Backup
- Chapter 6 - Managing Performance
- Chapter 7 - Troubleshooting Windows
- Chapter 8 - Managing Windows Networking
- Chapter 9 - Managing Network Shares
- Chapter 10 - Managing Internet Information Server
- Chapter 11 - Managing Hyper-V
- Chapter 12 - Managing Azure
- Chapter 13 - Using Desired State Configuration
Each chapter has a separate folder in this repository, and inside each chapter. Additionally, there is a Readme.MD file that describes the recipes in the chapter along with the PowerShell scripts making up each recipe.
All recipes are 'as is' - if they work, that is great. But if not, oh well. Any damage you do by running these scripts is on you. If you do find issues with any script, please file an issue at GitHub.
Many of these scripts vary from what is published in the book. There are a couple of reasons for this. In the book, many of the scripts used the back tick character to create multi-line commands. Turns out that didn't work very well - they are hard to read. The line width in the book for scripts meant that, in publication, some scripts broke across lines. With that in mind, I've tried to fix these where I have found issues. Additionally, the scripts have been reformatted to fit inside a 72-character line width. To fit within that limit, I've made liberal use of hash tables and splatting.
Any comments: email Thomas Lee at DoctorDNS@Gmail.Com