Most companies with more than a handful of computers in their IT environments rely on the results of network-inventory tools to gather the deployment data needed for accurate software audits. Without the tools, a business would be required to assign valuable resources to manually looking at the titles installed on each machine. Therefore, it should…
Microsoft licensing is a complex, multi-faceted undertaking, with different rules and license metrics applying to different products. In the context of software audits initiated by Microsoft, it is important to keep in mind the fact that the auditors hired to perform those investigations are fallible human beings and that they can (and do) make mistakes…
In recent years, Microsoft seems to have been shifting an increasing volume of its license-compliance resources toward what it calls Software Asset Management (SAM) reviews. These “optional” engagements typically are proposed by Microsoft personnel with whom a company has not had any prior interactions, and the company often receives no advance warning or introductions from…
Microsoft’s Services Provider License Agreement (“SPLA”) is a popular licensing framework for businesses delivering hosted or rented software solutions to their customers. However, as with many software license agreements pertaining to resale or other business channel partnership programs, the SPLA typically includes audit rights language giving Microsoft the ability to review a SPLA partner’s records…
Following the conclusion of a software audit, Microsoft’s standard practice is to require an audited company to purchase licenses associated with calculated “unlicensed use” within a set period of time (typically, 30 days) following receipt of Microsoft’s settlement demand. However, it is important for companies with Enterprise Agreements to keep in mind the fact that…
Many of our clients contact us regarding notices they received from Microsoft requesting an internal self-assessment of their license positions under their Services Provider License Agreements (SPLAs). Naturally, many of those clients have questions about that process and the ramifications of cooperating with Microsoft. For those who may be unaware, SPLA is the principal licensing…
Microsoft does not make licensing SQL Server easy, either under SPLA or under volume licensing agreements. Here are the three most significant problems that our clients face when trying to license that product: Four-Core Minimum – Microsoft allows SQL Server to be licensed based either on physical core counts (for physical servers or virtualization hosts)…
Companies with experience licensing Microsoft software and services through Enterprise Agreements know that small forests could be felled to produce the paper required for the typical document stack. EAs often incorporate a dozen or more different components, including some or all of the following: Microsoft Business and Services Agreement or Microsoft Business Agreement (Microsoft sometimes…
Microsoft, like other software publishers, routinely audits customers to help ensure that it is protecting the value of its intellectual property. Microsoft verifies its customers’ compliance using several methods. Microsoft License Verification (also, Software Asset Management “SAM” request). In a SAM request, Microsoft assigns a third party to reach out to a customer to confirm…
Many software-solution vendors utilize third-party infrastructure or application programs as frameworks for embedded solutions that they sell to their customers and install on their customers’ computers. Licenses for those third-party products typically can be acquired by a vendor and passed to its customers pursuant to the terms of an Independent Software Vendor (ISV) or Original…
