1 Reply

  • You are very much misunderstanding several things about what a server is and what a workstation is. 

    What you are linking is what Windows 10 is and is not allowed to perform functions under conditions. Simply remoting to an operating system (which is what you're really talking about) does not then define the destination system as a server. A server, by definition, is fairly specific. It serves specific functions to one or more users over a local or remote network; examples may be file shares, web services, print services, etc. A workstation, either physical or remote, is one that performs complex tasks for only a single user. 

    The Windows EULA that you have referenced states that you cannot use the Windows 10 operating system as a server function. Examples I've seen are organizations using a Windows 10/11 OS to map and share out drives on the network as a file server, virtualize it and use it as a print server, or install third-party services on the desktop OS and use it as a VPN aggregator for multiple users. All of these functions fall under services not intended for a workstation to perform and thereby violate the EULA.

    You are misinterpreting what does and does not violate the agreement. Remote connection companies (such as ones you've listed above) are not violating the EULA simply by producing software that allows someone to remotely control the destination system; to expand on that, it doesn't even provide a desktop to the source, it simply let's you control it, you still have to log in and be provided your own desktop by the remote system (which would require certain CALs/VDA/etc, completely separate of the remote control software).

    Pepper graySpice (6) flagReport
    1 found this helpful thumb_up thumb_down

Read these next...