Install Windows on Build / Continuous Integration Server RRS feed

  • Question

  • Hello. 

    After reading the Microsoft Visual Studio Licensing 2015 White Paper I am still a bit confused if our MSDN/VisualStudio Subscription covers what we want. 

    We have Physical Server which runs a Virtualization OS. On this Physical Server we have 1 VM for our Build and Continuous Integration Server. On this VM we want to install Windows Server 2016 and use our MSDN Subscription license. Is this allowed or do we need to purchase a license? 


    • The Build Server runs (later TeamCity) to compile our projects and run unit tests. 
    • The Build Server creates Daily/Nightly Builds and copies the final setup.exe to an external Network Drive where Testers grab the setups from. 
    • The Build Server operates a Maven repository where developers consume packages from. 
    • All developers accessing the server remotely, have a MSDN Subscription. 
    • CCNet/TeamCity have web-interfaces, some times users with no MSDN subscription will access the page to check the build status. 
    • We are NOT using TFS which seems to require a purchased Windows license. 

    From the details I've read we should be able to use a MSDN License for this server as it is only used for internal development. All developers using the server directly have MSDN subscriptions. The nasty part is that people (which are part of the project team) without MSDN subscription might access a web interface running on the server



    "When Virtual Environments Require a Separate License
    If a physical machine running one or more virtual machines is used entirely for development and test, then the operating
    system used on the physical host system can be subscriber software. " (Microsoft Visual Studio Licensing 2015 White Paper, Page 18)-> Unfortunately it does not highlight if the VMs also can use the MSDN license for Windows.

    "Different Licensed Users Can Run the Same Software
    Each member of the development team that will use (install, configure, or access) the software must have his or her own
    Visual Studio subscription. Two or more individuals may use the same software if each has a Visual Studio subscription.
    Example 1: A development team consists of 6 software developers, 1 architect/developer, and 3 testers. The team is
    building an in-house Web-based accounting system, and wants to use the software to set up a test environment running
    Windows Server 2012 and Microsoft SQL Server 2014. If all 10 team members will be accessing the development or test
    environment, then each will require a Visual Studio subscription. The minimum subscription levels including both of these
    products are Visual Studio Professional – annual, Visual Studio Professional with MSDN and Visual Studio Test
    Professional with MSDN." (Microsoft Visual Studio Licensing 2015 White Paper, Page 12) -> Here it becomes tricky and it highlights that all team members (including non devs) need a subscription. In our case testers without subscription might access the web interface of the CI software to check the build status. 

    Kind Regards 

    Kind Regards

    Tuesday, January 9, 2018 4:30 PM