Remotely Administering Windows Server Core


If you are like me, you are getting more and more excited about Microsoft Windows Server 2016; especially the core deployment with HyperV. No doubt then, you are already aware that after the quick and easy installation and configuration of the operating system, everyday management tasks require a longer process from the core GUI-less using commands and/or Powershell. And If you are running the HyperV server role, you will need remote management enabled to manage the HyperV remotely as the Microsoft Management Console (MMC) is not supported to run locally on the core deployment.

After the deployment and the initial server configuration try to use remote management of the HyperV, or the Core Server, from a remote full GUI windows OS deployment, and you will be greeted with the Computer Management error illustrated below.


Do not stress; in the next few lines, I will help you solve this issue quickly. Log into the core server, open a PowerShell window, and then run the following PowerShell commands:

  • Enable-NetFireWallRule -DisplayName “Windows Management Instrumentation (DCOM-In)”
  • Enable-NetFireWallRule -DisplayGroup “Remote Event Log Management”
  • Enable-NetFireWallRule -DisplayGroup “Remote Service Management”
  • Enable-NetFireWallRule -DisplayGroup “Remote Volume Management”
  • Enable-NetFireWallRule -DisplayGroup “Remote Scheduled Tasks Management”
  • Enable-NetFireWallRule -DisplayGroup “Windows Firewall Remote Management”

If security is not a concern, you can run the one single command shown below to disable the Core server local Firewall. I prefer using this command, as I am running a core server in a lab.

  • Get-NetFirewallProfile | Set-NetFirewallProfile -enabled false

That is all that you need to do on the Core server.

Your next stop before getting on with the remote management is running the following command on the Management server; yes, the server you are going to use to manage the core server.

  • Enable-NetFirewallRule -DisplayGroup “Remote Volume Management”


Running those commands, we showed you on both the core server and the management server will see you able to easily manage your core server, including the HyperV role, remotely.

I hope this quick post will help you with your day to day remote Windows core server management.

18 thoughts on “Remotely Administering Windows Server Core

    • Hi Loki5100, That’s strange, I use these steps every-time I install a new core server and work just fine. What version of windows server core are you deploying and trying the above steps? Can you somehow provide remote access to the server and I will give it a try?

  1. Hello HalYaman 🙂 I can’t understand how you made it working, i try on a fresh installed windows 2016 core servers. I try everything on the core server, even deactivating the firewall, nothing help 🙁 Yes absolutely if you want to make a try i can gave you the adminstrator password (please edit this post to not make it public):

    • Thanks for sharing, reran the commands in your server and didn’t see any issues, all went ok.
      Also re-checked my steps on my environment again and everything working just fine (so the post will be and stay public 🙂 ), did you run this command on the management server: Enable-NetFirewallRule -DisplayGroup “Remote Volume Management”. Also, the core server is not part of your domain.

  2. thanks HalYaman, but why it’s must be a challenge? i can connect to the server with powershell, remote desktop, even throught server manager, but only “computer management” failed … why computer management need a domain ? I read your link but it’s not helping me 🙁

    • Can you please check with the link I sent you, My post and steps is explaining how to manage your core server on a domain environment. Sorry that my blog post is not helping you :(, but if you can try the MS article and let me know if it helped then maybe will add and modify the post to insert the non-domain core server remote management. Also I will try to run a workgroup server and give it a try

      • OOh don’t be sorry you blog is very helpfull ! thank again for this you are great !! I already tryed the MS article but it’s didn’t help 🙁 I don’t think my problem is connected to a domain because when i install GUI server instead of server core then it’s work …

  3. HalYaman, can you edit my previous post and remove from it the IP and credential of my server ? not very good to leave them public 🙂 thanks again !

    • Done and I suggest to change the IP address and the password. Also it better to disable the admin account and create a diff user with same permissions (copy admin).

  4. Hi LoKi5100, Just did a test with a win core workgroup and all what I needed to added to be able to manage remotely in addition to what I wrote on this blog is the following two commands: Enable-PSRemoting & Enable-WSManCredSSP -Role server

    Hope this will help


    • @HalYaman, you are great thanks again ! I m now reinstalling the server, it’s can take a while but as soon as it’s ready i will make a try !

  5. HalYaman, no it’s still not working 🙁 I can’t connect to the server via “computer management” snap in 🙁 I try to install the Hyper V instead of the core, same i can’t connect to the server, even with Enable-PSRemoting & Enable-WSManCredSSP -Role server 🙁

Leave a Reply