I have a requirement to deploy a web application that will handle credential injection when users attempt to log on to the vCenter console. From an RDS perspective, what would be the recommended approach? Specifically, can I leverage my existing Brokers to publish this application, given that I currently support approximately 70 concurrent RDP and SSH sessions distributed across three brokers? Or is it strongly advised to provision dedicated RDS servers for this purpose?!--endfragment>!--startfragment>
Solved
Web Application - Vcenter
Best answer by jchandler
Hello
Using Resource Brokers as RDS Session Hosts is possible, however this is not considered best practice.
While Microsoft Remote Desktop Services can technically be installed on a Resource Broker, it is generally not recommended as it mixes security zones on a single host. This can introduce additional risk and operational complexity.
If RDS were installed on a Resource Broker regardless, close monitoring would be required to ensure the broker has sufficient CPU, memory, and storage resources available to support both brokering functions and Remote Desktop workloads without performance degradation.
A quick online search returned the following general RDS Session Host sizing guidelines, however Microsoft documentation should always be consulted to confirm the actual requirements for your environment:
- Light User: 2 vCPUs, 8 GB RAM, 32 GB storage
- Medium User: 4 vCPUs, 16 GB RAM, 32 GB storage
- Heavy User: 8 vCPUs, 32 GB RAM, 32 GB storage
Regards,
John
Hello
Using Resource Brokers as RDS Session Hosts is possible, however this is not considered best practice.
While Microsoft Remote Desktop Services can technically be installed on a Resource Broker, it is generally not recommended as it mixes security zones on a single host. This can introduce additional risk and operational complexity.
If RDS were installed on a Resource Broker regardless, close monitoring would be required to ensure the broker has sufficient CPU, memory, and storage resources available to support both brokering functions and Remote Desktop workloads without performance degradation.
A quick online search returned the following general RDS Session Host sizing guidelines, however Microsoft documentation should always be consulted to confirm the actual requirements for your environment:
- Light User: 2 vCPUs, 8 GB RAM, 32 GB storage
- Medium User: 4 vCPUs, 16 GB RAM, 32 GB storage
- Heavy User: 8 vCPUs, 32 GB RAM, 32 GB storage
Regards,
John
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.