Deploy its Licenses only with Microsoft Azure Platform Services or qualified License Mobility through Software Assurance Partner; and Complete and submit the License Mobility Validation form with each License Mobility through Software Assurance Partner who will run its licensed software on their shared servers. Customer may move its licensed software from shared servers back to its Licensed Servers or to another party’s shared servers, but not on a short term basis (not within 90 days of the last assignment). Customer may also move Instances run or OSEs managed under a particular License from shared servers in one Server Farm to its shared servers in another Server Farm, but not on a short-term basis (not within 90 days of the last assignment). OSEs managed under the same License must be in the same Server Farm. Customer agrees that it will be responsible for third parties’ actions with regard to software deployed and managed on its behalf. Except as provided below, the License Terms applicable to the Product together with the License Mobility through SA terms govern its use. The License Mobility through SA terms supersede any conflicting License terms for a Product when License Mobility through SA is used. Some Products, as outlined below, have different use rights for shared servers under License Mobility through SA: License Product/Product License Permitted Model Type Number of: OSEs or Cores per License Server/CAL External Each 1 OSE per Connector External license Licenses Connector License with active SA coverage Server/CAL SQL Server Each Server 1 OSE per License with license active SA coverage Per-Core All eligible Each Core One virtual Products License with core active SA (subject to coverage the product use rights including the requirement of a minimum of 4 cores per OSE) Management System Center Each 2 Managed Servers 2012 R2 Management OSEs per Standard License with license active SA coverage Management System Center Each 10 Managed Servers 2012 R2 Management OSEs per Datacenter License with license active SA coverage Fail-over Rights For Products that are also granted Fail-Over Rights, Customer may run passive fail-over Instances on the qualifying shared servers in anticipation of a fail-over but the number of Fail-over Instances must not exceed the corresponding number of licensed product Instances. Servers Self Hosted Applications – Self-Hosted Applications means those Products for which Self-Hosted rights apply. Despite any terms to the contrary in Customer’s volume licensing agreement including the Product Terms, Customer may run licensed copies of Self-Hosted Applications that interact directly or indirectly with its software to create a unified solution (“Unified Solution”) and permit third parties to use it, subject to the terms below.
Deploy its Licenses only with Microsoft Azure Platform Services or qualified License Mobility through Software Assurance Partner; and Complete and submit the License Mobility Validation form with each License Mobility through Software Assurance Partner who will run its licensed software on their shared servers. Customer may move its licensed software from shared servers back to its Licensed Servers or to another party’s shared servers, but not on a short term basis (not within 90 days of the last assignment). Customer may also move Instances run or OSEs managed under a particular License from shared servers in one Server Farm to its shared servers in another Server Farm, but not on a short-term basis (not within 90 days of the last assignment). OSEs managed under the same License must be in the same Server Farm. Customer agrees that it will be responsible for third parties’ actions with regard to software deployed and managed on its behalf. Except as provided below, the License Terms applicable to the Product together with the License Mobility through SA terms govern its use. The License Mobility through SA terms supersede any conflicting License terms for a Product when License Mobility through SA is used. Some Products, as outlined below, have different use rights for shared servers under License Mobility through SA: License Model Product/Product Type License Permitted Number of: OSEs or Cores per License Server/CAL External Connector Licenses Each External Connector License with active SA coverage 1 OSE per license Server/CAL SQL Server Each Server License with active SA coverage 1 OSE per license Per-Core All eligible Products Each Core License with active SA coverage One virtual core (subject to the product use rights including the requirement of a minimum of 4 cores per OSE) Management Servers System Center 2012 R2 Standard Each Management License with active SA coverage 2 Managed OSEs per license Management Servers System Center 2012 R2 Datacenter Each Management License with active SA coverage 10 Managed OSEs per license Fail-over Rights For Products that are also granted Fail-Over Rights, Customer may run passive fail-over Instances on the qualifying shared servers in anticipation of a fail-over but the number of Fail-over Instances must not exceed the corresponding number of licensed product Instances. Servers – Self Hosted Applications Self-Hosted Applications means those Products for which Self-Hosted rights apply. Despite any terms to the contrary in Customer’s volume licensing agreement including the Product Terms, Customer may run licensed copies of Self-Hosted Applications that interact directly or indirectly with its software to create a unified solution (“Unified Solution”) and permit third parties to use it, subject to the terms below.
1602-product-terms.docx