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

Placing NLB nodes into maintenance


One of the great benefits of NLB is the ability to remove one or more hosts from the cluster without affecting the overall service. This is often done when installing patches or upgrading code on a single server at a time. Removing hosts may result in degraded performance, and therefore, should only be done during a maintenance window, where performance is not an issue, but the overall service will remain online.

Getting ready

This recipe assumes you have a two-node cluster (Web1 and Web2) and Web2 is being taken offline to perform maintenance. The maintenance may require multiple reboots, so we will need to ensure the node remains offline until all work is finished.

How to do it...

Carry out the following steps to place NLB nodes into maintenance:

  1. Safely shutdown and suspend the NLB node on Web2:

    $myCluster = Get-NlbCluster web1
    $myNode = $myCluster | Get-NlbClusterNode -NodeName web2
    $myNode | Stop-NlbClusterNode -Drain
    $myNode | Suspend-NlbClusterNode
    $myNode...