Hello everyone
I've just updated my workstation to Windows 8 Pro, yea! - sigh, and now I'm going through trying to get all my management tools working properly and want to use the new Server Manager tools. So I've dutifully installed the windows 8 RSAT tools and begun to add in my servers. However most of my servers are 2003, 2008, 2008 R2 with only 1 solitary 2012 and I'm now suffering the above error on all my 2008 servers. Having done some 2012 training I was expecting this and jumped in to install .net 4, WMF 3.0 as requested. I've not installed the performance counter hot fix yet but I don't believe that has any bearing on this issue (correct me if I'm wrong).
So having followed the advice in the links below and verified that all the relevant services are running I still get the WinRM error under Server Manager against these 2008 servers. I get this whether I use the Server Manager on Windows 8 or Server 2012 and I'm at a loss to fix it.
To confirm what I've done
1. Windows 2008 R2 SP 1 - Domain Controller
2. Installed .Net 4 using the full standalone package - dotNetFx40_Full_x86_x64 (49,268KB size - file version 4.0.30319.1)
3. Installed WMF 3.0 using - Windows6.1-KB2506143-x64.msu (16,171KB size)
4. Ran the Command WinRM QuickConfig - which set up WinRM and applied the appropriate firewall rule - confirmed as being there. The result below is from running the command WinRM id which as you can see indicates that version 3 is in use.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>WinRM id
IdentifyResponse
ProtocolVersion = http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd
ProductVendor = Microsoft Corporation
ProductVersion = OS: 6.1.7601 SP: 1.0 Stack: 3.0
SecurityProfiles
SecurityProfileName = http://schemas.dmtf.org/wbem/wsman/1/wsman/secprof
ile/http/spnego-kerberos
C:\Windows\system32>
5. Restarted the DC just to make sure (I've actually done this several times now - no change in the results)
6. Disabled the firewalls on the clients and servers
6. Refreshed and Restarted both the Windows 8 workstation and the 2012 Server.
I have this issue on multiple servers that I've done the above process through so it's not an isolated incident but I'm at a loss to know what I've got wrong. From all the searching I've done on the net it would be a number of people have experienced the issue but the above steps resolved it; I appear to be the exception. Does anyone have any thoughts or advice as to how I can resolve the issue as I would like to benefit from the new Server Manager without having to update all my servers to 2012 :).
Blessings
Jez
http://blogs.technet.com/b/servermanager/archive/2012/09/10/managing-downlevel-windows-based-servers-from-server-manager-in-windows-server-2012.aspx
http://social.technet.microsoft.com/wiki/contents/articles/13444.windows-server-2012-server-manager-troubleshooting-guide-part-ii-troubleshoot-manageability-status-errors-in-server-manager.aspx