Remember to configure your licenses per user and not per device.Īs a temporary alternative.
#Ncomputing vspace alternative how to#
We have many articles written on our knowedgebase on how to configure a licensing server for 2008 R2, 2012 and 2016. Once you deploy on a Server OS, you will need to configure your licensing server. 20 R2 will also have similar configurations to enable desktop experience mode and show at the clients a Windows 8 or 7 desktop respectively.
#Ncomputing vspace alternative windows 10#
For example, if you desire a Windows 10 look and feel for your users, we would recommend using Server 2016, so you can enable a desktop experience mode that will deliver a native Windows 10 look and feel. This will enable you to comply with Microsoft’s licensing requirements and will allow your multiuser sessions freely.Įnsure that you are using a compatible Server operating system with our vSpace products seeing our vSpace Operating System Support Matrix.Īs an additional benefit of using Server OS, our UXP protocol will utilize some of the APIs within the Server Platform. If multiuser sessions are needed, vSpace will need to be installed on a Server OS, like 2008 R2, 2012, or 2016. Our End User Licensing Agreement assumes that when you are installing vSpace for multiuser purposes, you are installing on a Server Operating System. In addition, our UXP protocol does not change performance or alter licensing scheme on Microsoft products. If multiuser sessions are attempted, these will be rejected as a security measure. Under this condition, the operating system will only allow one session on a thin client, which is perfectly suitable for VDI deployment scenarios where a single session is accessed per operating system. Windows 7, Windows 8.1, Windows 10) a warning error may be displayed when attempting to login: “Select a user to disconnect so that you can sign in.
0 kommentar(er)
