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

Enabling Branch Office Direct Printing


Prior to Windows Server 2012, for clients to print, they would send all print traffic to the print server, which then sent the data to the appropriate printer. In main office environments, or environments with local print servers, this worked well since the print server was readily accessible to the clients and printers via high speed connections.

However, this model caused problems in branch offices, which traditionally utilized slower WAN links to the main office. When printing, the client would often send a print job to the print server at the main office, which would then process and send the job to the printer back at the branch office.

To resolve the bandwidth issues in branch offices, many solutions could be implemented. For example, the WAN links between the offices could be improved. Or a separate print server could be installed in the branch office itself. Alternatively, clients could bypass the print server and print directly to the local printer...