Tip

Enabling multi-server management in Windows Server 2012

As part of its cloud initiative, Microsoft designed Windows Server 2012 so it can be fully managed either locally or remotely. By allowing the management of remote servers, Microsoft has also opened the door to performing multi-server management.

Enable remote management

Before you can take advantage of multi-server management, you will have to enable remote management on the individual servers. To do so, open the Server Manager and select the Local Server container. Next, click on the Disabled link next to Remote Management. Doing so will cause Windows to display a dialog box that gives you the option of enabling remote management from other computers. Simply select the Enable Remote Management check box (figure 1) and click OK.

    Requires Free Membership to View

Figure 1. To enable remote management on individual servers, open Server Manager, select Local Server container and click on Disabled next to Remote Management.

Using Server Manager

The most effective way to manage multiple servers through Server Manager is to create a server group. A server group is a collection of physical or virtual servers that perform the same tasks and should be managed or monitored together. To create a server group, open Server Manager and click on the Dashboard option, followed by the Create a Server Group option shown (figure 2).

Figure 2. To create a server group, open Server Manager, click on the Dashboard option to come to the Create a Server Group option.

At this point, Windows will display the Create Server Group dialog box. Enter a name for the server group you are creating and then specify the servers that should be included in the group. For example, I created a server group called Hyper-V hosts (figure 3). Click OK when you finish selecting the servers that should be included in the group.

Figure 3. Enter a name for the server group and specify the servers to be included in the group.

When you finish creating the group, it will be listed in the Server Manager console. When you click on the group, Server Manager will provide you with an aggregate view of the servers that make up the group (figure 4). For example, you can see the event logs, services, performance and Best Practices Analyzer results for all of the servers in the group. You can even configure performance alerts across the various servers that make up the group.

Figure 4. If you click on the group, Server Manager will give admins a view of servers in the group.

What about PowerShell?

Microsoft has long stated that Windows PowerShell is the preferred mechanism for managing Windows Server 2012. It should come as no surprise that most of the multi-server management capabilities are only exposed through PowerShell.

There are a number of different techniques that can be used to simultaneously manage multiple computers. The easiest of these techniques involves using the Invoke-Command cmdlet. There are three parts to the Invoke-Command cmdlet. First, there is the Invoke-Command cmdlet itself. Next, you must provide the ComputerName switch, followed by a list of the computers on which you wish to run the command. The last part of the command is the actual command that you want to run against the remote machines.

To see how this technique is useful, imagine that you had a number of Hyper-V servers and you wanted to see the names of the virtual machines residing on each Hyper-V host. Normally, the command you would use to create a list of virtual machines and the host server each is running on is:

Get-VM | FT VMName, ComputerName

Figure 5. The PowerShell command being run against the remote servers is in brackets at the end.

The problem with this command is that it only looks at the virtual machines on the local server. If we wanted to run the command against multiple servers we would need to use the Invoke-Command cmdlet. To show how this works, imaging that we wanted to analyze three servers named Lab1, Lab2 and Lab3. To do so, we would use the following command:

Invoke-Command –ComputerName Lab1, Lab2, Lab3 {Get-VM | FT VMName, ComputerName}

We started out by issuing the Invoke-Command cmdlet. Next, we used the ComputerName switch and provided the names of the servers that we wanted to run the command against. The actual command that is being run against the remote servers is encased in brackets at the end of the command (figure 5).

One important caveat when thinking about using Windows Server 2012 for multi-server management: In most cases the remote hosts must be running Windows Server 2012 in order to be remotely managed.

About the author:
Brien Posey is an eight-time Microsoft MVP with two decades of IT experience. Before becoming a freelance technical writer, Brien worked as a CIO at a national chain of hospitals and health care facilities. He has also served as a network administrator for some of the nation's largest insurance companies and for the Department of Defense at Fort Knox.

This was first published in November 2012

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.