Windows Server 2019 installation summary (vs 2019 build tool)


FROM: Original

The Essentials: After Windows Server 2019 Evaluation Installed

Trial evaluation version

Windows Server 2019 allows 180 days of trial. After the trial expires, it can be reset five times to extend the evaluation period, so it is a rare basic tool.

Windows Server trial official website:here

Extended Probationary Periods

The order to extend the probation period is:

slmgr.vbs -rearm

Windows Server 2019 Evaluation Keys:

Key is used to evaluate the following products:

Windows Server 2019 Standard


Windows Server 2019 Datacenter


Version comparison: core and desktop experience

There are several versions of Windows Server 2019:

The first is the division of large versions:

  • Data Center,
  • Standard,
  • Essentials (desktop experience minor version only)

In addition to the large version, there is a large version of Hyper-V server 2019, which only includes the small version of server core). I won’t mention it more.

The minor version is divided into server core and with desktop exxpirience. The difference is whether there is a GUI environment.

Server Core

For the server core, there is only one command line box interface:

Windows Server 2019 installation summary (vs 2019 build tool)

However, the so-called no GUI only means that there are no GUI management tools (such as start menu, various control panel elements, etc.), in fact, it allows you to launch the desktop app from the command line interface. For example, visual studio 2019 build tool will be started and run in a separate window interface:

Windows Server 2019 installation summary (vs 2019 build tool)

The installation management interface will come out later.

In the server core, at least these applications are incompatible:

  • Microsoft Server Virtual Machine Manager 2019 (SCVMM)
  • System Center Data Protection Manager 2019
  • Sharepoint Server 2019
  • Project Server 2019

In addition, at least these system components are incompatible: Windows tiff ifilter, internet printing client, ras connection manager kit, simple TCP / IP services, TFTP client, windows search service, XPS viewer, etc

You can see incompatibilities that have almost nothing to do with ordinary people.

In addition, you can basically think that the core is a lighter version. Its installed size is about 5.1gb, which is relatively rare.

Desktop Experience

Of course, you can start the operation through the command line menu of windows experience 11, and you can also start the operation through the command line menu of windows experience 11.

Here is the reference drawing of the interface:

Windows Server 2019 installation summary (vs 2019 build tool)

Windows Server 2019 with Desktop Experience — The Classic Look (e.g. Windows 10 1809)

The screenshots during installation are as follows:

Windows Server 2019 installation summary (vs 2019 build tool)


Therefore, the official address can be seen in the installation interface of Windows Server 2019 ISO, which is usually as follows:

  1. Windows Server 2019 Standard (Desktop Experience)
  2. Windows Server 2019 Standard

Therefore, 2 is the server core version.

Disk size occupation

Server core is a lighter version. Its installed size is about 5.1gb.

As a reference, an ordinary windows 20h2 occupies about 20GB after installation, while the installed size of a Windows Server 2019 standard (desktop expirience) is about 8.6 ~ 9.3gb.

Version comparison

The official comparison table is here:

Comparison of Standard and Datacenter editions Windows Server 2019 – Microsoft Docs

If it’s too long, look here first:

Windows Server 2019 Licensing & Pricing – Microsoft

Post installation summary

Check server IP address

have access toipconfigperhapsipconfig /all

Enable Remote Desktop on Server Core

Enable remote desktop on Server Core

Following are the steps to enable remote desktop on Windows Server core.

Follow the steps below to enable remote desktop for Windows Server core.

Start the Server Configuration Tool, login to your Windows Server (2016/2019) core. Type SConfig and press Enter.

Log in to your Windows Server 2016 or 2019 core and run the server configuration tool: EntersconfigAnd enter.

You will find a list of options under Server Configuration. From the list, take a look at option 7 which is for Remote Desktop. Notice that Remote Desktop is currently Disabled

You will see that the sconfig command displays a list of options. Select item 7 in this option table, the remote desktop entry. By default, this item should be “disabled”.

Windows Server 2019 installation summary (vs 2019 build tool)

Press 7 and hit enter. The next line that you see lets you Enable or Disable remote desktop. To enable the remote desktop, type E and press enter key.

Press the key7And enter(Enter)。 The next line prompts you to enable or disable remote desktop. To enable it, press the keyEAnd enter.

Now you see two options: – now you will see two sub options

  • Allow only clients running remote desktop with network level authentication (more secure)
  • Allow clients running any version of remote desktop (less secure)

Type 1 and press Enter. You get a confirmation box for enabling Remote Desktop. Click OK.

Press the key1Press enter and you will see a confirmation dialog box. Click OK to confirm it:

Windows Server 2019 installation summary (vs 2019 build tool)

Now take a look at option 7, it shows Remote Desktop Enabled (more secure clients only).

