Server Manager in Windows server 2012 lets you manage remote servers using Windows Remote Management (WinRM). However, for managing down-level servers like Windows server 2008 and Windows server 2008 R2 there are a few prerequisites need to be met.
1. Service Pack Prerequisite
- SP1 required on Windows Server 2008 R2 and SP2 on Windows Server 2008.
2. Microsoft .Net Framework 4.0
3. Windows Management Framework (WMF) 3.0
- Target system needs to have WinRM 3.0. It is included in Windows Management Framework 3.0 and can be download from Microsoft Site.
4. Services status
- Windows Remote Management (WS-Management) service – Started and set to Automatic
- Windows Management Instrumentation service – Started and set to Automatic
- DCOM Process Launcher service – Started and set to Automatic
5. WINRM Port or DCOM Port connectivity
- Make exception in Windows firewall to allow Winrm or Dcom port.
- Default port for WinRM over HTTP is 5985 and over HTTPS is 5986.
6. Microsoft Patch for the down-level (target) server
- Windows Server 2012 list the target servers with status: “Online – Verify WinRM 3.0 service is installed, running, and required firewall ports are open”
7. Allow remote server management through WinRM
- Method 1: Group Policy
Computer Configuration > Policies > Administrative Templates > Windows Components > Windows Remote Management (WinRM) > WinRM Service > Allow remote server management through WinRM
Set the policy to Enabled and put * symbol for IPv4 and IPv6 filter.
- Method 2: Command line
On the target server, type the command: Alternatively, you can run the command “winrm quickconfig” to enable remote access
8. Enable Windows PowerShell remote management
- On the target sever, launch Powershell window and type the following comment: Enable-PSremoting –Force
- This command configures the computer to receive Windows PowerShell remote commands that are sent by using the WS-Management technology.