Hetzner hosting Windows Server 2019 Standard pojasnjenje licence

Use of own licenses
We take part in the Microsoft SPLA Program. The Windows License made available to us is thus an SPLA License. The combining of clients´ own Microsoft licenses with the Hetzner SPLA License would have to be put in writing (contract), as the client would have to commission Hetzner to host the product. Furthermore, the deployment of an own Microsoft license would not be possible in every case (e.g. for terminal server licenses). Therefore, in view of the increased administrative time and effort that would be involved, we have chosen not to permit the combining of licenses. Hence, the use of own Microsoft licenses on a Windows operating system leased from us is not possible.

However, a client is able to install their own Windows version, using their own license. It is possible to install Windows via a KVM Console.

Included license for Hyper-V in the Standard Edition
As part of our SPLA license you have an additional license for use on a Hyper-V instance when using the Standard Edition. You can use this as follows:

Order an additional single IP via Robot (for subnets see Windows Server Subnet)
Make a note of the virtual MAC
Create a new instance
Add the Legacy Network Adapter and assign the MAC
Start the instance and let it boot via PXE
If successful the Hetzner PXE Boot Menu will appear (blue logo)
Activate the Windows installation via Robot for the additional IP
Boot the instance via PXE again, and instead of the Hetzner menu the installation of Windows is started. Once the standard login screen appears you can use the instance

Each virtual machine is opened in a separate Virtual Connection Manager interface (vmconnect.exe)

The Virtual machine Connection client application (VMconnect.exe) uses the Remote Desktop Protocol (RDP).

The Single Port Listener for RDP in the Virtual Machine Management Service listens for incoming connection requests on TCP port 2179 on the parent partition.

The Virtual Machine Connection client application uses the Terminal Services ActiveX control, mstscax.dll to make the connection to TCP port 2179 when it is launched.

This ActiveX control is the same ActiveX control that is used by the Remote Desktop Connection (RDC) client application, mstsc.exe.

The Virtual Machine Connection client application is simply a shell that utilizes the Terminal Services ActiveX control. This becomes most evident when the Virtual Machine Connection client application is set to the full screen view.

When the Virtual Machine Connection client application connects to port 2179, the Virtual Machine Management Service routes the communication to the worker process for the specified virtual machine.

At the current situation, it only allow one session when you connect to the Virtual Machine.