1-VPN connection

2-Setup of Remote deDesktop Service (RDS) with Hyper V

3-Quota. Adjusting the storage space (Z)

4-Sharing trough File and Storage Services V1

5-DFS Share and Replication

6-Windows Server Backup

Mainserver 2019 (1)
Server 2019 with 2 clients

On the other side
Hyper-V server (2) with RDS.
Deploying a virtual Windows 10 desktop from hyper-V to a thin client.
On the left side a screen with a thin client.
Right side a second server with RDS and VM.

Server 2 with Hyper V  and RDS

De LAN gaat naar de hub (switch)
Vandaar worden client 1 en 2 verbonden met Server 1 (lokaal) met dat domein
En ook Server 2 met dat domein.
Server 2 rolt een virtuele W10 desktop uit via een VPN als account 3 inlogt
De client kan overal ter wereld staan.
Op een normale computer als client heb je de map documenten met afbeeldingen, documenten, onedrive etc.
Als je daar een shared folder voor aanmaakt op de server dan kan je de onderdelen van die map verplaatsen naar die share.
Als je een document opslaat dan komt dat in die shared folder op de server.

Server 1

Nu uitzoeken hoe je het Office pakket 365 zo kan laten werken dat als je iets opslaat vanaf de VPN client, het dan in onedrive wordt opgeslagen en er voor die account ook een shared folder op server 1 aanwezig is die met dat onedrive synchroniseert.

Install Hyper V

Setup of RDS (thin clients) with Hyper-v in Windows Server 2019 Standard.

2 Servers
Windows server 2019 Standard or Datacenter installed on both server
Main server Should have 2 NiCs, on for the LAN and one for the WAN
Both servers need sufficient amount of RAM, server 2 might need more RAM and a good CPU because it will have to run multiple VMs, if needed it can also use a GPU.
Server 1 with installed ADDS, DHCP and Routing and remote Access.
Make sure server 1 is a domain controller and also give a name the to server itself
Server 2 added to the domain of server 1 with a unique server name and a static IP address which can access the router in Server 1.

Computer Name and Domain should look as below.

It is also recommended to add the secondary server to the list of servers in the Domain Controller
Manage > Add Servers > Find now > server name > double click on server > OK

We will first start of by Installing Hyper V on Server 2.
Hyper V and the Remote Desktop Service (RDS) have to be installed on server 2 because the RDS does not work on a Domain controller, preferably Hyper V should also be installed on a separate server but in this use case we will only make use of 2 servers.

Manage > add roles and features > Next > Role-Based or feature-based installation > Next

Select a server from the server from the server pool > Select the server you want to have to install It on in this case the server 2 > next

Select Hyper-V > add Features > Next

Keep as is > Next


Select the Ethernet adaptor connected to the LAN > Next

Keep as is > Next

Change the virtual hard disk files location the a separate volume, same as the configuration files.

Select the Restart the destination server automatically if required > Next

After the installation is completed and the server has restarted again go to Tools > Hyper-V then right click on the server you installed hyper-v on go to New > Virtual Machine.

Next >

Specify the name you want to use for your template
Next >

In this use case we only have to make use of generation 1
Next >

Assign a decent amount of startup memory to the VM and select Use Dynamic Memory for this virtual machine.
Dynamic Memory allows the VM to make use of more RAM than the designated Startup memory and will only access this extra RAM when it needs it.

Select the Connection you used when installing Hyper-V > Next

Change the virtual hard disk size to 64gb > Next

Install an operation system from a bootable image file > browse > the image of the OS you want to use in the RDS setup (in this case windows 10) > Next / Finish

After this the made VM will show up in the Virtual Machines list
Right click on the template and click on Connect

Click on Connect

After this you will have to install the OS or windows 10 as usual with all the application like 365 a different browser etc on it and also update the OS to the most recent version.

After you are done preparing your template open up a command prompt in elevated mode (as admin)
in the command prompt type:
cd C:\windows\system32\sysprep
and then:
sysprep.exe /oobe /generalize /shutdown /mode

Now the template will prepare itself for use in the RDS.

-Install RDS

Go to add roles and features and select Remote Desktop Services Installation

Select Standard Deployement

Select Virtual machine-based desktop deployement


Select the server you want to act as the Connection Broker

Select the server you want to act as the RD Web Access server

Select the server you want to act as the RD Virtualization host.

Toggle the Restart and then deploy, the server will restart one time during the installation en will continue after restarting.

Go to the Server Manager Dashboard, then go to the new tab of Remote Desktop Services

Go to Collections, click on Tasks and then on Create virtual Desktop Collection.

Skip the Before You Begin page, and at Collection Name give your VM collection an appropriate name

Make sure Pooled virtual desktop collection and Automatically create and manage virtual desktops are selected.

If everything went right then now you should be able to select the virtual template you recently made, if you installed RDS on a domain controller then you won´t be able to see any template, that is why we have installed RDS on a separate server.

Keep these settings like this, next>

Select kompserver.nl as your Active Directory Domain name:, and change the time zone to the appropriate one

Set the amount of virtual desktops you want to create
Change the prefix and suffix if necessary, the prefix and suffix is late user to make a connection to your remote desktop.

Set the allocation number to the amount previously selected.

Keep the default settings on this page too, Next>
You can already enable user profile disks, just make sure to link to the right location. In this case we use \\kompsv1\KPUPD as a storage for the profile disks.

Click on create and then the server will start creating the VM

-Authorizations for groups that need access to the VM
Make sure the VMs in the active directory are in a separate OU, you can also set this when you
creating the virtual desktop collection.

After you haved confirmed the OU the vms are located in go to the Group Policy Management and create a new GPO linked to this OU.

Then edit the new GPO.

Open up the GPO settings as below, then right click on Local Users and Group  and create a new Local Group.

 Make sure Remote Desktop Users (built-in) in the Group name:.

 Click on add and make sure the group that needs access to VMs is selected.

Make sure the policy looks like this in the end.

After the VMs are created open up internet explorer and browse to https://%servername%/rdweb
Click on Go on to the webpage (not recommended)

Enter the user and server you want to use and the password of the user

Click on the VM collection you created.

Click on Connect

After this you should be able to login on the VM, while connecting and logging in to the VM a separate virtual hard disk will be created automatically at the location you used for the user profile disk. Be sure to check this otherwise all files will stored locally on the VM itself or will be deleted once you logout of the VM.

Qouta. Adjusting the storage space (Z)

Select the drive you want to put a quota on and go to properties

Use the setting you want to enable, in this example we will limit the gdisk space to 2gb and add a warning whenever the user exceeds the limit. Click on apply and after go to quota entries.

In this tab, go to Quota > New Quota Entry

Advanced > Find Now > %username%

Again set the quota limits.