Microsoft introduced a number of new features in Windows Server 2016, from container support to the Nano Server...
deployment option. But there's no need to cook up a script from scratch to implement these innovations when there are prepared PowerShell recipes that do the job.
Windows Server 2016 admins can automate jobs and reduce their workload if they master newer cmdlets. For IT shops that want to avoid manual intervention to arrange and manage features in the latest server OS, there are more than 100 PowerShell recipes in Windows Server 2016 Automation with PowerShell Cookbook: Second Edition by Thomas Lee that can help.
Lee provides scripts to ease the mundane processes that can trip up admins who need to be available when trouble strikes. Microsoft switched the Windows Server patching to a cumulative model in 2016, which made the monthly releases more frustrating to handle for some. Lee has a few scripts to make the process less painful. For admins who want an easier way to work with the Desired State Configuration management tool to keep certain systems tamper-proof, Lee walks through the concepts and provides PowerShell recipes to set up the deployment.
In this excerpt taken from the book's first chapter, Lee describes PackageManagement, a PowerShell module that helps admins and developers install and manage applications from the command line:
PowerShellGet is a powerful resource for PowerShell, built on top of the core PackageManagement capabilities of PowerShell 5. It is one of many PackageManagement providers available. ...
PackageManagement is a unified interface for software package management systems, a tool to manage package managers. You use the PackageManagement cmdlets to perform software discovery, installation, and inventory (SDII) tasks. PackageManagement involves working with package providers, package sources, and the software packages themselves.
Within the PackageManagement architecture, PackageManagement providers represent the various software installers that provide a means to distribute software via a standard plug-in model using the PackageManagement APIs. Each PackageManagement provider manages one or more package sources or software repositories. Providers may be publicly available or can be created within an organization to enable developers and system administrators to publish or install propriety or curated software packages.
Editor's note: This excerpt is from Windows Server 2016 Automation with PowerShell Cookbook: Second Edition, authored by Thomas Lee, published by Packt Publishing, 2017. For updates to scripts used in the book, check the author's PowerShell Cookbook GitHub repository.
PowerShell editor debate: VS Code or ISE?
Get-EventLog cmdlet trims troubleshooting efforts
PowerShell Gallery is one-stop shopping for scripts