Our experience as Sys Admins can be improved if we switch from Server Manager and MMC to Windows Admin Center. Hey, stop. What is Windows Admin Center? Windows Admin Center is web-based solution unveiled by Microsoft on September 2017, but the first stable version is released in January 2019. It helps us to manage a bunch of Windows Server and Windows 10 machines from a single location. Oh, great, where can I find it and how to use it? We are recommending you to download Windows Admin Center from Microsoft’s website.
The process of installation is straightforward, all you need is to run the .exe file and add your Windows servers or client machines. Sometimes the procedure of adding the server or client to Windows Admin Center can get wrong and we gonna need to invest our time in order to solve a problem. One of the problems is a disconnection of runspace that prevent Windows Admin Center to add remote machines. The same error can appear in case we upgrade Windows Admin Center in service mode from a previous mode. The error is known as:
Connection error: Cannot perform the operation because the runspace is not in the Opened state. Current state of the runspace is Disconnected
This problem occurs because there is no firewall rule that will allow Windows Admin Center to access our remote server. In order to simulate problem, we will use Windows 10 Pro and Hyper-V 2019. Windows Admin Center is installed on Windows 10 machines.
Solution: Create Inbound Firewall rule via Powershell
This solution consists of a few steps and all of them are described hierarchically:
- Left click on the Start menu and type Powershell
- Right click on Powershell and click Run as Administrator
- Click OK in order to confirm running Powershell as Administrator
- Type the command below and press Enter
Powershel> New-NetFirewallRule -DisplayName „SmeInbounOpenException“ -Description „Windows Admin Center inbound port exception“ -Localport 6516 -RemoteAddess Any -Protocol TCP
- Open Windows Admin Center and connect to Hyper-V 2019.