locked
Enable WinRM Failed, not sure why? RRS feed

  • Question

  • Hi,

    In order to allow client center to connect to remote machines we found that we need to have WinRM enabled. So we have created a package called "Enable WinRM" which runs a command line "winrm quickconfig -q". I have targeted a collection to apply this package and when I check the reporting of the package status "Enable WinRM" it says Failed. We have it set to run with administrative rights so I am not sure why it is failing or where to check why? I also tried from the powershell prompt to connect via "enter-pssession - computername ..." and I get a message that:

    enter-pssession : Connecting to remote server ***** failed with the
    following error message : WinRM cannot complete the operation. Verify that the
    specified computer name is valid, that the computer is accessible over the
    network, and that a firewall exception for the WinRM service is enabled and
    allows access from this computer. By default, the WinRM firewall exception for

    Has anyone run into this issue before where WinRM package is failing or where in SCCM I can check to find out why?

    Thank you

    Tuesday, October 7, 2014 2:24 PM

Answers

  • Why not use group olicy or compliance settings to enable WinRM?

    http://www.mnscug.org/blogs/sherry-kissinger/307-compliance-setting-to-enable-winrm-updated

    http://www.grouppolicy.biz/2014/05/enable-winrm-via-group-policy/


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Proposed as answer by Daniel JiSun Thursday, October 9, 2014 3:23 AM
    • Marked as answer by Daniel JiSun Tuesday, October 14, 2014 6:01 AM
    Wednesday, October 8, 2014 4:41 PM

All replies

  • Open a cmd in system context (using psexec -i -s cmd) for testing purposes and run the command manually. See what happens (you might have to leave out the "-q" parameter though)

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, October 7, 2014 3:19 PM
  • Hi, I would like to not do this so that I can test to see if the package eventually works with this machine if I am able to find the root cause?
    Tuesday, October 7, 2014 3:27 PM
  • Hi, I would like to not do this so that I can test to see if the package eventually works with this machine if I am able to find the root cause?

    Why not? This is for testing purposes only and you won't see anything when using ConfigMgr plus the "-q" parameter.

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, October 7, 2014 3:29 PM
  • So you want me to run the "winrm quickconfig -q" command?
    Tuesday, October 7, 2014 3:39 PM
  • Why not use group olicy or compliance settings to enable WinRM?

    http://www.mnscug.org/blogs/sherry-kissinger/307-compliance-setting-to-enable-winrm-updated

    http://www.grouppolicy.biz/2014/05/enable-winrm-via-group-policy/


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Proposed as answer by Daniel JiSun Thursday, October 9, 2014 3:23 AM
    • Marked as answer by Daniel JiSun Tuesday, October 14, 2014 6:01 AM
    Wednesday, October 8, 2014 4:41 PM
  • Hi,

    I think the error means that the package is failed to deploy. In another word, the command haven't run yet.

    Check the error status, you can get the detail information about the error code.

    Like Jason suggested, use GPO would be a good solution.

    Thursday, October 9, 2014 3:27 AM