Windows Server Automation with PowerShell Cookbook - Fourth Edition

By : Thomas Lee

Windows Server Automation with PowerShell Cookbook - Fourth Edition

By: Thomas Lee

Overview of this book

With a foreword from PowerShell creator Jeffrey Snover, this heavily updated edition is designed to help you learn how to use PowerShell 7.1 effectively and manage the core roles, features, and services of Windows Server in an enterprise setting. All scripts are compatible with both Window Server 2022 and 2019. This latest edition equips you with over 100 recipes you'll need in day-to-day work, covering a wide range of fundamental and more advanced use cases. We look at how to install and configure PowerShell 7.1, along with useful new features and optimizations, and how the PowerShell compatibility solution bridges the gap to older versions of PowerShell. Topics include using PowerShell to manage networking and DHCP in Windows Server, objects in Active Directory, Hyper-V, and Azure. Debugging is crucial, so the book shows you how to use some powerful tools to diagnose and resolve issues with Windows Server.

Preface

Who this book is for

What this book covers

To get the most out of this book

Get in touch

Installing and Configuring PowerShell 7

Introduction

Installing PowerShell 7

Using the PowerShell 7 console

Exploring PowerShell 7 installation artifacts

Building PowerShell 7 profile files

Installing VS Code

Installing the Cascadia Code font

Exploring PSReadLine

Free Chapter

Introducing PowerShell 7

Introduction

Exploring new operators

Exploring parallel processing with ForEach-Object

Improvements in ForEach and ForEach-Object

Improvements in Test-Connection

Using Select-String

Exploring the error view and Get-Error

Exploring experimental features

Exploring Compatibility with Windows PowerShell

Introduction

Exploring compatibility with Windows PowerShell

Using the Windows PowerShell compatibility solution

Exploring compatibility solution limitations

Exploring the module deny list

Importing format XML

Leveraging compatibility

Using PowerShell 7 in the Enterprise

Introduction

Installing RSAT tools on Windows Server

Exploring package management

Exploring PowerShellGet and the PS Gallery

Creating a local PowerShell repository

Establishing a script signing environment

Working with shortcuts and the PSShortcut module

Working with archive files

Exploring .NET

Introduction

Exploring .NET assemblies

Examining .NET classes

Leveraging .NET methods

Creating a C# extension

Creating a PowerShell cmdlet

Managing Active Directory

Introduction

Installing an AD forest root domain

Testing an AD installation

Installing a replica domain controller

Installing a child domain

Creating and managing AD users and groups

Managing AD computers

Adding users to AD using a CSV file

Creating Group Policy objects

Reporting on AD replication

Reporting on AD computers

Reporting on AD users

Managing Networking in the Enterprise

Introduction

Configuring IP addressing

Testing network connectivity

Installing DHCP

Configuring DHCP scopes and options

Using DHCP

Implementing DHCP failover and load balancing

Deploying DNS in the Enterprise

Configuring DNS forwarding

Managing DNS zones and resource records

Implementing Enterprise Security

Introduction

Implementing Just Enough Administration (JEA)

Examining Applications and Services Logs

Discovering logon events in the event log

Deploying PowerShell group policies

Using PowerShell Script Block Logging

Configuring AD password policies

Managing Windows Defender Antivirus

Managing Storage

Introduction

Managing physical disks and volumes

Managing filesystems

Exploring providers and the FileSystem provider

Managing Storage Replica

Deploying Storage Spaces

Managing Shared Data

Introduction

Managing NTFS file and folder permissions

Setting up and securing an SMB file server

Creating and securing SMB shares

Accessing SMB shares

Creating an iSCSI target

Using an iSCSI target

Implementing FSRM quotas

Implementing FSRM reporting

Implementing FSRM file screening

Managing Printing

Introduction

Installing and sharing printers

Publishing a printer

Changing the spooler directory

Changing printer drivers

Printing a test page

Managing printer security

Creating a printer pool

Managing Hyper-V

Introduction

Installing Hyper-V inside Windows Server

Creating a Hyper-V VM

Using PowerShell Direct

Using Hyper-V VM groups

Configuring VM hardware

Configuring VM networking

Implementing nested virtualization

Managing VM state

Managing VM and storage movement

Managing VM replication

Managing VM checkpoints

Managing Azure

Introduction

Getting started using Azure with PowerShell

Creating Azure resources

Exploring the Azure storage account

Creating an Azure SMB file share

Creating an Azure website

Creating an Azure Virtual Machine

Troubleshooting with PowerShell

Introduction

Using PowerShell Script Analyzer

Using Best Practices Analyzer

Network troubleshooting

Checking network connectivity using Get-NetView

Exploring PowerShell script debugging

Managing with Windows Management Instrumentation

Introduction

Exploring WMI in Windows

Exploring WMI namespaces

Exploring WMI classes

Obtaining local and remote WMI objects

Using WMI methods

Managing WMI events

Implementing permanent WMI eventing

Other Books You May Enjoy

Index

Customer Reviews

5 star

4 star

3 star

2 star

1 star

Establishing a script signing environment

You can often find that it is essential to know that an application, or a PowerShell script, has not been modified since it was released. You can use Windows Authenticode Digital Signatures for this. Authenticode is a Microsoft code-signing technology that identifies the publisher of Authenticode-signed software. Authenticode also verifies that the software has not been tampered with since it was signed and published.

You can also use Authenticode to digitally sign your script using a PowerShell command. You can then ensure PowerShell only runs digitally signed scripts by setting an execution policy of AllSigned or RemoteSigned.

After you digitally sign your PowerShell script, you can detect whether any changes were made in the script since it was signed. And by using PowerShell's execution policy, you can force PowerShell to test the script to ensure the digital signature is still valid and only run scripts that succeed. You...

Windows Server Automation with PowerShell Cookbook - Fourth Edition

By : Thomas Lee

Windows Server Automation with PowerShell Cookbook - Fourth Edition

By: Thomas Lee

Overview of this book

Related Content you might be interested in

Current Title:

Windows Server Automation with PowerShell Cookbook - Fourth Edition

Windows Server 2016 Automation with PowerShell Cookbook

Powershell Core 6.2 Cookbook

PowerShell 7 Workshop

Establishing a script signing environment