Forum Discussion
Mixed licensing for WVD?
Windows Virtual Desktop (WVD) is a combination of licensing entitlements (e.g free Windows 7 ESU) and net-new technology which includes the management plane featuring things like AAD support, reverse connect, broker, gateway. licensing etc.
All of this is included with Windows 10 Enterprise E3 Per User” licenses or better (e.g. Windows 10 Enterprise E5 or Microsoft 365 E3, E5, F1, or Business) or RDS CALs.
From that point on, WVD supports multiple operating systems as RDSH including Windows Client and Windows Server. You will need Per User Windows licenses for a client OS and RDS CALs for a Server OS.
Hope this clarifies.
Please may I also ask for clarification?
We are a non-profit and are hugely grateful for the help Microsoft give us with our Charity licences.
Currently we have a:
- an on prem Window Server 2012 using AD sync
- a Azure Windows 2016 instance that our few users access.
- E2 Licences for 365
- Windows Remote Desktop Services - User CAL's
BUT we only have 8 users - so this is rather cumbersome.
So rather than unnecessarily messing with a server I wondered if I can use our existing E3 or using our Windows Remote Desktop Services - User CALto get access to WVD and make our live simpler?
This would be the case for many non-profits that want to keep life simpler.
Many thanks for your suggestions!
- PieterWiglevenJun 24, 2019Former EmployeeCould you help me understand the following: - What exact licenses do you have, Windows, Office and/or M365? - Is the Windows 2016 instance running in Azure?
- BuckleberyJun 24, 2019Copper Contributor
Hi Pieter,
Thank you for your response. Detail below.
As a non-profit we have been given
- Office 365 E2
- Microsoft Office Professional Plus 2016
- Windows 10 Enterprise
- Windows 10 Pro
On Prem: Windows Server 2012 Standard
10 Remote Desktop Licence Windows Server - Device CAL
Open License Details : 87101258 Our Windows Server 2016 is an Azure instance.
Please let m,e know if you need anything else to clarify our bets path to using in the WVD in New Zealand! I think it would be so much simpler.
Kind Regards
Ian
- PieterWiglevenJun 26, 2019Former EmployeeIt might be good to wait until we have rolled-out our management plane to New Zealand and we announced AAD support. The first will make sure the traffic isn't routed via the US and enhance performance. The second will remove the requirement for AD in Azure saving costs. It's hard to give timeliness as we are in planning phase but I'm personally expecting somewhere Q1 of next calendar year. Until that, the existing setup is probably best.