Skip to main content

Remote Manage Workgroup Windows Server 2016 Core

I wrote an article about how to manage Windows Server 2016 TP remotely. Today I had some spare time to re-build my lab environment by the latest release of Windows Server 2016 Core. It's easy to remotely manage a Windows Server in a domain, but a trick for workgroup Windows Server. Following is an improved procedure.

One Windows Server 2016 Core

  1. Run sconfig command on Windows Server 2016 Core.

  2. Go to Configure Remote Management - Enable Remote Management to enable remote management.

  3. Then enable responding to ping in same page.

  4. Enable NetBIOS protocol on the firewall by PowerShell.
    Set-NetFirewallRule -Name FPS-NB_Name-In-UDP -Enabled True
    Set-NetFirewallRule -Name FPS-NB_Name-Out-UDP -Enabled True



One client Windows 10

  1. Install Remote Server Administration Tools on the client Windows 10.

  2. Reboot the client.

  3. Open "Server Manager".

  4. Add the Windows Server 2016 Core machine by IP address.

  5. Go to "All Servers" in "Server Manager".

  6. Right-click the newly added server - "Managed As...".

  7. Enter the administrator credential of the target server. Format is "workgroup/Administrator".  For example, my workgroup is "DC", so the account is "dc/Administrator".


 

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 https://repo.ius.io/ius-release-el7.rpm yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm yum -y install https://packages.endpointdev.com/rhel/7/os/x86_64/endpoint-repo.x86_64.rpm yum -y install epel-release yum -y install yum-utils yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.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 = "https://app.terraform.io/api/v2/organizations/ZHENGWU/organization-memberships?page%5Bsize%5D=100" 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 $Test.data.attributes.email