Back to 5 remote sessions in 1 VM
Installing (nesting) a second VM in another VM with Hyper-V
Nesting was currently Intel-only but since june 2020:
Windows 10 AMD Machines Now Support Nested Virtualization
This manual is for Intel and for AMD it might be different.
However you can try it.
After you have set up a physical server with 2 clients and you´ve installed a VM on a W10 laptop or computer with multiple remote sessions, we'll now go a step further.
W10 VM in Server 2016-2019 VM
This workshop does not require you to activate the software.
The only limitations are, that you cannot change the desktop and you cannot set the sleep mode.
Nested virtualization is a feature that allows you to run Hyper-V inside of a Hyper-V virtual machine (VM). This is helpful for running a Visual Studio phone emulator in a virtual machine, or testing configurations that ordinarily require several hosts.
- The Hyper-V host and guest must both be Windows Server 2016/Windows 10 Anniversary Update or later.
- VM configuration version 8.0 or greater.
OneDrive for Bussines
M$ promotes Azure coupled with onedrive for bussines
It amounts to rolling out and virtual desktop that connects to a separately created onedrive.
All those separate onedrives are merged into one environment where the administrator has access to each onedrive.
You then have to create separate business OneDrives for all staff members which are then also all accessible by the administrator.
Below is what we would actually want.
But to test it out we would rather not use Azure and
OneDrive for Bussines because of the high cost.
In addition, you should not want M$ and the NSA to be able to dig into your data because of the Patriot Act.
The setup to be tested is to deploy virtual desktops and have the data synchronized via shared folders on the server.
We are first using server 2016
It should eventually become server 2019 but we found that adding clients often leads to problems because they don't get internet.
So installing server 2016 and then if everything works upgrading to 2019 is recommended.
On the Host machine not in the VM
VM has to be off
Assuming that you named that VM Server2019
In Powershell as administrator:
Create a vNAT switch
On the host
In powershell as administrator
New-VMSwitch -SwitchName vNAT -SwitchType Internal
New-NetIPAddress -IPAddress 192.168.1.125
-PrefixLength 25 -InterfaceAlias "vEthernet (vNAT)"
3 New-NetNat -Name vNATNetwork -InternalIPInterfaceAddressPrefix 192.168.1.0/25 -Verbose
On a real server
Manage ad role and features
On al laptop or normal computer
In the searchbox:
Turn windows features
Go to the ISO from W10 1607
Stand on it and choose Copy (not drag and drop)
Paste that on the C from the Server2019 VM
On the same C a new folder Server2019
Search in the list for Administrative Tools
Right button Hyper-V manager
More, Pin to taskbar
Make a folder Make a second VM Win-10 same way as Server 2019
Choose United States
Choose no product key
New and apply
installation go to the website and download the Wrappaer
Extract the Wrapper Package
Set al the items on the dektop
Go to the privieus instalation of Wndows 10 VM and create extra accounts etc.