Installing Windows Admin Center in Windows Server Core mode

Before you introduce the features and interfaces of Windows Admin Center: http://blog.51cto.com/rdsrv/2103443

But installing Windows Admin Center is a Windows Server 2016-based graphical GUI installation of Windows Admin Center, and today I mainly introduce you to Windows Server 2016 In core mode (no GUI) Install Windows Admin Center, why should I separately describe installing Windows Admin Center in core mode? Because I think that the future of Microsoft's server operating system and enterprise-class products such as Exchange Server will support the installation in core mode, so that Windows Server in the core mode to save resources, start faster, more secure and stable, Reduce the number of problems caused by human error operation

Note: When you install Windows Admin Center on Windows 10, port 6516 is used by default, but you can choose to specify a different port.

First I install a system ready for Windows Server core to install Windows Admin Center

The administrator password is required to install the system when it is booted.

Enter the set Administrator password after clicking OK

Administrator Password Setup Complete

Next, set the firewall to open file and printer sharing policies and HTTPS policies

netsh advfirewall firewall add rule name= "HTTPS" Dir=in action=allow protocol=tcp localport=443

netsh advfirewall firewall set rule name= "File and Printer Sharing (smb-in)" New Enable=yes

Next, you can copy and upload Windows Admin Center's installation package to this Windows Server (the following server is called Admincenter) via the network.

At the WindowsServer Server Core installation, you can install Windows admin Center by using the command prompt (run as administrator). Specify the port and SSL certificate using the Sme_port and Ssl_certificate_option parameters, respectively. If you want to use an existing certificate, use Sme_thumbprint to specify its thumbprint

Run the following command to install Windows Admin Center and automatically generate a self-signed certificate (the automatically generated certificate expires 60 days after installation):

msiexec/i <windowsadmincenterinstallername>.msi/qn/l*v log.txt sme_port=<port> SSL_CERTIFICATE_OPTION= Generate

Run the following command to install Windows Admin Center with an existing certificate:

msiexec/i <windowsadmincenterinstallername>.msi/qn/l*v log.txt sme_port=<port> SME_THUMBPRINT=< Thumbprint> ssl_certificate_option=installed

Here I use a self-signed certificate:

Next, navigate to the C packing directory, install Windows Admin Center and log the installation log Log.txt file

msiexec/i windowsadmincenterpreview1807.msi/qn/l*v log.txt sme_port=443 ssl_certificate_option=generate

To view the installation log, a successful installation occurs as follows

Finished here, but I met a very strange problem, that is, after the installation can be seen in the service Windows Admin Center is running, but with Netstat-na to see the lack of listening 443 port, it is natural that my WAC site can not open, If you encounter me the same problem can take the following methods:

Run regedit in cmd to open the registry

Create a new 2 registry value in the following location:

Next, enter PowerShell in CMD to go to PowerShell mode and perform the command to restart the system

Restart-computer (Shutdown is stop-computer)

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

remark:

run under PowerShell:

View current computer name: hostname

Modify Computer name: Rename-computer-newname admincenter-computername.

computers that have been added to the domain need to modify the computer name: Rename-computer-newname admincenter-computername.-domaincredential Domain\User

Add the server domain: Add-computer-domainname corp-restart

Join the workgroup: Add-computer-workgroupname WORKGROUP

use domain Administrator account fallback domain: remove-computer-unjoindomaincredential contoso\administrator-passthru-verbose-restart

List Firewall all rules: Get-netfirewallrule | format-table name, displaygroup, action, direction, Enabled-autosize

allow all Remote Desktop connections (a rule that opens a firewall): Enable-netfirewallrule-displaygroup Remote Desktop

cmd under execution:

View current IP address: Ipconfig/all

Modify the IP address and DNS address (in modifying the DNS server address, Index=1 is the preferred DNS server address, index=2 is the alternate DNS server address):

Turn on Remote Desktop Connection: cscript c:\windows\system32\scregedit.wsf/ar 0

Disabling Remote Desktop Connection: cscript C:\windows\system32\scregedit.wsf/ar 1

To view Remote Desktop Connection status: Cscript c:\windows\system32\scregedit.wsf/ar/v

To view the current Windows update settings: cscript c:\windows\system32\scregedit.wsf/au/v

To Enable Automatic Updates:

Net Stop Wuauserv

cscript c:\windows\system32\scregedit.wsf/au 4

Net start Wuauserv

Disable Automatic Updates:

Net Stop Wuauserv

cscript c:\windows\system32\scregedit.wsf/au 1

Net start Wuauserv

force Windows Update to immediately detect and install any available updates: Wuauclt/detectnow

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Restart the server and then you can see the 443 port work, and now open https://10.20.30.101 again to see the Windows Admin Center site

Click on the server name here to see the detailed information, such as in the core mode, the server's memory in the installation of Windows Admin Center only occupied more than 600M points.

Restart and start, shut down and so fast, because it is the core, it is not feel like playing Windows Server is playing Linux?

Installing Windows Admin Center in Windows Server Core mode