Getting Started with Windows Server Version 1709 Management

Absrtact: I believe some of the students will have this experience, in the public cloud to buy windows Server version 1709 Datacenter Edition of the virtual machine, through the remote connection in, there is a dark command line, and nothing else. This, a face ignorant ah.

I believe some students will have this experience, in the public cloud to buy windows Server version 1709 Datacenter Edition of the virtual machine, through the remote connection, there is a dark command line, and nothing else. Is it poisoned? The system is broken??? This, a face ignorant ah.

First of all, please do not panic, the system is normal.

What is Windows Server, version 1709?

Windows server, version 1709 runs in Server Core mode. This means that there is no graphical user interface. Why would you do that? According to Microsoft, it can provide powerful advantages, such as lower hardware requirements, smaller attack surfaces, and reduced update requirements (which I cannot agree with, and others can accept). And in this version, Microsoft does not provide a graphical interface to the Server core conversion. It is possible that in Windows Server 2012/R2, the conversion of the graphical interface to Server core often goes awry, in 2016 it is a little bit rough, once installed, the conversion is forbidden. By the 1709, there is no graphical interface directly.
The main differences between Server Core and normal Windows Server with GUI graphical interface are as follows:

• The Explorer is gone. We are familiar with Windows Explorer and cannot appear in Server Core.
• All the console interfaces that depend on MMC are gone. This means that running *.msc will not work. For example: We cannot open the Device Manager by running Devmgmt.msc.
• In addition to the region and language and time, other control panel options are gone.
• Compared to the "famous" IE also did not have.

Introduction to Windows management tools

Maybe for Linux, Windows Server Version 1709 is more like Linux. Many people who are accustomed to the Windows operator interface (using Windows without a graphical interface, life will be meaningless:), the use of Server Core does not work. This section provides a few windwows to manage the big kill: PowerShell and Project Honolulu, and so on and a brief introduction to this.

PowerShell

Thanks to PowerShell, Windows frees up productivity from the traditional DOS command line and batch processing. The father of PowerShell, Jeffrey Snover, was Linux before joining Microsoft. So, we can see the Linux Shell's shadow like LS, wget, curl and so on everywhere in PowerShell. But PowerShell is definitely not a simple shell upgrade. PowerShell relies on the. NET framework for powerful object-oriented scripting. With the. NET Framework's open source and cross-platform, PowerShell Core has also been officially launched on Linux.

Microsoft naming has always been very low-key, but PowerShell named directly with a power, visible this feature is powerful. After inventing PowerShell, Jeffrey was promoted directly to Microsoft's distinguished engineer and dominated the architecture design of Windows Server 2012 (running away, back).

Opening PowerShell in Windows Server Version 1709 is simple, and entering PowerShell (case insensitive) directly on the command line can open PowerShell for action.

PowerShell can also remotely manage Windows machines like SSH. The following example configures PowerShell remote in a workgroup environment, assuming that the managed machine IP is 172.16.158.183.

• On the managed machine, run the following PowerShell command:

Enable-PSRemoting -ForceSet-NetFirewallRule -Name "WINRM-HTTP-In-TCP-PUBLIC" -RemoteAddress Any

• If the security group has restrictions, open the 5985 (HTTP) and 5986 (HTTPS) ports to this machine in the direction.
• On the client machine (which requires remote connection to the managed machine), run the following command to accept that the managed machine is trusted. If you want to manage any machine, replace 172.16.158.183 as *.

Set-Item WSMan:localhost\client\trustedhosts -value 172.16.158.183 -Force

Otherwise, the next Enter-pssession may report the following error:

Enter-pssession: Connection to remote server 172.16.158.183 failed with the following error message: The WinRM client could not process the request. If the authentication scheme differs from Kerberos, or if the client computer is not joined to the domain, you must use the

HTTPS transport or the destination computer must be added to the Trustedhosts configuration settings. Use Winrm.cmd to configure Trustedhosts. Note that the computers in the Trustedhosts list may not be authenticated. You can get more information about this content by running the following command: WinRM help config. For more information, see the About_remote_troubleshooting Help topic.

Location Line: 1 characters: 1
Enter-pssession ' 172.16.158.183 '-credential: ' Administrator '

 CategoryInfo          

• This allows the remote "SSH" to the managed machine via the following PowerShell commands on the client machine. (Enter the password or enter a password)

Enter-PsSession –ComputerName 172.16.158.183

Microsoft Project Honolulu

Microsoft also announced a project called Honolulu when it was released in 1709. Honolulu is the capital and port city of the state of Hawaii, USA. The Chinese call it Honolulu (and run away). The Honolulu project is a browser-based graphical management tool. He is the administrative tool that replaces Server Manager and MMC in Server Core. Honolulu can be downloaded from the following websites:
Https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-honolulu

Honolulu Management Configuration Method:

1. On the managed server 1709 machine, run the following PowerShell command:

Enable-PSRemoting -ForceSet-NetFirewallRule -Name "WINRM-HTTP-In-TCP-PUBLIC" -RemoteAddress Any

1. If the security group has restrictions, open the 5985 (HTTP) and 5986 (HTTPS) ports to this machine in the direction.
2. (Steps 3rd and 4th only need to be done in one step.) Download and install the Honolulu tool and install it on the managed server 1709 machine.

First, the installation on the server 1709 machine is described. The following PowerShell command was used to download the MSI tool on the managed machine.

wget -Uri http://download.microsoft.com/download/E/8/A/E8A26016-25A4-49EE-8200-E4BCBF292C4A/HonoluluTechnicalPreview1802.msi -UseBasicParsing -OutFile c:\HonoluluTechnicalPreview1802.msi

After downloading, use the following command line to perform the installation. The command is returned immediately.

msiexec /i c:\HonoluluTechnicalPreview1802.msi /qn /L*v log.txt SME_PORT=443 SSL_CERTIFICATE_OPTION=generate

To verify that the installation was successful, you can use the PowerShell command cat Log.txt to view the installation results. If you have the following words, the installation is successful.
MSI (s) (14:44) [09:48:37:885]: Product:project ' Honolulu ' (technical Preview)--installation completed successfully.
MSI (s) (14:44) [09:48:37:885]: Windows Installer installed products. Product Name: Project ' Honolulu ' (Technical preview). Product Version: 1.1.10326.0. Product language: 1033. Manufacturer: Microsoft Corporation. Installation success or Error status: 0.

3. (Steps 3rd and 4th only need to be done in one step.) This tool can also be installed on any client machine that is remote as a PowerShell.

can be downloaded and installed in a browser.
After the installation is complete, you can open https://localhost/and add the address of the machine that we need to manage for server 1709.

4. Once the installation is complete, you can open it through any browser that has access to the machine where the Honolulu is installed. It was a surprise that Internet Explorer was not supported. You must have Microsoft edge or Chrome.

Sconfig

This tool is available on the day that the Server Core was born. But now it's hidden. This command can occur when you enter sconfig on the command line. Can meet the basic needs, the function is not very powerful.

Remote server Manager

This is the main form of management, but the read-only feature is more, you can operate a few configurations. The secret has been superseded by Project Honolulu, so this article does not describe it.

Common Operations FAQ for managing Windows Server, Version 1709

How do I copy files to server 1709?
This assumes that the file to be copied is on the client machine. Both the managed machines on both the client machine and the server 1709 have been configured as described above through PowerShell remote and through project Honolulu methods.

Via Remote RDP

1. On the client machine, right-click the file and select Copy.
2. Remote MSTSC to server 1709
3. On the remote machine, open Notepad. file, and then click Open. In the Open dialog box, select the path of a disk and right-click Paste. The file is copied over. This is one of my favorite ways.

Remote via PowerShell

Run the following PowerShell commands on the client machine:

$session = New-PSSession -ComputerName 172.16.158.183Copy-Item -ToSession $session -Path C:\1.txt -Destination c:\2.txt

C:1.txt is the file location of the client machine. The C:2.txt is the location to be copied to the target machine.

Through Project Honolulu

Click on the managed machine--file--upload.

How do I shut down or restart the server 1709 virtual machine from the inside?

Via Remote RDP

1. Remote RDP to server 1709.
2. Enter sconfig on the command line, then select 13-reboot as needed, 14-turn the machine off and enter it.
3. or enter the following command line/powershell to restart or shut down directly:

shutdown -r -t 00 ::命令行 在0秒后重启shutdown -s -t 00 ::命令行 在0秒后关机Stop-Computer -Force # Powershell 立即关机Restart-Computer -Force # Powershell 立即重启

Remote via PowerShell

Run the following PowerShell commands on the client machine:

Enter-PsSession –ComputerName 172.16.158.183Restart-Computer -Force #重启Stop-Computer -Force #关机

Through Project Honolulu

Click on managed Machines--overview.

How do I install the IIS service?

Via Remote RDP

1. Remote RDP to server 1709.
2. Enter PowerShell at the command line, and then execute the following PowerShell command:

Import-Module ServerManagerAdd-WindowsFeature Web-Server, Web-CGI, Web-Mgmt-Console

Remote via PowerShell
Run the following PowerShell commands on the client machine:

Enter-PsSession –ComputerName 172.16.158.183Import-Module ServerManagerAdd-WindowsFeature Web-Server, Web-CGI, Web-Mgmt-Console

Through Project Honolulu

Select the Web server and determine the required features by clicking on the managed machines, roles and features.

Accidentally closing a command-line window in an RDP session what do I do?

If you accidentally close the command line window in a remote session, you can send the Ctrl + Alt + DEL key combination via Remote Desktop, and then the task Manager will appear after you select Task Manager enter in the interface that appears, click File--New task, and then enter CMD.

Original link

Read more about dry goods, please scan the following two-dimensional code:

Getting Started with Windows Server Version 1709 Management