Our company is using a standard enterprise combination of Citrix VDI and VMWare to provide Virtual Windows Desktops that the Sage client is running in.

The 2016.1 release is causing issues with the new Sage licensing, as every time an employee logs in, they are likely to receive a different windows machine as part of their virtual session.

We currently have Sage clients running in a test environment and when we deploy it into production this issue will exacerbate as even more virtual machines will be in the pool.

Any user will be accessing any machine in the pool randomly as availability permits.

I have been working with Sage Technical Support all morning. They were very good at customer service and I appreciated their assistance towards finding solutions, but they have been unable to provide a solution. After reading a related Sage Blog, I am concerned that the three VM's we removed during the tech support session will now never allow a future logon according to the Blog - "Once a computer is deactivated, it will no longer be counted as a licensed computer and will not be able to access the application."

Is there anyone there with experience in deploying Sage in a Citrix VDI and VMWare environment that knows how to best continue working with this new licensing system in version 2016.1?

I was able to remove the admin licenses that were used during building, deploying and testing the image, but we are out of resets, still running into issues and having read this, concerned that some of the virtual workstations in the pool will no longer be able to access the application.