Now look at option 7, which shows that remote desktop has enabled all clients.

Windows Server 2019 installation summary (vs 2019 build tool)

In the next step we will enable the firewall to allow the remote desktop. Type 15 which is an exit to command line.

Next, we need to allow the connection of remote desktop to enter on the firewall. Press the key15Press enter, that is, select option 15 to exit the menu interface of sconfig and return to the command line.

Now type the below command and press enter key.

Now enter the following command and enter to run it:

netsh advfirewall firewall set rule group="remote desktop" new enable=Yes

You get a line that reads Updated 3 rules.

It allows remote desktop connections to pass through.

Windows Server 2019 installation summary (vs 2019 build tool)

Original: Enable Remote Desktop On Server Core – Prajwal Desai

Modify the host name of the server

Similarly, use the sconfig command. The second item is to modify the computer name.

Add operator account

If you don’t want to log in as administrator, you need to add your own operator account. Still use the sconfig command and select item 3 (add local administrator).

Enable file sharing

The following command enables file sharing:

netsh advfirewall firewall set rule group=”File and Printer Sharing” new enable=Yes

Then you can connect to the server core through the manager sharing point:

# in macOS
open 'smb://server-core/admin$'
open 'smb://server-core/c$'

Net use command

Net use | Microsoft Docs)

Simple way

The typical way to load Samba resources in LAN is:

net use z: \\hz-pc\downloads password /user:hz

You can delete it after using it:

net use z: /delete

/Savecred mode

You can use/savecredTo create the drive letter, so that there is no need to explicitly enter the password and user parts in the future.

net use z: \\hz-pc\downloads /savecred /persistent:yes

An example is as follows:

Windows Server 2019 installation summary (vs 2019 build tool)

Command line format

Net use command has the following standard forms:

net use [{<DeviceName> | *}] \
   [\\<ComputerName>\<ShareName>[\<volume>]] \
   [{<Password> | *}]] \
   [/user:[<DomainName>\]<UserName] >[/user:[<DottedDomainName>\]<UserName>] \
   [/user: [<[email protected]>] \
   [/savecred] [/smartcard] \
   [{/delete | /persistent:{yes | no}}]
net use [<DeviceName> [/home[{<Password> | *}] \
   [/delete:{yes | no}]]
net use [/persistent:{yes | no}]

Because we imply that the context is to connect to a Windows server or a Windows Server core server remotely, the persistence form of the net use command is usually meaningless. When net use is needed in this context, it is generally because we downloaded the installation disk on the download server in LAN in advance, so we need to link to the download server and then install visual studio 2019 build tool, etc.

Remote Desktop

RDP mode

You can use the free RDP client tool on MacOS:

CoRD: Remote Desktop for Mac OS Xperhaps

Remote Desktop Manager Free

Note that remote desktop manager free requires you to register an account to use it for free, or you can simply buy an enterprise license

If you are evaluating or managing an azure server, you can use the remote management tool embedded in the azure management interface.

VNC mode

If you are using home edition versions such as windows 11 (such as notebook preset OEM), the Remote Desktop Services on these workstations cannot be activated, which is shameful – so you need VNC tools at this time:

TightVNC: VNC-Compatible Free Remote Control / Remote Desktop Software

SSH mode

You can also use openssh tool to connect to the server remotely through SSH:

Install openssh | Microsoft docs


When initiating a remote management session from a Windows workstation, you can also use the tool windows admin center, which is a special tool officially issued by Microsoft.

Install visual studio build tool

Official website:Download visual studio 2019 for windows and MAC

Visual studio 2019 build tool can be simply regarded as a GUI free version of visual studio.

Create offline installation package

reference resources:

First, Download vs on the official website_ Execute the setup file, and then use this command line to create an offline package:

vs_buildtools__2036376674.1537335944.exe --layout .\vs2019bt_offline  --lang en-US

Pay attention to the vs you downloaded_ The name of the setup executable file and replace it with itvs_buildtools__2036376674.1537335944.exepart.


After downloading the offline package OK, you can connect to the server of the offline package through Samba file sharing on the server core:

net use z: \\hz-pc\d

Then go to the subdirectory to initiate the installation process:

cd /d z:\downloads\\vs2019bt_offline

Then check in the separate installation window and complete the installation.

Disk size

Installed C + + (with ATL and MFC) and Net build tool requires about 17GB of disk space. Therefore, after we installed the vs2019bt tool on a server core, the whole disk space is about 22.2gb, which is very speechless.

This is a huge consumption in all aspects.

Therefore, I still admire the Windows C + + build server in GitHub actions. Each push is accompanied by a download of the build server, startup, scheduling and building CI commands until they are destroyed


Write so much for the time being.