![]() ![]() While this may seem like a good idea, it's not best practice to do so. You could do an all in one RDS Role setup: We don't do standalone and have not done so in years, though as a caveat we don't work with high transaction SQL where bare metal is preferred. RD Physical Server or Virtualization HostWe virtualize. The Internet pipe needs to be a consideration here even with 10 users. Microsoft's CrEdge is probably one of the better ones for management and user resource usage.īandwidth and video quality will be an issue. RDS EnvironmentBrowsers are killers in an RDS Session Host shared environment. UDP 3391 needs to be allowed inbound via the WAN to the RD Gateway and that there is a firewall exception in place on the Session Hosts.Īlso, port UDP 3391 gives a performance boost to the RDP stream for all other RD Clients. MAC and Windows Modern RDCIt is important to note that when the MAC or Modern Remote Desktop Client (RDC) is in use that port The cost will be as good or better than a dedicated thin client with all of the Windows goodness for driver compatibility and overall management experience. Thin ClientI suggest an Intel NUC with i3 processor, Windows 10 Pro for an OS, and the appropriate Group Policy structure to manage them down to thin client status. * User Usage: Browsing, Zoom, Office Apps So, the following is something to keep in mind: ![]() IntroductionThis article stems from a question on this forum. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |