Apr 23, 2019 - 11:04 AM
Visual Studio the tool is fine to use in on any number of machines used by developers, as long as they have an active subscription or a perpetual license for the in-use version. Or are you saying that your developers have got a Prod machine for company email and the like and a separate Dev machine? Production here means "software developers and other staff who are using VS to design, develop, and test applications". As long as you're not connecting VS to production systems you're fine, as I understand it.
Apr 23, 2019 - 11:16 AM
From a licensing perspective it is my understanding via our reseller that because we have an SCE and EA, we are required to procure only the subscription based method of entitlement to Visual Studio, and that we cannot license the tool via a standalone license.
If developer workstations are covered and not defined as 'production' as one partner inferred then a small light be forming at the end of my tunnel!
Apr 23, 2019 - 12:37 PM
I've never had to manage a huge number of Dev/Test users (we had about 40, and most of those were sysadmins) so I'd have to defer to someone with greater practical knowledge of this but my approach was get Ops to segragate Dev/Test using AD access groups and control via Service Request authorisation who was added to those groups - basically only those users with a VS subscription. That way they had their developer sandbox segragated from the rest of the network, but they were certainly using VS on a machine that was also used for production tasks such as writing documentation, emails, HR stuff, and so on. What those machines did need to have was a valid Windows OS license (OEM fine) - you're not allowed to use the VS subscription Windows OS entitlement on a machine used for production.