In Windows Server 2012, you can use Server Manager to perform management tasks in remote Windows-based servers, without requiring either physical access to servers, or the need to enable Remote Desktop protocol (RDP) connections to each server.
You can use Server Manager to manage remote servers that are running older releases of Windows Server, but to fully manage these older operating systems, the following updates to the older operating systems:
Manage older OS from Windows Server 2012 R2:
- .NET Framework 4.5
- Windows Management Framework 4.0.
- The performance update associated with Knowledge Base article 2682011, which allows Server Manager to collect performance data from Windows Server 2008 and Windows Server 2008 R2. (Note: you don’t need this update on servers that are running Windows Server 2012).
Manage older OS from Windows Server 2012:
- .NET Framework 4
- Windows Management Framework 3.0.
- The performance update associated with Knowledge Base article 2682011.
Remote management is enabled by default. Before administrators can remotely connect to a computers that is running Windows Server 2012 R2 or Windows Server 2012, Server Manager remote management must be enabled on the destination computer if it has been disabled. In the Server Manager console, the remote management status for the local server is displayed in the Properties area of the Local Server page.
To add a server to manage remotely,
- Open Server Manager. (You can verify which servers you are managing by clicking All Servers on the console tree).
- On the Manage menu, click Add Server or on the Console tree click the Dashboard and select “Add other servers to manage” Option.
- On the Add Servers windows, choose a method to add the servers to be managed (Active directory, DNS, import), then select the server you want to manage remotely and click Ok.
- On the console tree, click All Servers to verify the server was added.
- Right click on the remote server, you will see a list of options you can use to manage the remote server.
Windows Remote Management (WinRM) listener settings
Server Manager relies on default WinRM listener settings on the remote servers that you want to manage. Be careful, if the default authentication mechanism or the WinRM listener port number on a remote server has been changed from default settings, Server Manager cannot communicate with the remote server.
The following list shows default WinRM listener settings for managing by using Server Manager.
- The WinRM service is running.
- A WinRM listener is created to accept HTTP requests through port number 5985.
- Port number 5985 is enabled in Windows Firewall settings to allow requests through WinRM.(The default port number is 5985 for WinRM to communicate with a remote computer).
- Both Kerberos and Negotiate authentication types are enabled.