Forum Discussion

Jeff Woolslayer's avatar
Jeff Woolslayer
Icon for Microsoft rankMicrosoft
Sep 20, 2018

Windows Admin Center 1809 Generally Available!

This is our first GA refresh since Windows Admin Center version 1804.25, and it's packed with new features.   Check out the official announcement blog post for more information and download or up...
Artur Schneider's avatar
Artur Schneider
Copper Contributor
Sep 26, 2018

Version:1.0 StartHTML:000000266 EndHTML:000002633 StartFragment:000002016 EndFragment:000002601 StartSelection:000002016 EndSelection:000002597 SourceURL:https://techcommunity.microsoft.com/t5/forums/replypage/board-id/WindowsServerManagement/message-id/134

Thank you for replying. I tried to apply suggested changes. WAC v.1809 Win Server 2016. Initially after accessing site I was indeed getting error message websocket/powershell could not connect. I checked features on Server 2016 and added WebSocket feature. Now I am not able to connect to server even locally getting connection refused message. As for Ajax error I checked the service and it was running.

  • Artur Schneider's avatar
    Artur Schneider
    Copper Contributor
    Oct 01, 2018

    Hi again Jeff Woolslayer

     

    A strange new development occured with v.1809 installation. Although I can access gateway locally I get error 500 trying to access it from anywhere else. That doesn't happen with other servers that have v.1808 installed. (The setup is: Wn Server 2016, valid certificate (not self signed). I did the most common steps like clearing cache on client machine, refreshing dns etc still the error remains. As I said I know the service is running cause I can access gateway locally. Any ideas?

    Thank You

    • Jeff Woolslayer's avatar
      Jeff Woolslayer
      Icon for Microsoft rankMicrosoft
      Oct 02, 2018

      We are tracking a known issue that can cause the firewall rule to be deleted, which would causes this.

       

      To check of the firewall rule exists -

      Get-NetFirewallRule -DisplayName "SmeInboundOpenException"

      If the rule is missing, use this to recreate it replacing <port> with the port configured for Windows Admin Center (default 443.) -

      New-NetFirewallRule -DisplayName "SmeInboundOpenException" -Description "Windows Admin Center inbound port exception" -LocalPort <port> -RemoteAddress Any -Protocol TCP

       

       

Resources