Learning has never been so easy!
- Virtual Machine Platform Windows
- Enable Virtual Machine Windows 10
- Virtual Machine Windows 10
- Microsoft Windows Virtual Machine
- Windows 7 Virtual Machine Download
- Microsoft Windows Xp Virtual Machine
There have been some changes to the licensing model for licensing Windows 10 for use in a virtualized environment (aka VDI or virtual desktop infrastructure) since Windows 10 first released. The updates include incorporate the new per-user licensing options and the options to have your VMs hosted by a 3rd party hosting provider or in Azure.
It’s with that in mind that I’m updating my licensing how-to article from 2 years ago (Licensing Windows 10 with virtualization technologies) to incorporate these changes.
6 Steps total
- We currently package our virtual machines for four different virtualization software options: VMWare, Hyper-V, VirtualBox, and Parallels. Windows 10 Enterprise - 20 GB download This VM will expire on 3/14/21.
- The virtual machine boots into setup and you can walk through the installation like you would on a physical computer. Note: Unless you're running a volume-licensed version of Windows, you need a separate license for Windows running inside a virtual machine. The virtual machine's.
- Test IE11 and Microsoft Edge Legacy using free Windows 10 virtual machines you download and manage locally Select a download Virtual Machines Select one IE8 on Win7 (x86) IE9 on Win7 (x86).
- Windows Virtual PC is the latest Microsoft virtualization technology. You can use it to run more than one operating system at the same time on one computer, and to run many productivity applications on a virtual Windows environment, with a single click, directly from a computer running Windows 7.
Aug 13, 2019 Microsoft has said previously that it will “freeze” the state of the virtual machine, archive it, and bring it up when you launch Windows Sandbox again—basically, everything should launch.
Step 1: What’s new with licensing Windows 10 in a virtualized environment?
Web browser for laptop free download. Traditionally there were only per-device licensing options to license Windows 10 in a virtualized environment, until now. Volume Licensing now includes a per-user license option with option of having your Windows 10 VM hosted on your behalf both on-prem or in the cloud. The Microsoft Cloud Provider (CSP) agreement now includes a Windows 10 per-user license option with virtualization use rights.
With the Windows per-user licensing options in both Volume Licensing and CSP, you can now also have a “qualified multitenant hosting provider” host your Windows 10 virtual machines on your behalf. This means your Windows 10 VMs can be hosted on Azure or by a qualified 3rd party on your behalf.
Step 2: Do’s and don’ts of virtualization licensing
Did you know that only the primary user of the Windows licensed device is licensed to remotely access his/her PC? It’s true, and while technically other users could remote into said device, it doesn’t mean they’re licensed to do so.
Regardless of the virtualization technology being used to virtualize and deliver Windows 10 to your client device (i.e. VMware, Citrix, Microsoft RDS), the licensing is the same for Windows 10. License users or their devices for virtualization access.
Do not license your server hardware or each Windows 10 VM (instance).
Do license your users or their primary device for virtualization use rights (access).
Do not use Retail, OEM or the Windows 10 Pro Volume License Upgrade to license the access of a Windows 10 VM or instance (i.e. VDI). The OEM/Retail/Volume License Upgrades do not permit remote use rights from a shared device (AKA server). Remember, only the single primary user of a Windows licensed device may remotely access said device.
Do license your users or their primary work device for the Windows 10 Enterprise E3/E5 OR Windows Virtual Desktop Access (VDA). License virtualization use rights either per-device or per-user license to allow remote access of a Windows 10 in a VM remotely from a server.
Step 3: Start with these discovery questions
I’ve tried to simplify the “how-to” of licensing Windows 10 for use in a VDI environment by giving you five simple questions about the device and VM location to determine which license is the best for you.
1. Accessing device –
1a. Is the device a work or personal device?
1b. What OS is installed on the device?
1c. Is there a primary user of the device?
1a. Is the device a work or personal device?
1b. What OS is installed on the device?
1c. Is there a primary user of the device?
2. VM –
2a. Where will the VM will be hosted or accessed from? (locally on device, server based, cloud i.e. Azure, or QMTH*)?
*QMTH = Qualified MultiTenant Hoster
2b. What Windows instance do you require? (i.e. Windows 7/8.1/10 Pro/Ent?)
2a. Where will the VM will be hosted or accessed from? (locally on device, server based, cloud i.e. Azure, or QMTH*)?
*QMTH = Qualified MultiTenant Hoster
2b. What Windows instance do you require? (i.e. Windows 7/8.1/10 Pro/Ent?)
The answers to the above questions will lead you towards which licensing option is best for you.
Virtual Machine Platform Windows
Step 4: Option 1 – Per Device with Volume Licensing
Windows per-device licenses through Microsoft Volume Licensing include virtualization rights for dedicated hardware (both on-premises or through a qualified third-party service provider).
The Windows 10 per-device virtualization licensing options are:
1) Windows 10 Enterprise E3 or E5 per device; OR
2) Microsoft 365 Enterprise E3 or E5 per device; OR
3) Windows VDA E3 or E5 per device
1) Windows 10 Enterprise E3 or E5 per device; OR
2) Microsoft 365 Enterprise E3 or E5 per device; OR
3) Windows VDA E3 or E5 per device
Windows 10 Enterprise E3/E5 per-device is the right option if ALL of the following apply:
• The device is licensed for Windows 10 Pro, Enterprise, or Education; Windows 8/8.1 Pro or Enterprise; or Windows 7 Professional or Enterprise AND
• The device is a work device
• The device is licensed for Windows 10 Pro, Enterprise, or Education; Windows 8/8.1 Pro or Enterprise; or Windows 7 Professional or Enterprise AND
• The device is a work device
Windows VDA E3/E5 per-device is the right option if either ONE of the following applies:
• The device is not licensed with a “qualifying OS”
• The user does NOT have a primary work device (BYOD)
• The device is not licensed with a “qualifying OS”
• The user does NOT have a primary work device (BYOD)
Windows 10 Enterprise E3/E5 per device and Windows VDA E3 per device are available via Microsoft Open Value, MPSA & EA agreements.
Step 5: Option 2 – Per User with Volume Licensing
Enable Virtual Machine Windows 10
Windows per User licenses through Microsoft Volume Licensing include virtualization rights for Windows 10 on dedicated hardware (both on-premises or through a qualified third-party service provider). Windows per User now also includes Windows 10 virtualization rights for Microsoft Azure and/or third-party hosting in a multitenant environment by an Authorized QMTH Partner.
The Windows 10 per-user virtualization licensing options are:
1) Windows 10 Enterprise E3 or E5 per-user; OR
2) Microsoft 365 Enterprise E3 or E5 per-user; OR
3) Windows VDA E3 or E5 per-user Buy adobe premiere pro cs6 windows.
1) Windows 10 Enterprise E3 or E5 per-user; OR
2) Microsoft 365 Enterprise E3 or E5 per-user; OR
3) Windows VDA E3 or E5 per-user Buy adobe premiere pro cs6 windows.
Virtual Machine Windows 10
![Windows Windows](https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/media/vmgallery.png)
Microsoft Windows Virtual Machine
Windows 10 Enterprise E3/E5 per-user is the right option if ALL of the following apply:
• The user is the primary user of at least one device licensed for Windows 10 Pro, Enterprise, or Education; Windows 8/8.1 Pro or Enterprise; or Windows 7 Professional or Enterprise AND
• The device is the user’s primary work device AND
• The device is not already covered by Windows 10 Enterprise or Windows VDA. *If the device is already licensed for Windows VDA or SA per-device, you can license Windows per-User with the add-on Windows per-user license.
• The user is the primary user of at least one device licensed for Windows 10 Pro, Enterprise, or Education; Windows 8/8.1 Pro or Enterprise; or Windows 7 Professional or Enterprise AND
• The device is the user’s primary work device AND
• The device is not already covered by Windows 10 Enterprise or Windows VDA. *If the device is already licensed for Windows VDA or SA per-device, you can license Windows per-User with the add-on Windows per-user license.
Windows 7 Virtual Machine Download
Windows VDA Per User is the right option if either ONE of the following applies:
• The user is NOT the primary user of at least one device licensed with a “qualifying OS.”
• The user does NOT have a primary work device.
• The user is NOT the primary user of at least one device licensed with a “qualifying OS.”
• The user does NOT have a primary work device.
*Note Windows VDA per-user is the least restrictive option. If you were to license every user with Windows VDA Per User, every user would have access to Windows Enterprise without the need to track the operating system license(s) on the user’s device(s) (except for devices on which you install the software locally).
Windows 10 Enterprise E3/E5 per user and Windows VDA E3/E5 per user are available via Microsoft MPSA & EA agreements.
Step 6: Option 3 – Per-User with Cloud Solution Agreement (CSP)
The Microsoft Cloud Agreement offers a Windows subscription license includes virtualization rights for Windows 10 Creators Update or later Semi-Annual Channel release - hosted on Microsoft Azure and/or third-party in a multitenant environment by an Authorized QMTH Partner
The Windows 10 Cloud Agreement per-user virtualization licensing options are:
1) Windows 10 Enterprise E3 or E5 - with VDI rights; OR
2) Microsoft 365 Enterprise E3 or E5 per user; OR
3) Windows VDA E3 per user
1) Windows 10 Enterprise E3 or E5 - with VDI rights; OR
2) Microsoft 365 Enterprise E3 or E5 per user; OR
3) Windows VDA E3 per user
Microsoft Windows Xp Virtual Machine
Windows 10 Enterprise E3/E5 with VDI rights via Cloud Agreement is the right option if ALL of the following apply:
• The user is the primary user of at least one device licensed for Windows 7/8.1/10 Pro; AND
• The device is the user’s primary work device; AND
• The VM is Windows 10 Creators Update or later Semi-Annual Channel release
• The user is the primary user of at least one device licensed for Windows 7/8.1/10 Pro; AND
• The device is the user’s primary work device; AND
• The VM is Windows 10 Creators Update or later Semi-Annual Channel release
Windows VDA Per User is the right option if either ONE of the following applies:
• The user is NOT the primary user of at least one device licensed with a “qualifying OS”; OR
• The user does NOT have a primary work device
• The user is NOT the primary user of at least one device licensed with a “qualifying OS”; OR
• The user does NOT have a primary work device
![Microsoft windows virtual machine Microsoft windows virtual machine](https://docs.microsoft.com/pt-br/virtualization/hyper-v-on-windows/about/media/hypervnesting.png)
Windows 10 Enterprise E3/E5 per user and Windows VDA E3 per user are available via Microsoft Cloud Solution (CSP) Agreements.
Published: Sep 11, 2017 · Last Updated: Sep 14, 2017
References
- Licensing Windows 10 with virtualization technologies - How-To (old 2015 version)
- Licensing Windows Server for use with virtualization technologies
- Multitenant Hosting Rights for Windows 10
- New Windows 10 upgrade benefits for Windows Cloud Subscriptions in CSP
- Windows 10 Licensing
61 Comments
- TabascoDuluthG33k Sep 11, 2017 at 03:26pmDon't forget to send this to your favorite person on LinkedIn. So he can update his awesome tutorial.But on a serious note another great how-to packed full of information for the wonderful wold of Microsoft Licensing.
- Ghost ChiliChris (Microsoft) Sep 11, 2017 at 03:29pm@DuluthG33k - HAHAHA right? Thankfully that post was taken down off his profile.Thanks for the feedback on this. I need google chrome in english. It took a few weeks to complete.
- TabascoDuluthG33k Sep 11, 2017 at 03:33pmI hadn't checked lately. Glad to hear that LinkedIn took the issue seriously and did something about it.
- Chipotletlong_vna Sep 12, 2017 at 04:25pmThanks for the how-to, great write up! I wish Microsoft would just make licensing simple but wish in one hand and install Linux with the other I guess.
- Anaheimjj99 Sep 12, 2017 at 05:06pm'Did you know that only the primary user of the Windows licensed device is licensed to remotely access his/her PC? It’s true, and while technically other users could remote into said device, it doesn’t mean they’re licensed to do so.'Chris, I think that should be clarified a little bit.From the 'Microsoft Product Terms' (Sept. '17):
'4. Remote use is permitted for the Primary User of the Licensed Device ***and for any other user from another Licensed Device or a Windows VDA Licensed Device***' - emphasis mine.If other users have their own licensed Windows box, they can also remote into other machines. A scenario for this would be five people have their own licensed, physical workstations, but they each share a single remote workstation as a jumphost/management station. - Ghost ChiliChris (Microsoft) Sep 12, 2017 at 05:14pm@jj99 - that is the correct part from the Product Terms to quote, but you've interpreted them a bit incorrectly.
'from another Licensed Device' means a device licensed with Windows SA (virt use rights) or Windows VDA. The OEM/FPP/VL Upgrade license permits only the primary user to remotely access the licensed device, not any Windows OS licensed device.
Using my examples: If device Z was to remotely access device X, either the primary user of device Z or device Z itself would need to be licensed for Windows SA (virt use rights) or Windows VDA. - Thai PepperDavid Auth Sep 12, 2017 at 05:32pmFavorited, for future reference! I'd spice it if I could, so in lieu of that, here's a +1?
- SerranoDanielgingerich Sep 12, 2017 at 05:34pmI have seen many attempts at virtualization of use resources over the year, and each has had major problems that keeps most companies from using it effectively. While it look great in theory, with many theoretically money saving aspects, I have yet to find a company that actually saved money with it in actual practice. It winds up more of a headache for the admins, and while cutting time for desktop support, it is more than made up in admin time and costs.
- Chipotlemichaelmac Sep 12, 2017 at 05:38pmThat 'Qualified MultiTenant Hoster' bit..does that mean that Microsoft tells me who I can and can not have host my Windows 10 VDIs?
- Ghost ChiliChris (Microsoft) Sep 12, 2017 at 05:44pm@michaelmac - it says if you want to have your Windows 10 VDI hosted by a 3rd party, in a multitenant (shared resources) scenario - yes that hoster needs to be 'qualified' hosting provider. More info here: https://www.microsoft.com/en-us/CloudandHosting/licensing_sca.aspx
- Anaheimjj99 Sep 12, 2017 at 05:56pm@chris-microsoft, Retail EULA states:
'(v) Remote access. No more than once every 90 days, you may designate a single user who physically uses the licensed device as the licensed user. The licensed user may access the licensed device from another device using remote access technologies. ***Other users, at different times, may access the licensed device from another device using remote access technologies, but only on devices separately licensed to run the same or higher edition of this software.***' - emphasis mine -- https://www.microsoft.com/en-us/Useterms/Retail/Windows/10/UseTerms_Retail_Windows_10_English.htmI think that makes it pretty clear other users can remote into it with just Retail Win10 licensing, etc (which is what most people have if they upgraded from Win7+). - ChipotleBF15 Sep 12, 2017 at 05:59pmso with per user, how many devices can the user use? I have some people that sign into 3 or 4 different machines, like conference room machines and stuff.
- Datilcomputerdave Sep 12, 2017 at 06:07pmWe use Intune with SA here. Does that include VDI rights? I feel like that was something we read when we first started using it.
- Ghost ChiliChris (Microsoft) Sep 12, 2017 at 06:25pm@jj99 - I get what you're saying but I would not make the assumption that everyone is on the same version they're remotely accessing.
- Ghost ChiliChris (Microsoft) Sep 12, 2017 at 06:26pm@BF15 - with CSP per-User it's 5 devices. With VL per-User I dont know of a limit
- prev
- 1
- 2
- 3
- 4
- 5
- next