On Wed, Sep 18, 2019 at 7:12 AM James Allsopp
<[email protected]> wrote:

> Hi,
> I was wondering what Windows 10 licences people were using for Guacamole?
> We want to have users logging in one at a time, but have the windows 10
> machine installed as a VM on a VMware Esxi server, with Guacamole
> connecting to the server via RDP. We're planning on buying retail Windows
> licences.
>
> Section 2c v.) of the Windows Licence (
> https://www.microsoft.com/en-us/Useterms/Retail/Windows/10/Useterms_Retail_Windows_10_English.htm
>  )
> seems to prohibit this;
> * install the software on a server and allow users to access it remotely,
> or install the software on a device for use only by remote users;  *
>
> This seems to contradict 2d v.)
> *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.  *
>
> But does that mean that it's only within licence terms to access the
> machines from a Windows 10 Home pc?
>

It's been a while since I dealt directly with Windows workstation
licensing, but my recollection of the license terms are as follows:
- You can use the remote desktop feature of a Windows workstation on a
standard PC to access that system from a Windows edition of equal or
greater (e.g. Pro -> Pro, Enterprise -> Pro, etc. - 2d).
- You *cannot* run any edition of Windows lower than Enterprise on a server
to use in a "VDI"-type scenario.  This means using Retail edition for
VDI-like functionality is a no-go in Microsoft licensing terms.
- Not only do you need Enterprise Edition or higher (I think Ultimate is
higher), you also need to maintain Software Assurance on the licenses you
use for VDI.

Again, that's my recollection.  I'm also not sure how much of that guidance
was "reseller guidance" (someone who's in it for the $$) and how much of
that was honest legal guidance (if you do this, you're actually in
violation of the EULA).  I'd recommend you consult someone intimately
familiar with Microsoft licensing, but who's not in it to get your money
(good luck finding said person).

-Nick

Reply via email to