Manage 2008 from 2012 Server Manager

NB. Don’t install this on Exchange or SharePoint servers – see comment from Chris below

One of the biggest improvements to Windows Server 2012 is the (almost) all encompassing Server Manager. From any 2012 server you can now manage any other 2012 server through WinRM – but if you add a 2008 or 2008 R2 server to Server Manager, you will get a manageability warning of “Online – Verify WinRM 3.0 service is installed, running, and required firewall ports are open“.

Online - Verify WinRM 3.0 service is installed, running, and required firewall ports are open

To get this working, there are 3 main steps to perform:

  1. Install Windows Management Framework 3.0
  2. Allow remote server management through WinRM (preferred method is via Group Policy)
  3. Create firewall rules
1. Install Windows Management Framework 3.0

Go and get the appropriate .msu from here: http://www.microsoft.com/en-us/download/details.aspx?id=34595

  • Windows Server 2008 R2 SP1
    • WINDOWS6.1-KB2506143-x64.MSU
  • Windows Server 2008 SP2
    • 64-bit versions: WINDOWS6.0-KB2506146-x64.MSU
    • 32-bit versions: WINDOWS6.0-KB2506146-x86.MSU

As you can see, there are some slight caveats. 2008 R2 requires SP1 while 2008 requires SP2 to be installed.

2. Allow remote server management through WinRM

There are 2 ways you can do this. I would recommend use Group Policy wherever possible, so go to:

Computer Configuration > Policies > Administrative Templates > Windows Components > Windows Remote Management (WinRM) > WinRM Service > Allow remote server management through WinRM

Set it to enabled and if you want it to listen on all addresses, put a * in IPv4 and IPv6 filter boxes.

Alternatively, you can run the command “winrm quickconfig” to enable remote access

3. Create firewall rules

Do this again through Group Policy, allowing port 5985.

 

Updated: 10th January 2013 – Added note about Exchange

This entry was posted in Technology and tagged , , , , . Bookmark the permalink.

5 Responses to Manage 2008 from 2012 Server Manager

  1. guest says:

    Why we can not to install Windows6.0-KB2506146-x64.msu on Vista?
    Technically it the same Windows Server 2008.

  2. Chris Knight says:

    Just don’t do this on a box running Exchange 2010 or SharePoint 2010 – it will essentially kill the PowerShell interfaces on these products as they’re expecting PowerShell 2.0. In fact WMF 3.0 will kill your ability to install Exchange 2010 updates.
    We’re living in an era where Microsoft aren’t really supporting backwards for forwards compatibility for administrative functions – the Hyper-V management console is a perfect example of this. You really need separate management silos for different product versions. The goal of one management tool (PowerShell) just isn’t being realised, as a single version simply cannot be deployed everywhere.

Leave a Reply

Your email address will not be published. Required fields are marked *