We just installed our new Windows Server 2012 RC and the first application opened by the OS is…Server Manager. Great ! It’s time to see how does it works. Very quickly you’ve understand this new server manager will be the console to manage easily all your servers, and for the moment you have one 2012 server for many 2008 servers…so let’s go to add them !
On the Dashboard you have a button to add them. You can find your server in your Active Directory, you DNS or you can import them.
Immediately you will have to face to this error meesage : “Online – Verify WinRM 3.0 service is installed, running, and required firewall ports are open”.
The main reason is the server manager in Windows Server 2012 use Windows Management Framework 3.0. This version must be deploy on your windows Server 2008 r2. To do this :
- Install and deploy .Net Framwork 4.0 : get it here
- Install and deploy the WMF 3.0 (you will have to reboot) : get it here
Logon your server 2008 R2 SP1, open a PowerShell as Administrator and type : winrm quickconfig. The system should purpose to create a listener and a firewall rule. Accept the actions
To test the result, go in your Server Manager on the Server 2012, open “all servers”, select the server 2008 R2 SP1 where you’ve deploy WMF 3.0 and do a right click to ask to open a powershell Session in remote.
If it works well you have just to do a refresh and launch a BPA on the server and it will be green and ready to be manage from the new Server Manager
if you have the error : “Online – cannot get performance counter data” you must intall this hotfix KB2682011. You will have to reboot your server.
UPDATE from 03/10/2012 : if you’ve install the Beta version you must update the new one (http://www.microsoft.com/en-us/download/details.aspx?id=34595) or you will have “The WinRM client cannot process the request. Property “StartTimes” with MI type MI_DATETIMEA does not match the expected type from the schema: MI_UINT64A. Specify the correct type and retry the operation.”
UPDATE from 03/10/2012 : and good start point to troubleshoot is this page