Windows Server 2016 removes the restriction for the number of Connection Brokers you can have in a deployment when using Remote Desktop Session Hosts (RDSH) and Remote Desktop Virtualization Hosts (RDVH) that also run Windows Server 2016. If you are creating a highly available environment, all of your Connection Brokers need to be at the same OS level. Remember that a 2019 license server can process CALs from all previous versions of Windows Server, down to Windows Server 2003.įollow the upgrade order recommended in Upgrading your Remote Desktop Services environment.
If you upgrade your RD Session Host to Windows Server 2019, also upgrade the license server. You can have a collection with Windows Server 2016 Session Hosts and one with Windows Server 2019 Session Hosts. Windows Server 2019 is backward-compatible with these components, which means a Windows Server 2016 or Windows Server 2012 R2 RD Session Host can connect to a 2019 RD Connection Broker, but not the other way around.įor RD Session Hosts - all Session Hosts in a collection need to be at the same level, but you can have multiple collections. Use Windows Server 2019 for your Remote Desktop infrastructure (the Web Access, Gateway, Connection Broker, and license server). Make sure to review the system requirements for Windows Server.
0 kommentar(er)
