Failed to Read Remoting State

ComputerHabit 781 Reputation points
2020-11-12T22:13:26.313+00:00

All of a sudden just my 2019 servers are having this issue.

39448-screenshot-2020-11-12-161138.png

Help I have no idea why it started.

Windows Server Management
Windows Server Management
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Management: The act or process of organizing, handling, directing or controlling something.
421 questions
0 comments
Accepted answer
  1. ComputerHabit 781 Reputation points
    2020-11-20T16:43:08.367+00:00

    I finally got this resolved. Turns out the firewall rules were corrupted. I deleted the old rules and ran the following command.

    netsh advfirewall firewall add rule name="Windows Remote Management (HTTP-In)" dir=in action=allow service=any enable=yes profile=any localport=5985 protocol=tcp

    From <https://support.logbinder.com/SuperchargerKB/50218/WinRM-says-Unable-to-check-the-status-of-the-firewall>

    The only change I can think of is we moved from 2008R2 forest functional level to 2012R2.

    0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Karlie Weng 14,411 Reputation points Microsoft Vendor
    2020-11-13T08:36:18.23+00:00

    Hello @ComputerHabit

    May this thread helps:
    Remote Management: "Failed to read remoting state" error

    Other article for reference:
    Configure remote Management in Server Manager

    ----------

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Best Regards
    Karlie

  2. ComputerHabit 781 Reputation points
    2020-11-18T10:49:57.197+00:00

    I haven't been able to get back to it. None of the articles have helped. I had SSL setup so I'll have to see what I can do to reverse all the changes. At a loss as to why this happened.

    We did just update the forest functional level to 2012.

    0 comments