Core mode of Windows Server 2016 TP3 - Remote Management Tip

Microsoft just released technical preview 3 of Windows Server 2016, it's catching up VMware on SDDC. I can see a lot of enhancement in the new version. A stable hypervisor is  prerequisite of SDDC but it's weakness of Microsoft. You have to patch and reboot frequently, some organizations even have regular reboot schedules. Microsoft introduced core mode on Windows Server 2008, it much enhanced on Windows Server 2012 R2. But Windows Server 2012 R2 aims to SBM. I didn't think SBM organizations really need that if you compare operation complexity of core mode with GUI.

[do_widget "Language Switcher" wrap=aside title=false]

Windows Server 2016 aims to enterprise market I guess, I expect it more successful if Microsoft can works out a powerful management tools (VMM 2012 R2 is suck). So it's reasonable to take a look core mode of the new version.

Installation is similar like Windows Server 2008 or 2012. Configuration of remote management is tricky. I was never successful by following Microsoft article. Looks like most of time I cannot fix issue by follow Microsoft articles when I got a problem. Do you?

To make my lab simple, I used following steps to enable remote management feature on Windows Server 2016 TP3.

  1. Install Remote Server Administration Tools for Windows 8 on my laptop.  (Not applicable for Windows Server and Windows 7.)

  2. Run command below on my laptop.
    Set-Item wsman:localhostclienttrustedhosts -value *

  3. Run command on Windows Server 2016 TP3 console. (I got this command from this article.)
    netsh advfirewall set allprofiles state off

  4. Run following command on Windows Server 2016 TP3 console to enable remote management feature.

  5. Add the server on Server Manager on my laptop.

[caption id="attachment_583" align="alignnone" width="300"]Configure remote management feature on Windows Server 2016 TP3 core mode Configure remote management feature on Windows Server 2016 TP3 core mode[/caption]

Popular posts from this blog

Moving to

How to Use Proxy on WSL 2

Connect-NsxtServer shows "Unable to connect to the remote server"