Jun 20 2019 01:10 AM
Jun 20 2019 01:10 AM
As far as I understand there are two ways of licensing a WVD user, either giving the user a M365 license or pointing the Windows 10 multisession host at a TS licensing host the old-fashioned way. Right?
How about mixed mode, where some users have the M365 license and others only a O365 E3 license?
Will using a M365 license get rid of the "host not licensed" message?
I really would like documentation that explains how this scenario works.
Jun 20 2019 10:26 AM
Jun 20 2019 11:00 AM
So for my O365 E3 users I need to configure a TS licensing server on the Windows multisession host, which makes good sense.
And on this same host a Windows E3 user will not occupy a TS license?
Just want to be sure how this mixed license scenario works. Thanks.
Jun 20 2019 11:04 AM
Jun 20 2019 11:35 AM
So TS/RDS CALs is not an option? Now I am confused.
According to your blog “Getting started with Windows Virtual Desktop”:
Organizations 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 can use Windows Virtual Desktop for no additional charge apart from Azure compute/storage and network usage billing
In my POC tenant I have Windows 10, Mac and iOS endpoints. Some of my customers have M365 licenses, most have O365 and then some have mixed.
Jun 20 2019 11:53 AM - edited Jun 20 2019 12:18 PM
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.
Jun 23 2019 05:45 PM
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:
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!
Jun 24 2019 09:46 AM
Jun 24 2019 02:14 PM
Thank you for your response. Detail below.
As a non-profit we have been given
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.
Jun 26 2019 09:57 AM
Jan 27 2020 02:41 AM
Hi @PieterWigleven Pieter Wigleven (WINDOWS)
I have a customer whose previous environment is in RDS and now he is trying out WVD. The customer already has an O365 E3 license and i have deployed a WVD environment for the customer using ADDS, so just wanted to confirm the customer has E3 license, so will he will be still charged for the windows enterprise multi-session that i have deployed for him. Do i need to enable any client OS Licensing on WVD?And if so how am i suppose to do it?
Jan 27 2020 01:50 PM
Jan 29 2020 08:59 AM
@sarahpotrick2573 as M365 E3 contains both "Windows E3 Per User" and "Office E3 Per User" you are all good assuming you are providing access to a Client SKU.
You can run the VMs against linux rates (preventing paying double) using the information provided here
Feb 04 2020 10:45 AM
Hi @PieterWigleven , I just clear my doubts. I've read the previous questions and still don't have sure on one thing.
If I deploy my Hostpools using the Azure market place using Win 10 multisession . Am I good to use with as many users i Want? Or will I be charged for the infrastructure plus the total users that uses WVD?
Feb 07 2020 10:32 AM
@sarahpotrick2573 Yes, with the note that WVD supports multiple operating systems and depending what you spin up, the requirements are slightly different.
In essence it's the same as on-premises:
- If you spin up a Windows Server, it requires a RDS CAL for the user that connects.
- If you spin up a Windows client OS (including multi-session), it requires the user has a Windows E3 Per User license.
For Office 365 ProPlus, you need an appropriate license just like on-premises: either Office E3 or higher.
Mar 27 2020 09:26 AM
"For Office 365 ProPlus, you need an appropriate license just like on-premises: either Office E3 or higher" or just an Office365 ProPlus licence ;)
Do you know if Office Standard runs in WVD (presume it does) and would it be licenced in same way as standard VDI solutions i.e. need Software Assurance or SPLA licence?