Book Image

Windows Server 2012 Automation with PowerShell Cookbook

By : EDRICK GOAD
Book Image

Windows Server 2012 Automation with PowerShell Cookbook

By: EDRICK GOAD

Overview of this book

Automating server tasks allows administrators to repeatedly perform the same, or similar, tasks over and over again. With PowerShell scripts, you can automate server tasks and reduce manual input, allowing you to focus on more important tasks. Windows Server 2012 Automation with PowerShell Cookbook will show several ways for a Windows administrator to automate and streamline his/her job. Learn how to automate server tasks to ease your day-to-day operations, generate performance and configuration reports, and troubleshoot and resolve critical problems. Windows Server 2012 Automation with PowerShell Cookbook will introduce you to the advantages of using Windows Server 2012 and PowerShell. Each recipe is a building block that can easily be combined to provide larger and more useful scripts to automate your systems. The recipes are packed with examples and real world experience to make the job of managing and administrating Windows servers easier. The book begins with automation of common Windows Networking components such as AD, DHCP, DNS, and PKI, managing Hyper-V, and backing up the server environment. By the end of the book you will be able to use PowerShell scripts to automate tasks such as performance monitoring, reporting, analyzing the environment to match best practices, and troubleshooting.
Table of Contents (19 chapters)
Windows Server 2012 Automation with PowerShell Cookbook
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Configuring the Windows update client


The Windows update client on servers and workstations default to downloading updates from Microsoft's public update servers. In a business environment, this is not always desirable due to unpredictable installation schedules and potentially varied patch revisions.

Once the update server is configured, we can configure the Windows update client. At its most simplistic configuration, the client configuration includes the address of the update server and a setting instructing the client to use the update server.

Getting ready

The simplest way to configure the clients is to create one or more group policies that define the address of the local update servers. This group policy can then be deployed to the entire Active Directory (AD) environment, specific sites, or only a subset of computers.

Our group policy will define the following registry setting on our clients:

Path

Name

Value

HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU

UseWUServer...