Greetings once again, Server Manager and Windows Server 2012 fans. Server Manager test engineer Imran Farooqui has written a great post about how to add servers that are running older versions of Windows Server to the new Server Manager in Windows Server 2012. Here's what Imran has to say:
The multi-server-managing Server Manager that ships in Windows Server 2012 (and in its corresponding Remote Server Administration Tools for Windows 8 package) can be used to manage remote, downlevel servers that are running the following operating systems:
To manage these servers from Server Manager in Windows Server 2012, you need to install Windows Management Framework 3.0 (WMF 3.0) and its prerequisites on the managed servers (remote servers that are running the downlevel operating systems). No configuration is required on the client (the computer on which you’re running Server Manager).
Suppose you want to manage two downlevel servers in Server Manager, and these servers do not have WMF 3.0 and its prerequisites. On the first server, the installed operating system is Windows Server 2008 R2 SP1, while on the second server, the installed operating system is Windows Server 2008 SP2. Both servers are in the same domain as the client (the computer on which you’re running Server Manager).
The following table is a step-by-step guideline to ensure that downlevel servers are manageable from Server Manager. I will discuss both installation options of downlevel servers, full server and Server Core.
Operating System-Specific Details
I added my existing WS08 R2 & WS08 SP2 servers to Server Manager and received a manageability status alert.
The manageability status in Server Manager: "Online – Verify WinRM 3.0 service is installed, running, and required firewall ports are open"
The manageability status in Server Manager: "Target server not accessible"
When you added the downlevel servers, Server Manager attempted to connect to the Windows Remote Management (WinRM) port (if that fails, then the DCOM port) of the target server. If either the WinRM or DCOM connection is successful (depending on firewall settings, and whether WinRM is installed), Server Manager checks whether WMF 3.0 is installed on the target server. On the Windows Server 2008 R2 SP1 server, the WinRM connection attempt failed because either the WinRM service was not running, or WinRM inbound firewall rules were not enabled. The DCOM connection was successful, and Server Manager determined that WMF 3.0 is not installed on that server. So Server Manager displayed the manageability status of that server as “Online – Verify WinRM 3.0 service is installed, running, and required firewall ports are open.”
On the Windows Server 2008 SP2 server, the connection attempt to both WinRM and DCOM ports failed (due to firewall restrictions, or no earlier WinRM version was installed), so Server Manager was unable to connect and retrieve data from the target server, and displayed manageability status as “Target server not accessible.”
Ensure the most current service pack for each operating system is installed.
WS08 R2 Service Pack 1 (or newer)
WS08 Service Pack 2 (or newer)
To get the major version of an installed service pack, open Command Prompt on the downlevel server, and run the following command: wmic OS Get ServicePackMajorVersion
Ensure .NET Framework 4 (or newer) is installed.
For servers that are running the full installation option of Windows Server 2008 R2 SP1, see Microsoft .NET Framework 4 (Standalone Installer).
For Server Core, use Microsoft .NET Framework 4 (Standalone Installer) for Server Core.
For servers that are running the full installation option of Windows Server 2008 SP2, see Microsoft .NET Framework 4 (Standalone Installer).
For Server Core, use Microsoft .NET Framework 4 (Standalone Installer) for Server Core.
You can use Knowledge base article 318785 to find out which version of .NET Framework is currently installed.
Install Windows Management Framework 2.0.
Install WMF 3.0 on downlevel servers.
Before this step, you’ll need to complete the last three prerequisite steps; they must be done in order. If you try to run the WMF 3.0 installer without performing the first three steps, the installation fails with an error message similar to the following:
Install the performance update associated with Knowledge Base article 2682011 on downlevel servers.
To get performance counter data in the Server Manager console for servers running previous versions of Windows Server, you need to apply this update.
After installing all the prerequisites on a downlevel server, make sure that the WinRM service is running, and that its inbound firewall rules are enabled on each server.
This can be easily done by using command winrm qc in a command prompt window (which was run as Administrator on the downlevel server). If the WinRM service is not running on the downlevel server, or if the incoming connection attempts to WinRM service are denied by the firewall, when you add the downlevel server (with prerequisites) to the Server Manager server pool, the connection attempt fails as described in step 1 in this table.
Enable Windows PowerShell remote management on each server.
To support Best Practices Analyzer (BPA) operations, Windows PowerShell remoting should also be enabled on the downlevel server. This can be done by running the command Enable-PSremoting -Force in a Windows PowerShell window (that was opened with administrative rights on the downlevel server). For more information about how to enable Windows PowerShell remote management on downlevel servers, see Configure Remote Management in Server Manager, or download the Server Manager Quick Reference Guide.
WMF 3.0 can also be installed on the Server Core installation option of Windows Server 2008 R2 SP1. But it cannot be installed on the Server Core installation option of Windows Server 2008 SP2. Downlevel servers that are running the Server Core installation option of Windows Server 2008 R2 SP1 can be managed remotely from the new Server Manager. The installation process of Windows Management Framework 3.0 on Windows Server 2008 R2 SP1 Server Core is exactly the same as that for full server (already described above). However, before going through the aforementioned prerequisites, you must install or enable certain features in Server Core by using Deployment Image Servicing and Management (DISM) commands. The command names for the features are as follows:
You can enable these features in Server Core by running the following command. Remember, DISM is case-sensitive:
Dism /online /enable-feature: <Feature Name>
After these features are installed on Windows Server 2008 R2 SP1 Server Core, the installation process of Windows Management Framework 3.0 is same as that for full server (already described above).
For the Server Core installation option of Windows Server 2008 R2 SP1, the system administrator can choose to uninstall Windows PowerShell, if it has been installed. If that’s the case, we get a manageability status for the Server Core server (without Windows PowerShell) as follows:
After you have the prerequisite packages installed on your downlevel servers, if you haven’t already done so, you’re ready to add them to the pool of servers that you manage in the new Server Manager console. You can do this by clicking Add Servers on the Manage menu of the new console. For more information about how to add your servers, now that they’re prepped for management with Server Manager, see Add Servers to Server Manager.
Thanks to Imran Farooqui for this detailed step-by-step guide to preparing your downlevel servers for Server Manager. If you're still having trouble adding and managing older server operating systems by using Server Manager in Windows Server 2012, try looking at the Server Manager Troubleshooting Guide, or posting about your difficulties on the Server Manager forum.
More documentation for Server Manager starts right here: Manage Multiple, Remote Servers with Server Manager.
For people having troubles on enabling the features on windows server core this is the complete command:
Dism.exe /Online /Enable-Feature /FeatureName:NetFx2-ServerCore /FeatureName:MicrosoftWindowsPowerShell /FeatureName:NetFx2-ServerCore-WOW64 /FeatureName:MicrosoftWindowsPowerShell-WOW64
Good stuff for the upcoming 70-417 certification, thanks Gaby and Imran :)
I have followed all the steps listed and I still get the error for 2008 R2 Sp1. Please Help!
i have problem with the Server,Im not able to unlock the password how do i retrive it.
I have also followed all the steps listed above and I am getting same error which Wesley Hader is getting for 2008 R2 Sp1.
Is it possible to manage a server running Microsoft server 2003?
Of course, the question I am trying to find the answer to, has no comments... "Is it possible to manage a server running Microsoft server 2003?"
This was asked by Glenn on 11/8/13, almost a month ago.
I realize you can't fully manage a 2003 server but it would be nice to suppress the refresh error and still have the limited management functionality. Anyone know how to do this?
@Glenn, @Brian F
Same issue here. Would love to know if this is possible on a 2003 server. Even if it is only to suppress the "Refresh Failed" errors.
This works perfectly for me managing a 2008 R2 system from 2012. Thanks so much.
When running 2012 Server, will you be able to manage systems that has windows 7, VISTA & etc?
email me your answer email@example.com
En el administrador de servidor me aparece en linea: errores al recuperar datos o error en la actualizacion y en los paneles me marca en rojo y no puedo acceder a roles y caracteristicacas como solucionno esto? firstname.lastname@example.org
How Server Manager embodies the Microsoft Design Principlesthank you