Microsoft on prem RDS deployment best practices and high level steps for implementation

Can someone please provide some updates here?

Thank you.

Microsoft has simplified this considerably.  Have you gone through the wizards?

no, can you please elaborate and be more specific?

determine which windows server(s) you want to remote desktop into.
The quick install will setup everything on one server
you will need RDS CALS and a license server
Workgroup you must use per-device CALS and manage via powershell
Domain - your choice per-device/per user and manage using Server Manager or powershell

RDS has many flavors:
remote desktop ONLY - you login to the RDS server as a user
User Profile disks - you can put these on a share and the user profiles will reside on separate virtual disks good when you have several RDS computers
will you be connecting from outside your network - install RDS gateway do not use web broker or connection broker directly to the internet (do not forward port 3389 or try to hide it by changing the port)
personal virtual machines (requires hyper-v role)
remote desktop has the lowest cpu/memory/disk footprint and it requires more hardware resources as you use different versions.
https://learn.microsoft.com/en-us/troubleshoot/windows-server/remote/install-rds-host-role-service-without-connection-broker

if you prefer here's a decent video https://youtu.be/ZVpTcWw7bKE

It is spot on david Johnson answer. 

The main question ask is how many users your RDS are designing for, and what is the "usage pattern" you are anticipating. 

what is the concurrent user at anytime of the environment you anticipating etc. 

All of these are valid questions before you go in for a design (either scale up or scale out OR whether RDS is the right solution) 

Hi Jian,

Can you please attach a questionnaire with the right valid questions for a great design?

Thank you in advance