Microsoft would love to see you migrate to Windows Virtual Desktop (which is also multi-session), but that is only available on Azure. If you have Office 365 licensing or Office 2016 perpetual, you are forced to stay on Windows Server 2016 or move to VDI. In my opinion, you would need to have a very good reason to use Windows Server 2019 instead of 2016 for RDSH. Office versionĪs you can see, only Office 2019 perpetual licensing is supported on Windows Server 2019.
In the following table you can see the support of the different Office versions on Windows Server 20. If you are providing access to Microsoft Office applications through RDSH, you must be aware of the support status of Microsoft Office on specific operating system versions. One thing you don’t want is a lower user density when changing the operating system of the RDSH servers (unless it will offer new functionality or offer a better user experience, then you might accept the lower user density). Sharing the operating system with multiple users allows you to host more users per physical server than you could host with VDI.
One of the reasons to choose RDSH over VDI is the higher user density you (should) get. You can use RDSH in the plain vanilla Microsoft variant or use for example Citrix Virtual Apps and Desktops (formally known as XenApp), VMware Horizon, Parallels Remote Application Server or another product on top of RDSH. RDSH, or Server Based Computing (SBC) as we used to call it, can be used in different flavors. There are other considerations as well, application compatibility and support for example, but this research will focus on the impact on performance and capacity. If you are thinking about updating your Remote Desktop Session Host (RDSH) environment from Windows Server 2016 to Windows Server 2019, one of the considerations is the impact this change has on user density and performance.
0 kommentar(er)
