Alex In our case, we really haven't had to do anything special in regards to licensing.
For Microsoft products, we have a campus license which allows us to install on any University-owned systems using the campus site key. For many applications we have network license servers, so the VCL images with that software point to the license servers to get licenses. For all other licenses we have, the license is for a specific number of seats, not specific computers, so we just set the maximum concurrent usage setting on the image to the number of licenses there are for the application. Mike Mike Waldron Systems Specialist ITS Research Computing University of North Carolina at Chapel Hill CB #3420, ITS Manning, Rm 2509 919-962-9778 ________________________________ From: Alexander Patterson [alexander.patter...@csueastbay.edu] Sent: Wednesday, March 07, 2012 1:12 PM To: vcl-user@incubator.apache.org Subject: VCL software licensing Hello, I wanted to know how are people dealing with software licensing for VCL? Does anyone have a document or information on how they are dealing with the different vendors when it comes to VCL. For example with Microsoft you are using 1 license for each virtual machine you spin up in a Windows environment. Do you have one per user base? Is this for concurrent users? Are you able to split up lab licensing for in house software to be used in the VCL? Do the companies know you are doing this? Does anyone have an agreement with any vendors that goes within the current VCL licensing that they are using? If someone has like an overview or general information on how you are licensing the VCL for educational use; that would be very helpful. We are starting to run into licensing walls and I would love some inside information from someone who has gone through this. -- Thanks, Alex Patterson User Support Services Operating System Analyst California State University, East Bay
