I'm currently using a Remote Desktop Connection Broker VM that our IT staff connects to. Once logged in, they automatically get dropped onto a management machine session host. However, we've been facing persistent issues with the connection broker, often needing to reboot the VM to restore proper access. I'm curious about how others set up their management machines and whether there's a more efficient way to handle this.
3 Answers
Your architecture seems fine, but it sounds like the connection broker is causing all your headaches. It might be time for some troubleshooting or even a rebuild of that broker. As for what's considered best practice, opinions vary on whether to stick with a setup like yours or opt for dedicated VMs instead.
If you're looking for alternatives, I mostly work with Microsoft cloud solutions these days. A comparable option you might consider is Azure Virtual Desktop—it could simplify your setup.
Your current setup shouldn’t be an issue aside from the connection problems. A solid alternative is implementing a Privileged Access Workstation (PAW) combined with Virtual Desktop Infrastructure (VDI). This way, admins get a dedicated PAW for administration and log into a VDI for their workstation tasks. Check out this link for more insights: [Privileged Access Workstations](https://learn.microsoft.com/en-us/security/privileged-access-workstations/legacy-privileged-access-devices).
Awesome, cheers mate. Appreciate it.