Back to index VM
On a server domain
W10 VM in a Server VM
Installing Hyper V with multiple remote desktop sesions on a
Server, a Windows 10 stand alone computer or laptop in a real network on just 1 VM
Using the wrapper technique for (thin) clients, we finally managed to activate 5 accounts with 1 VM on different computers. But even more can also.
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.
A server has a domain to connect the clients with a LAN
Because we install a server with only a few clients, we use a simple hub for this practice task.
Bert and Ernie had been added to the domain as users.
But for this setup they were removed from the domain by putting them back in the Workgroup as a normal stand alone machine.
With this system, you no longer need a LAN.
A server has an incoming WAN and an outgoing LAN to the clients.
That means 2 internet connections
Incoming and outgoing.
That makes it tricky on a laptop (or normal computer) because you only have a WAN connection.
Now you can run a VM with multiple remote desktop sessions on a server, a laptop or a normal computer.
And also from home with a VPN connection.
Read the whole article before you begin.
Your PC must have a 64 bit Windows 10 Pro installed with 8-16gb internal memory.
You can upgrade from Home to Pro.
See of virtualisation is present and enabled in the BIOS
For the Hyper V is a separate partition created of 50 GB
Total 3 partitions
D: 50 gb with a folder called VM-1
E: for the data
We're going to install Windows 10 version 1607 and if that all works then we'll create an image of that which will then reside on E.
Should the VM upgrade to the latest version then we can restore the Windows old file, but if necessary also the image.
Run the following
command in Powershell as administrator.
DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V
Go left to start and search in the list.
Pin to taskbar
For Windows 10, version 1607 was used and with the accompanying wrapper it did work.
The exercise with 1 computer with 2 extra accounts connected via thin clients.
If you have 2 extra accounts on a normal computer then you actually have 3 desktops.
But only 1 person can work on it.
Those 2 extra desktops were connected with a remote desktop session via thin clients,
10 is also possible and they still work since 2011.
First W7 a
First W7 and now with W10
Traineeship IT students Zadkine (MBO level 2)
Download the tool with which you can then connect to the Win-10 ISO download site.
You will immediately be offered the latest version, but you choose the 1607.
This workshop is meant as a practical exercise to teach you the principle.
If you really want to use it then you can download the latest version of Windows 10 and you have to look for a wrapper that works with it.
We were able to find the Wrapper for the 21H1 (May 2021) and you will come across it as a download later in this workshop.
But by that time there will be another new version and then even Windows 11.
So we'll stick with the 1607 just to be sure because that works with that Wrapper 6.1
It is recommended to install that 1607 first.
Then you will also learn to avoid upgrades with the Windows-show-hide tool.
Set the ISO were you want. In this case on the D.
Create a new empty folder with the name VM-1 on a partition with more than 40 gb free space.
In this case on the D.
Start Hyper V Manager
Hyper V and that VM need to be installed on 1 location in the same network
Click on Virtual Switch manager
There may only be that default switch.
When there is allready a new switch you have to remove it.
Then click on New Virtual Switch
Choose new virtual machine
Chance that name New Virtual Machine in something else as VM-1
If you don't change that default name, then that seems to be the reason that the VM remains attached to the virtual default switch with the IP range 172.20... instead of 192.168... and the wrong subnet mask of 255.255.240.0
the machine with the VM
Network IP in the right IP range and a Default Switch with the wrong IP range.
But this is normal because the host machine with the VM shall not find the new virtual switch.
On the VM
The default switch with the wrong IP address and subnet mask.
The new switch with an IP address in the right IP range.
And also has internet.
That VM has to use the same IP range as your laptop or computer.
For that, you are also going to set up a new virtual switch that will (hopefully) be attached to your network card with the correct IP range.
Change the memory to 4500mb
Make not the mistake to choose the default switch
Then it will use the wrong IP range started with 172..
Choose for new virtual switch and then it will use the IP
range from the host computer.
In this case it will be 192.168.1.125
Browse and select that empty folder
Change the size to 40 GB
Browse to that ISO
Click on Virtual Switch Manager
When you see default switch and the new switch with the name of the manufacturer from your networkcard it should be allright.
Start W-10 instalation
Open Hyper V manager, stand on the hyper V installation with the right mousebutton, start and then connect.
Then the W-10 installation begins.
For this workshop you do not need any activation.
Choose United States
You can skip that. (have no product key)
Click on New and Apply
When completing that Windows 10
installation you will need to make a few more choices
School or work
Join a domain
Enter username and password.
If Windows 10 (1607) is installed in Hyper V, see if you you have internet and your IP address is in the same range as your computer.
Open CMD in the VM and type: ipconfig
In this case we have internet and the right IP range and subnetmask for that new virtual ethernet adapter
Click on new virtual switch.
Yo have to see the name from the networkcard.
Restart the VM.
If it is not working then it can be quite troublesome.
Type Hyper V default switch in Google and you will see that many people struggle with that.
Turn off the VM
Virtual Switch Manager on the right
Delete the virtual Switch on the top left
Create a new one (external)
Restart the VM.
Is your Hyper-V still not connecting to the Internet ? Try this.
If you think: I just want to start a new VM then you can delete that not working VM.
Delete the VM folder.
Create an new folder for the VM.
If it works properly we will continue with that VM.
Type sharing in the searchbox
Manage advanced sharing settings
Network discovery has to be on.
Click on all networks.
There should be the same Network discovery should be on.
Also the other options.
Then you can check if network discovery has stayed on. If not, change that.
If it keeps jumping back to
Type in the search box: services.msc
There must be 3 services on
Probably they are on manual.
1- Function Discovery resource
2- SSDP discovery
3- UpNp device host
You have to set it to
automatic and start it up.
Then check whether network discovery is on or not.
On the VM
Dowload the Wrapper with the Windowsupdateshowhide tool, OOSU10 tool, Setup Chrome and Firefox.
In this download you will also find the Wrapper 6.2 with the update for version 21H1 (May 2021)
Download and install 7zip 64 bit.
Extract that zip file.
Right mouse button on that file.
In that zip file you will also find a notepad file with the URL for this manual.
Put the contents of that folder as separate items on the VM desktop.
Open the Wrapper folder
Click on install as administrator.
Then on update as administrator.
It may be that the VM is interrupted.
Click on install and update again as administrator.
When it is not listening try update again.
If it is indicated that you need to download or install something it must be done in that VM.
Now Windows has the annoying habit of releasing an upgrade every 6 months and then that wrapper no longer works.
You now have 1607 with the wrapper that goes with it and when you upgrade you should look for a new custom wrapper on the internet.
The first thing you do if that VM works is go Windows update settings in that VM.
Activate defer feature updates
Activate defer feature updatesIf that version is upgraded then you can revert that.
Before an upgrade is installed windows makes a copy of the existing installation and saves it as a Windows Old file.
You have 30 days to reverse this.
It goes like this.
You start that updated VM whose wrapper no longer works.
As soon as you see that Windows is starting you force a shut down of that VM.
You do that a few times in a row until you see the message.
Then you come to the troubleshooting screen and you can restore that previous version.
Using theo Windows shutup tool may also help to prevent an upgrade.
But you can also hide an upgrade with the Windows Show-hide tool if it presents itself.
Create 2 additional accounts as we did with those thin clients.
Go to settings, accounts.
If you want to create those 2 accounts then there is a thick red line with the warning that you need to activate Windows.
You can ignore that.
The only limitation, as far as noted, is that you cannot change the appearance of the desktops.
Create 2 accounts Frank and Mark.
Go to settings and accounts to add someone.
Click on: I don't have person's sign in imformation and then on:
Ad a user without....
Enter name and password.
You can use the same password for all of them.
That is convenient to test.
Change the account type from local account to administrator.
And then the seond account.
Then you need to be logged in to those accounts to complete the installation.
Go to system and Advanced system settings
Click on remote and allow..
You should do the same for the machine itself.
Then you can get the desktop of another computer just like teamviewer.
It must be visible in the network with a password that you can use to log in.
The user must be logged off.
Networkdiscvovery for the machine itself does not need to be on if you do not want to be seen in the network.
Basically a protection, so they can only access the VM on the network.
On the VM
Click on Select users.
On the VM
Click on settings to find the VM name.
Go to another
computer connected in the same network .
This PC and left under you see network with the visible computers.
Rigt button on that VM name and start a remote session.
Then you will get the VM login screen and you can log in those clients.
Is that VM still not visible on the network to other
Change Network Profile Type Windows 10 Using Registry
You can also change network profile by using Registry if option to change network from Public to Private is missing.
Step 1. You can press Windows + R to open Run. Type regedit and hit Enter to open Windows Registry Editor app.
Step 2. Click as follows to find the target key: HKEY_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Windows NT -> CurrentVersion -> NetworkList -> Profiles
Step 3. Expand Profiles and expand each folder under Profiles to find the ProfileName key which lets you recognize the Network you want to change setting.
Step 4. Double-click Category DWORD open it, and change the value from 0 to 1 to change network from Public to Private or in reverse.
Read the next chapter if you get the CredSPP error.
You don´t have to disable the firewall as we did
with the thin client
installation, you can leave it on here.
If you have a connection problem, it is due to a 2018 update.
And you get this error message.
Keep in mind that you can probably only make that system work in the network where you installed it.
Connect your laptop to another network and then see if the ip range of your laptop matches with the ip range of your VM.
If not. Can you try deleting the new virtual switch and creating a new one, which then hopefully assumes the IP range of that network.
The 1607 has a working wrapper (6.1)
If you get an upgrade then you will have to look for another wrapper.
Windows downloads updates in the background.
To prevent an upgrade, that OO tool is already set, but M$ keeps trying to take it down.
You should also regularly click that tool to check if the settings are still correct.
Microsoft releases a cumulative update every month, which also tries to disable that OOSU10 tool every time, to push those upgrades through anyway.
Together with that tool and that Windowsshowhide you can prevent those upgrades.
But you can also look for a working Wrapper for the latest version.
Activate deferring of upgrades and automatic driver updates has to be green
M$ update your drivers (?)
If it works don´t fix it.
The problem of driver updating occurs most often in the laptops with the Qualcom wifi cards.
If you suddenly have no wifi, go to device manager.
Click on network adapters.
Then you will see the wifi network card.
Click on that with your right mouse button
Search on my computer.
I want to choose from a list.
There should be only one driver there.
If you see more than one then click on the second and install.
And then it's waiting for the next wrong update.
A USB wifi adapter is a better solution
Use the Windows show hide tool
Click on that show hide tool.
Remove the check mark for automatically repairs
Ladys and gentlemen. We got him!
But that´s not the latest version, so the risk of another upgrade remains.
You don't need activation for this workshop.
If you do want to activate then that can still be tricky.
Open Notepad in the VM, type your W10 Pro activation key and save that on the desktop.
It may happen that you have entered the correct ativation key but W10 is still not activated.
Go to settings, update and security and click on activation.
If that fails.
Start CMD as administrator en type;
Copy the product key from the notepad file.
first Method 5
Follow the instructions.
Method 5. Rebuild the Tokens.dat
1. Open Command Prompt as Administrator.
2. In command prompt, type the following command and press Enter.
net stop sppsvc
3. Without closing command prompt, navigate to the following folder:
4. Rename the "token.dat" file to "tokens.old".
Go back to command prompt window, and
give these commands, in order:
net start sppsvc
cscript.exe %windir%\system32\slmgr.vbs /rilc
6. When the commands are executed, reboot your system twice.
A reboot means to restart that VM not the computer itself.
7. Finally, go to Start menu
8. Start CMD as administrator and type;
Then you may get another error message but it thurns out that Windows is actvatede anyway.