locked
Revert from WinRM 3.0 to WinRM 2.0 RRS feed

  • Question

  • Hello,

    I am trying to install System Center Virtual Machine Manager 2012 in a Hyper-V 2012 R2 environment, and when I run the analyzer, I get this alert:

    Category: Prerequisite
    Source: hyper-1
    Issue: The above issue was found about Windows Remote Management (WinRM) on the specified server.
    Impact: The specified server cannot be used for VMM server roles such as host/library/PXE server/WSUS server/VMM management server.
    Resolution: On the specified server:
    1. Verify that the WinRM service is present and running by running the command net start winrm at a command prompt using elevated privileges
    2. Run the command winrm id at an elevated command prompt, verify that no error is received, and that Stack=2.0
    3. Run the command winrm qc at an elevated command prompt.

    The verify output indicates that I am running Stack=3.0. My question is, if I uninstall WinRM 3.0 will it automatically revert to WinRM 2.0

    Marz23


    • Edited by marz23 Thursday, October 1, 2015 1:54 PM
    • Moved by BrianEhMVP Thursday, October 1, 2015 3:10 PM
    Thursday, October 1, 2015 1:53 PM

Answers

  • WinRM version is either an add-on to a Server OS (Windows Management Framework) to uplevel a Server or it is built-in.

    You cannot downlevel what is built in.  You can only not uplevel (not upgrade the Windows Management Framework).

    This is detailed here: https://technet.microsoft.com/en-us/library/gg610562.aspx?f=255&MSPPError=-2147217396

    • WinRM 2.0 is included in the Windows Server 2008 R2 operating system. By default, the Windows Remote Management (WS-Management) service is set to start automatically (delayed start).

    • WinRM 3.0 is included in Windows Server 2012 and in Windows Server 2012 R2. By default, the Windows Remote Management (WS-Management) service is set to start automatically.

    2012 R2 includes a new revision of WinRM.  And Hyper-V 2012 R2 includes the new v2 virtualization WMI namespace.

    That said, only SCVMM 2012 R2 knows how to talk to Hyper-V 2012 R2 / Server 2012 R2.

    Which is kind of described here (sort of): https://technet.microsoft.com/en-us/library/gg610649.aspx

    You need SCVMM 2012 R2.

    https://technet.microsoft.com/en-us/library/dn771747.aspx


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.

    • Proposed as answer by Elton_Ji Monday, October 5, 2015 2:34 AM
    • Marked as answer by Elton_Ji Wednesday, October 7, 2015 6:53 AM
    Thursday, October 1, 2015 3:09 PM