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 NLB across multiple servers


One of the easiest methods of making a website highly available is to use a Network Load Balancer (NLB). The NLB role resides on the web servers themselves and provides a virtual IP address that balances traffic between the individual nodes. Clients make requests to the virtual address, and the web servers communicate with each other to determine which will service the request.

This results in a website that is highly available and can sustain individual server failures, but also provides a scale-out capability to grow websites quickly and easily.

This recipe will cover setting up and configuring an NLB cluster in order to provide a redundant website infrastructure.

Getting ready

To configure NLB, we will need a minimum of two servers with three static IP addresses, all connected via a common Ethernet segment. As you can see in the following diagram, I have predetermined my IP addresses of 10.10.10.241 for Web1, 10.10.10.242 for Web2, and 10.10.10.240...