Home

Mixed licensing for WVD?

%3CLINGO-SUB%20id%3D%22lingo-sub-709647%22%20slang%3D%22en-US%22%3EMixed%20licensing%20for%20WVD%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-709647%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20far%20as%20I%20understand%20there%20are%20two%20ways%20of%20licensing%20a%20WVD%20user%2C%20either%20giving%20the%20user%20a%20M365%20license%20or%20pointing%20the%20Windows%2010%20multisession%20host%20at%20a%20TS%20licensing%20host%20the%20old-fashioned%20way.%20Right%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20about%20mixed%20mode%2C%20where%20some%20users%20have%20the%20M365%20license%20and%20others%20only%20a%20O365%20E3%20license%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWill%20using%20a%20M365%20license%20get%20rid%20of%20the%20%22host%20not%20licensed%22%20message%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20really%26nbsp%3B%20would%20like%20documentation%20that%20explains%20how%20this%20scenario%20works.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-711499%22%20slang%3D%22en-US%22%3ERe%3A%20Mixed%20licensing%20for%20WVD%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-711499%22%20slang%3D%22en-US%22%3EHi%20Oletho%2C%20It's%20very%20similar%20to%20how%20licensing%20works%20on-premises.%20If%20you%20are%20using%20Windows%20Server%20RDSH%2C%20you%20need%20a%20RDS%20CAL%20for%20every%20user%20that%20connects.%20If%20you%20are%20using%20a%20Windows%20Client%20OS%2C%20you%20are%20covered%20with%20your%20Windows%20E3%20(or%20better)%20Per%20User%20licensing.%20O365%20licensing%20is%20not%20sufficient%20for%20Windows%2010%20multi-session%2C%20it%20needs%20to%20be%20for%20a%20Windows%20OS.%20Since%2C%20from%20a%20licensing%20perspective%2C%20Windows%2010%20Multi-session%20is%20considered%20a%20client%20OS%20-%20you%20don't%20need%20an%20RDS%20CAL%20and%20there%20is%20no%20need%20to%20configure%20a%20TS%20licensing%20host.%20Now%20you%20might%20be%20getting%20pop-ups%20about%20a%20grace%20period%2C%20that's%20something%20we%20are%20fixing.%20For%201903%20builds%20that%20should%20go%20away%20in%20a%20couple%20of%20weeks.%20For%201809%20builds%20it%20will%20take%20longer%20and%20the%20best%20workaround%20is%20using%20the%20latest%20image%20from%20the%20gallery%20which%20has%20a%20grace%20period%20of%20800%20days.%20Thanks%2C%20Pieter%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-711612%22%20slang%3D%22en-US%22%3ERe%3A%20Mixed%20licensing%20for%20WVD%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-711612%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20for%20my%20O365%20E3%20users%20I%20need%20to%20configure%20a%20TS%20licensing%20server%20on%20the%20Windows%20multisession%20host%2C%20which%20makes%20good%20sense.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20on%20this%20same%20host%20a%20Windows%20E3%20user%20will%20not%20occupy%20a%20TS%20license%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20want%20to%20be%20sure%20how%20this%20mixed%20license%20scenario%20works.%20Thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-711632%22%20slang%3D%22en-US%22%3ERe%3A%20Mixed%20licensing%20for%20WVD%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-711632%22%20slang%3D%22en-US%22%3EYou%20cannot%20use%20Windows%2010%20Enterprise%20multi-session%20if%20a%20user%20is%20only%20licensed%20for%20Office.%20They%20need%20to%20be%20licensed%20for%20Windows.%20Either%20through%20E3%2C%20E5%2C%20Business%2C%20F1%20or%20M365%20E3%2FE5%20Per%20User.%20What%20endpoints%20are%20you%20using%3F%20Is%20that%20Windows%3F%20If%20so%2C%20switching%20to%20Windows%20Per%20User%20licensing%20for%20everyone%20might%20be%20the%20best%20option.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-711747%22%20slang%3D%22en-US%22%3ERe%3A%20Mixed%20licensing%20for%20WVD%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-711747%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20TS%2FRDS%20CALs%20is%20not%20an%20option%3F%20Now%20I%20am%20confused.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAccording%20to%20your%20blog%20%E2%80%9CGetting%20started%20with%20Windows%20Virtual%20Desktop%E2%80%9D%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CI%3EOrganizations%20with%20%E2%80%9CWindows%2010%20Enterprise%20E3%20Per%20User%E2%80%9D%20licenses%20or%20better%20(e.g.%20Windows%2010%20Enterprise%20E5%20or%20Microsoft%20365%20E3%2C%20E5%2C%20F1%2C%20or%20Business)%20%3CSTRONG%3Eor%20RDS%20CALs%3C%2FSTRONG%3E%20can%20use%20Windows%20Virtual%20Desktop%20for%20no%20additional%20charge%20apart%20from%20Azure%20compute%2Fstorage%20and%20network%20usage%20billing%3C%2FI%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20my%20POC%20tenant%20I%20have%20Windows%2010%2C%20Mac%20and%20iOS%20endpoints.%26nbsp%3BSome%20of%20my%20customers%20have%20M365%20licenses%2C%20most%20have%20O365%20and%20then%20some%20have%20mixed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-711885%22%20slang%3D%22en-US%22%3ERe%3A%20Mixed%20licensing%20for%20WVD%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-711885%22%20slang%3D%22en-US%22%3EAh%2C%20sure%20got%20that%20wrong.%3CBR%20%2F%3E%3CBR%20%2F%3EYes%2C%20this%20clarifies.%20Thanks!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-711830%22%20slang%3D%22en-US%22%3ERe%3A%20Mixed%20licensing%20for%20WVD%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-711830%22%20slang%3D%22en-US%22%3E%3CP%3EWindows%20Virtual%20Desktop%20(WVD)%20is%20a%20combination%20of%20licensing%20entitlements%20(e.g%20free%20Windows%207%20ESU)%20and%20net-new%20technology%20which%20includes%20the%20management%20plane%20featuring%20things%20like%20AAD%20support%2C%20reverse%20connect%2C%20broker%2C%20gateway.%20licensing%20etc.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAll%20of%20this%20is%20included%20with%20Windows%2010%20Enterprise%20E3%20Per%20User%E2%80%9D%20licenses%20or%20better%20(e.g.%20Windows%2010%20Enterprise%20E5%20or%20Microsoft%20365%20E3%2C%20E5%2C%20F1%2C%20or%20Business)%20or%20RDS%20CALs.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFrom%20that%20point%20on%2C%20WVD%20supports%20multiple%20operating%20systems%20as%20RDSH%20including%20Windows%20Client%20and%20Windows%20Server.%20You%20will%20need%20Per%20User%20Windows%20licenses%20for%20a%20client%20OS%20and%20RDS%20CALs%20for%20a%20Server%20OS.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHope%20this%20clarifies.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-715832%22%20slang%3D%22en-US%22%3ERe%3A%20Mixed%20licensing%20for%20WVD%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-715832%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20may%20I%20also%20ask%20for%20clarification%3F%3C%2FP%3E%3CP%3EWe%20are%20a%20non-profit%20and%20are%20hugely%20grateful%20for%20the%20help%20Microsoft%20give%20us%20with%20our%20Charity%20licences.%3C%2FP%3E%3CP%3ECurrently%20we%20have%20a%3A%3C%2FP%3E%3CUL%3E%3CLI%3Ean%20on%20prem%20Window%20Server%202012%20using%20AD%20sync%3C%2FLI%3E%3CLI%3Ea%20Azure%20Windows%202016%20instance%20that%20our%20few%20users%20access.%3C%2FLI%3E%3CLI%3EE2%20Licences%20for%20365%3C%2FLI%3E%3CLI%3E%3CSPAN%3EWindows%20Remote%20Desktop%20Services%20-%20User%20CAL's%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3EBUT%20we%20only%20have%208%20users%20-%20so%20this%20is%20rather%20cumbersome.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20rather%20than%20unnecessarily%20messing%20with%20a%20server%20I%20wondered%20if%20I%20can%20use%20our%20existing%20E3%20or%20using%20our%20%3CSPAN%3EWindows%20Remote%20Desktop%20Services%20-%20User%20CAL%3C%2FSPAN%3E%3CSPAN%3Eto%20get%20access%20to%26nbsp%3B%3C%2FSPAN%3E%26nbsp%3BWVD%26nbsp%3B%20and%20make%20our%20live%20simpler%3F%3C%2FP%3E%3CP%3EThis%20would%20be%20the%20case%20for%20many%20non-profits%20that%20want%20to%20keep%20life%20simpler.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMany%20thanks%20for%20your%20suggestions!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-717662%22%20slang%3D%22en-US%22%3ERe%3A%20Mixed%20licensing%20for%20WVD%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-717662%22%20slang%3D%22en-US%22%3ECould%20you%20help%20me%20understand%20the%20following%3A%20-%20What%20exact%20licenses%20do%20you%20have%2C%20Windows%2C%20Office%20and%2For%20M365%3F%20-%20Is%20the%20Windows%202016%20instance%20running%20in%20Azure%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-718479%22%20slang%3D%22en-US%22%3ERe%3A%20Mixed%20licensing%20for%20WVD%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-718479%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Pieter%2C%3C%2FP%3E%3CP%3EThank%20you%20for%20your%20response.%20Detail%20below.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20a%20non-profit%20we%20have%20been%20given%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3E%3CSPAN%3EOffice%20365%20E2%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EMicrosoft%20Office%20Professional%20Plus%202016%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EWindows%2010%20Enterprise%20%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EWindows%2010%20Pro%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%3CSPAN%3EOn%20Prem%3A%20Windows%26nbsp%3BServer%202012%20Standard%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E10%20Remote%20Desktop%26nbsp%3BLicence%26nbsp%3BWindows%20Server%20-%20Device%20CAL%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CTABLE%20cellspacing%3D%225px%22%20cellpadding%3D%220%22%3E%3CTBODY%3E%3CTR%3E%3CTD%3E%3CSPAN%3EOpen%20License%20Details%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3A%3C%2FTD%3E%3CTD%3E%3CSPAN%3E87101258%3C%2FSPAN%3E%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EOur%20Windows%20Server%202016%20is%20an%20Azure%20instance.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EPlease%3CSPAN%3E%26nbsp%3Blet%20m%2Ce%20know%20if%20you%20need%20anything%26nbsp%3Belse%20to%20clarify%20our%20bets%20path%20to%20using%20in%20the%20WVD%20in%20New%20Zealand!%20I%20think%20it%20would%20be%20so%20much%20simpler.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EKind%20Regards%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EIan%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-722400%22%20slang%3D%22en-US%22%3ERe%3A%20Mixed%20licensing%20for%20WVD%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-722400%22%20slang%3D%22en-US%22%3EIt%20might%20be%20good%20to%20wait%20until%20we%20have%20rolled-out%20our%20management%20plane%20to%20New%20Zealand%20and%20we%20announced%20AAD%20support.%20The%20first%20will%20make%20sure%20the%20traffic%20isn't%20routed%20via%20the%20US%20and%20enhance%20performance.%20The%20second%20will%20remove%20the%20requirement%20for%20AD%20in%20Azure%20saving%20costs.%20It's%20hard%20to%20give%20timeliness%20as%20we%20are%20in%20planning%20phase%20but%20I'm%20personally%20expecting%20somewhere%20Q1%20of%20next%20calendar%20year.%20Until%20that%2C%20the%20existing%20setup%20is%20probably%20best.%3C%2FLINGO-BODY%3E
Oletho
Occasional Contributor

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.

10 Replies
Hi Oletho, It's very similar to how licensing works on-premises. If you are using Windows Server RDSH, you need a RDS CAL for every user that connects. If you are using a Windows Client OS, you are covered with your Windows E3 (or better) Per User licensing. O365 licensing is not sufficient for Windows 10 multi-session, it needs to be for a Windows OS. Since, from a licensing perspective, Windows 10 Multi-session is considered a client OS - you don't need an RDS CAL and there is no need to configure a TS licensing host. Now you might be getting pop-ups about a grace period, that's something we are fixing. For 1903 builds that should go away in a couple of weeks. For 1809 builds it will take longer and the best workaround is using the latest image from the gallery which has a grace period of 800 days. Thanks, Pieter

 

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.

You cannot use Windows 10 Enterprise multi-session if a user is only licensed for Office. They need to be licensed for Windows. Either through E3, E5, Business, F1 or M365 E3/E5 Per User. What endpoints are you using? Is that Windows? If so, switching to Windows Per User licensing for everyone might be the best option.

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.

 

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.

Ah, sure got that wrong.

Yes, this clarifies. Thanks!

 

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!

Could 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?

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

 

It 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.
Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
38 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies