Good day,
I currently have a Windows 2008R2 RDS deployment with 5 RDS Session Host virtual servers [Hyper-v] and a single RD Connection Broker and licensing server [User CALs] I am looking to migrate to a Windows 2016 RDS deployment by adding 5 new virtual 2016 RDS Session Host servers as well as two 2016 HA connection brokers. We utilize a VPN so we do not require an RD Gateway or RD Web Access servers. My questions are:
1.] Can I add the two connection brokers while still utilizing the current single 2008R2 connection broker? In other words, will the 2008R2 connection broker coexist with he two new 2016 connection brokers on the same network while I prepare the 2016 environment? I am not looking for interoperability, just coexistence.
2.] Can I install a 2016 licensing server for the RDS CAL's on one of the connection brokers, and will that coexist and play nice with the current 2008R2 licensing server. I am aware that the 2016 Licensing server can host the 2008 CALs, and will probably migrate them to the new server, but wanted to make sure that all will stay good until that migration occurs.
We are basically hoping to spin up these new servers, install the RDS roles and various applications and then switch over to RDS 2016 when the new environment is ready, while maintaining the current RDS 2008R2 production system until all is ready. Any caveats?
Thanks for any help, guidance and experience that can be provided!
- Joe
- Are you smarter than most IT pros? Take the Daily Challenge »
- RDS UPD profiles registry for HKEY_CURRENT_USER\Software\Microsoft\...
- What Cipher suites are used by RDP Enhanced Encryption on Windows s...
- Unable to reconnect to RDP after disconnecting [nor ping it after]
- ROM
- CPU
- RAM
- GPU
3 Replies
FWIW, I recently brought up my first RDS environment on Windows Server 2019.
My AD servers are Windows Server 2019. I built a new Windows Server 2019 to handle RDS including the gateway, licensing and broker components. Plus RDS 2019 user cals.
As my goal was to only provide more than two Remote Desktop sessions on Windows Server 2019 or Windows Server 2012R2 hosts used as IIS web servers, I can state that it all worked for me using Connection profiles. I then tested it on both Windows Server 2019 and Windows Server 2012 R2 hosts and it worked.
I did not have to provide Remote Desktop Web applications, so that is unknown to me.
The answer to both is yes.
They will coexist as you have to tell RD setups where to look for RD connection brokers and License servers.
-
-
-
Quote Post