Add Servers to Server Manager

Artigo
08/31/2016

Applies To: Windows Server 2012, Windows Server 2012 R2

In Windows Server® 2012 R2 Windows Server® 2012, you can manage multiple remote servers by using a single Server Manager console. Servers that you want to manage by using Server Manager can be running Windows Server® 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, or Windows Server 2003. Note that you cannot manage a newer release of Windows Server with an older release of Server Manager.

This topic describes how to add servers to the Server Manager server pool.

Note

In our tests, Server Manager in Windows Server 2012 R2 and Windows Server 2012 can be used to manage up to 100 servers that are configured with a typical workload. The number of servers that you can manage by using a single Server Manager console can vary depending on the amount of data that you request from managed servers, and hardware and network resources available to the computer running Server Manager. As the amount of data you want to display approaches that computer’s resource capacity, you can experience slow responses from Server Manager, and delays in the completion of refreshes. To help increase the number of servers that you can manage by using Server Manager, we recommend limiting the event data that Server Manager gets from your managed servers, by using settings in the Configure Event Data dialog box. Configure Event Data can be opened from the Tasks menu in the Events tile. If you need to manage an enterprise-level number of servers in your organization, we recommend evaluating products in the Microsoft® System Center suite. Server Manager can receive only online or offline status from servers that are running Windows Server 2003. Although you can use Server Manager to perform management tasks on servers that are running Windows Server 2008 R2 or Windows Server 2008, you cannot add roles and features to servers that are running Windows Server 2008 R2, Windows Server 2008 or Windows Server 2003. Server Manager cannot be used to manage a newer release of the Windows Server operating system. Server Manager running on Windows Server 2012 or Windows 8 cannot be used to manage servers that are running Windows Server 2012 R2.

This topic contains the following sections.

Provide credentials with the Manage As command

As you add remote servers to Server Manager, some of the servers that you add might require different user account credentials to access or manage them. To specify credentials for a managed server that are different from those you use to log on to the computer on which you are running Server Manager, use the Manage As command after you add a server to Server Manager, which is accessible by right-clicking the entry for a managed server in the Servers tile of a role or group home page. Clicking Manage As opens the Windows Security dialog box, in which you can provide a user name that has access rights on the managed server, in one of the following formats.

User name
User name@example.domain.com
Domain\User name

The Windows Security dialog box that is opened by the Manage As command cannot accept smart card credentials; providing smart card credentials through Server Manager is not supported. Credentials that you provide for a managed server by using the Manage As command are cached, and persist as long as you are managing the server by using the same computer on which you are currently running Server Manager, or as long as you do not overwrite them by specifying blank or different credentials for the same server. If you export your Server Manager settings to other computers, or configure your domain profile to be roaming to allow Server Manager settings to be used on other computers, Manage As credentials for servers in your server pool are not stored in the roaming profile. Server Manager users must add them on each computer from which they want to manage.

After you add servers to manage by following procedures in this topic, but before you use the Manage As command to specify alternate credentials that might be required to manage a server that you have added, the following manageability status errors can be displayed for the server:

Kerberos target resolution error
Kerberos authentication error
Online - Access denied

Note

Roles and features that do not support the Manage As command include Remote Desktop Services (RDS) and IP Address Management (IPAM) Server. If you cannot manage the remote RDS or IPAM server by using the same credentials you are using on the computer on which you are running Server Manager, try adding the account you typically use to manage these remote servers to the Administrators group on the computer that is running Server Manager. Then, log on to the computer that is running Server Manager with the account you use to manage the remote server that is running RDS or IPAM.

Add servers to manage

You can add servers to Server Manager to manage by using any of three methods in the Add Servers dialog box.

Active Directory® Domain Services Add servers to manage that Active Directory finds in the same domain as the local computer.
Domain Name System (DNS) entry Search for servers to manage by computer name or IP address.
Import multiple servers Specify multiple servers to import in a file that contains servers listed by computer name or IP address.

To add servers to the server pool

If Server Manager is already open, go on to the next step. If Server Manager is not already open, open it by doing one of the following.
- On the Windows desktop, start Server Manager by clicking Server Manager in the Windows taskbar.
- On the Windows Start screen, click the Server Manager tile.
On the Manage menu, click Add Servers.
Do one of the following.
- On the Active Directory tab, select servers that are in the current domain. Press Ctrl while selecting to select multiple servers. Click the right-arrow button to move selected servers to the Selected list.
- On the DNS tab, type the first few characters of a computer name or IP address, and then press Enter or click Search. Select servers that you want to add, and then click the right-arrow button.
- On the Import tab, browse for a text file that contains the DNS names or IP addresses of computers that you want to add, one name or IP address per line.
When you are finished adding servers, click OK.

Add and manage servers in workgroups

Although adding servers that are in workgroups to Server Manager might be successful, after they are added, the Manageability column of the Servers tile—on a role or group page that includes a workgroup server—can display Credentials not valid errors that occur while trying to connect to or collect data from the remote, workgroup server.

These or similar errors can occur in the following conditions.

The managed server is in the same workgroup as the computer that is running Server Manager.
The managed server is in a different workgroup from the computer that is running Server Manager.
One of the computers is in a workgroup, while the other is in a domain.
The computer that is running Server Manager is in a workgroup, and remote, managed servers are on a different subnet.
Both computers are in domains, but there is no trust relationship between the two domains.
Both computers are in domains, but there is only a one-way trust relationship between the two domains.
The server you want to manage has been added by using its IP address.

To add remote workgroup servers to Server Manager

On the computer that is running Server Manager, add the workgroup server name to the TrustedHosts list. This is a requirement of NTLM authentication. To add a computer name to an existing list of trusted hosts, add the Concatenate parameter to the command. For example, to add the Server01 computer to an existing list of trusted hosts, use the following command.
```
Set-Item wsman:\localhost\Client\TrustedHosts Server01 -Concatenate -Force
```
Determine whether the workgroup server that you want to manage is in the same subnet as the computer on which you are running Server Manager.

If the two computers are in the same subnet, or if the workgroup server’s network profile is set to Private in the Network and Sharing Center, go on to the next step.

If they are not in the same subnet, or if the workgroup server’s network profile is not set to Private, on the workgroup server, change the inbound Windows Remote Management (HTTP-In) setting in Windows Firewall to explicitly allow connections from remote computers by adding the computer names on the Computers tab of the setting’s Properties dialog box.

<table>
<colgroup>
<col style="width: 100%" />
</colgroup>
<thead>
<tr class="header">
<th><img src="images/Dn495428.s-e6f6a65cf14f462597b64ac058dbe1d0-system-media-system-caps-security(WS.11).jpeg" /> Security Note</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><p>Running the cmdlet in this step overrides User Account Control (UAC) measures that prevent elevated processes from running on workgroup computers unless the built-in Administrator or the System account is running the processes. The cmdlet lets members of the Administrators group manage the workgroup server without logging on as the built-in Administrator. Allowing additional users to manage the workgroup server can reduce its security; however, this is more secure than providing built-in Administrator account credentials to what might be multiple people who are managing the workgroup server.</p></td>
</tr>
</tbody>
</table>

To override UAC restrictions on running elevated processes on workgroup computers, create a registry entry called **LocalAccountTokenFilterPolicy** on the workgroup server by running the following cmdlet.

    New-ItemProperty -Name LocalAccountTokenFilterPolicy -path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System -propertyType DWord -value 1

On the computer on which you are running Server Manager, open the All Servers page.
If the computer that is running Server Manager and the target workgroup server are in the same workgroup, skip to the last step. If the two computers are not in the same workgroup, right-click the target workgroup server in the Servers tile, and then click Manage as.
Log on to the workgroup server by using the built-in Administrator account for the workgroup server.
Verify that Server Manager is able to connect to and collect data from the workgroup server by refreshing the All Servers page, and then viewing the manageability status for the workgroup server.

To add remote servers when Server Manager is running on a workgroup computer

On the computer that is running Server Manager, add remote servers to the local computer’s TrustedHosts list in a Windows PowerShell session. To add a computer name to an existing list of trusted hosts, add the Concatenate parameter to the command. For example, to add the Server01 computer to an existing list of trusted hosts, use the following command.
```
Set-Item wsman:\localhost\Client\TrustedHosts Server01 -Concatenate -Force
```
Determine whether the server that you want to manage is in the same subnet as the workgroup computer on which you are running Server Manager.

If the two computers are in the same subnet, or if the workgroup computer’s network profile is set to

Private in the Network and Sharing Center, go on to the next step.

If they are not in the same subnet, or if the workgroup computer’s network profile is not set to Private, on the workgroup computer that is running Server Manager, change the inbound Windows Remote Management (HTTP-In) setting in Windows Firewall to explicitly allow connections from remote computers by adding the computer names on the Computers tab of the setting’s Properties dialog box.
On the computer on which you are running Server Manager, open the All Servers page.
Verify that Server Manager is able to connect to and collect data from the remote server by refreshing the All Servers page, and then viewing the manageability status for the remote server. If the Servers tile still displays a manageability error for the remote server, go on to the next step.
Log off of the computer on which you are running Server Manager, and then log on again by using the built-in Administrator account. Repeat the preceding step, to verify that Server Manager is able to connect to and collect data from the remote server.

If you have followed the procedures in this section, and you continue to have problems managing workgroup computers, or managing other computers from workgroup computers, see about_Remote_Troubleshooting on the Microsoft website.

Add and manage servers in clusters

You can use Server Manager to manage servers that are in failover clusters (also called server clusters or MSCS). Servers that are in failover clusters—whether the cluster nodes are physical or virtual—have some unique behaviors and management limitations in Server Manager.

Both physical and virtual servers in clusters are automatically added to Server Manager when one server in the cluster is added to Server Manager. Similarly, when you remove a clustered server from Server Manager, you are prompted to remove other servers in the cluster.
Server Manager does not display data for clustered virtual servers, because the data is dynamic, and is identical to data for the server on which the virtual clustered node is hosted. You can select the server that is hosting the virtual server to view its data.
If you add a server to Server Manager by using the server’s virtual cluster object name, the virtual object name is displayed in Server Manager instead of the physical server name (expected).
You cannot install roles and features on a clustered virtual server.

Partilhar via