The controlling factor for a machine to read a PHDwin license is the OS and how a user logs in. The fact that the OS is a virtual machine (VM) should not make a difference. Note that standard PHDwin licenses are commonly meant for local machine use where the license and the application resides on the user’s desktop. Alternatively, network license servers are designed for the server application to be stored on the company’s network, while the main application, PHDwin, is stored locally on the user’s machine.

1.If the OS that is running PHDwin as a Server OS and the user is not on the console (i.e. Remote desktop), PHDwin V3 requires a Concurrent Network User license

a.If the user is on the console, a local standard license should work. This is a common usage.

b.A machine running Server OS can only run PHDwin while connecting to a network seat license for the program. Attempting to run multiple sessions of PHDwin on Server OS is limited to the total number of available network seats.

c.This limitation was not needed in V2 because you could only run 1 instance of PHDwin. With the ability to allow users to run multiple instances of PHDwin in V3 this limitation had to be enforced.

2.If the OS is a workstation (e.g. Windows 10), a floating or fixed (standard) license should work from either the console or Remote Access. Note that this is what you are doing on your office computer. This will not breach the license agreement because a workstation, unlike an Server OS, will not support multiple logins operating at the same time.

In summary: 1) A machine running Server OS can only run PHDwin while connecting to a network seat license for the program. 2) Attempting to run multiple sessions of PHDwin on Server OS is limited to the total number of available network seats.