Skip to main content

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

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

When you run Connect-NsxtServer in the PowerCLI, it may show "Unable to connect to the remote server".  Because the error message is a little bit confusing with other login issues. It's not easy to troubleshoot. The actual reason is the NSX-T uses a self-signed certificate, and the PowerCLI cannot accept the certificate automatically. The fix is super easy. You need to set the PowerCLI to ignore the invalid certificate with the following command: Set-PowerCLIConfiguration -Scope User -InvalidCertificateAction:Ignore -Confirm:$false

Setup Terraform and Ansible for Windows provisionon CentOS

Provisioning Windows machines with Terraform is easy. Configuring Windows machines with Ansible is also not complex. However, it's a little bit challenging to combine them. The following steps are some ideas about handling a Windows machine from provisioning to post configuration without modifying the winrm configuration on the guest operating system. Install required repos for yum. yum -y install yum -y install yum -y install yum -y install epel-release yum -y install yum-utils yum-config-manager --add-repo Install  Terraform . sudo yum -y install terraform Install  Ansible . sudo yum -y install ansible Install  Kerberos . yum -y install gcc python-devel krb5-devel krb5-libs krb5-workstation

How to List All Users in Terraform Cloud

Terraform has a rich API. However, the API documentation does not mention how to list all users. We can leverage the organization membership API and the PowerShell command  Invoke-RestMethod  to get a user list. 1. Create an organization token in Terraform Cloud. 2. Create the token variable ( $Token ) in PowerShell. $Token = "abcde" 3. Create the API parameters variable in PowerShell. $params = @{ Uri = "" Authentication = "Bearer" Token = $Token ContentType = "application/vnd.api+json" } Note: You need to replace ZHENGWU with your own organization name. And I used 100 at the end of the URI to retrieve the first 100 users. It can be any number.  4. Retrieve the API return and list the user's email address. $Test = Invoke-RestMethod @params $