- #How long is visual studio enterprise license good for install
- #How long is visual studio enterprise license good for software
However, it eventually seems to say that deploying development and production virtual machines to the same physical hardware is allowed (without having to supply "production" licenses for all installed software on the development and test virtual machines). This post starts out by saying that mixing development and production virtual machines on the same physical hardware The closest thing was this thread below (which in my opinion I found to be inconclusive):
I've found some prior discussions on this topic, but I could not find a satisfying, definite answer from my internet searches. For example, developers/testers would be included in the "DevTest" AD group only if they have an active MSDN subscription. MSDN licensing is on a per user basis, so I'd limit access to any non-production virtual machine via Active Directory user groups. If I recall correctly, each Microsoft Windows Server 2016/19 Standard Edition license covers up to 2 virtual OSE for production use, or a Datacenter Edition license would cover an unlimited number of virtual OSE on this physical virtualization host.įor non-production virtual machines, I'd like to use Visual Studio/MSDN subscriptions to satisfy licensing requirements (which include the virtual development server OS as well as other software like SQL Server). Via Microsoft Volume Licensing (Open Value).
#How long is visual studio enterprise license good for install
On this physical virtualization host, I'd install Microsoft Windows Server (2016 or 2019) with Hyper-V role. I'd like to deploy both production and non-production work loads (virtual machines) to it. I'd like to create a SINGLE physical virtualization server (2 physical CPUs with 8 cores each).
To keep things focused, I'll just explain what I'd like to do: My goal is to avoid a catastrophic licensing "snafu".įair warning - I have an atypical situation, and this post would get much more complicated if I were to delve into all the details about why I've chosen my particular design. To clarify, I want to understand the implications of my planned design with respect to compliance with Microsoft's Development & Test) and production use, and I'd appreciate some expert advice specifically limited to Microsoft licensing considerations. Virtual environments for both non-production (i.e. I'm planning my first Microsoft Hyper-V deployment of
0 kommentar(er)
