This comparison is not easy because the license overview shows license rights, not deployments. A customer`s inventory data can display 1,000 copies of Office 2010, while MLS displays 1,000 licenses for Office 2013. Because the customer has a security association for Office, their 2010 licenses were upgraded to Office 2013 at the time of product release. But the customer is still compliant: 2013 release licenses cover 2010 release deployments through Office`s built-in downgrade rights. A customer had to pay a $250,000 bill for missing Office licenses. When reviewing their purchase history, we found that the customer initially purchased a ”business desktop” that bundles Windows, Office, and Core CAL suite licenses with SA. When it was renewed in 2007, the individual components were listed, not all, but the MLS could not record the transition to separate Office licenses. The MLS correction eliminated the deficit. Some purchases may go unprocessed for several reasons, such as . B if the product name in the MLS document does not match existing application records or names in the Application Discovery Library. or a software license definition corresponds to multiple licenses in the system. All of these purchases appear on the Unprocessed Purchases page and must be processed manually or through the Payment Assistant. See Unprocessed purchases.

The Transaction Data tab contains raw data that indicates each license purchase. The many columns include the entity that acquired the license, the contract by which it was acquired, the number of licenses purchased, the type of license – license and SA, SA only, standard (license purchases only), subscriptions, etc. – the reseller through which it was purchased and the country of use. This is the second most viewed and essential tab for anyone who wants accurate details about a customer`s purchase history. If you have any questions, please let me know or contact the MLS team at mlshelp@microsoft.com A license fee represents your right to install and use software products as described in the license agreement. The Microsoft License Statement (MLS) is a useful document for managing Microsoft software resources. The MLS is a report published by Microsoft that provides an understanding of software titles and the number of licenses (or license fees) purchased by your organization. The Pivot Data tab of an MLS report is used by IT Asset Management to generate the license position for Microsoft. To get a complete overview of your Microsoft investment, you need an inventory called the Microsoft License Statement (MLS).

This little-known spreadsheet document is a comprehensive effort by Microsoft to inventory every license transaction your organization makes. It is common to see transactions go back fifteen or twenty years in MLS. If you want new purchases not to be affected by future MLS imports, you can set the Authorization Status column on the Purchases tab of the License Properties page to Always enabled for these purchases. For example, you made an over-the-counter purchase of three different Microsoft licenses after you set an initial baseline through an MLS import. If you update the license line by importing another MLS, licenses are disabled if the associated purchase date is older or matches the new base date. This typically requires scanning the Transaction Data tab or customer purchase records to discover the original licenses. Here are three situations we recently encountered: The 2003 and 2007 project numbers are more complex. The effective license quantity displays licenses that were purchased without SA or for which SA has expired.

The Upgrade License Quantity (w Maintenance) column displays licenses in limbo: SA was purchased for them in previous agreements, but no underlying license purchase can be found and therefore these are not counted towards the actual license quantity.] The license overview shows the number of licenses purchased by the customer, by product and version version, as well as the license rights purchased through upgrades and SA. This is confusing for many customers, so we`ll take a closer look at it below. When you select Accept credentials and process purchases, IT Asset Management uses automatic recommendations to create license records (from the Microsoft license instruction) that match the permissions saved in the MLS. One of the reasons for the unresolved quantities that have occurred multiple times is this: When Microsoft discontinued upgrade licenses in 2001, customers had the unique option to purchase Upgrade Advantage or Software Assurance for licenses they already owned (typically, as Paul says, you can only purchase SA at the time of license purchase, but it was an exception). The offer was valid until 31.07.2002. MLS never recognizes this offer and will consider SA purchased as an extension for these ”loose” Upgrade Advantage and Software Assurance purchases as an invalid renewal and will store the licenses as unresolved quantities. Since many companies have taken advantage of this offer, you will probably come across it if you work as a SAM consultant. A customer was on the hook for more than 100 copies of Project Professional, for which he had paid SA for many years, but the original licenses could not be found by the auditor. We pointed out that Project 2003 was the first version with a Professional edition and that customers with SA on the previous version (like our customer) received Project Professional licenses.

No transactions took place, so the licenses had to be derived from the Project 2003 SA migration rights. Full licenses purchased with a specific license ID only appear in the license summary if the user can see that license ID in the relationship summary. (In other words, only if the user logged in to the VLSC has permission to view items related to this license ID.) Displays your organization`s important contacts, associated licenses, orders, order details, and purchase history by a specific license ID. OEM licenses cover pre-installed software that ships with hardware. For the OEM license to be considered valid, the proof of purchase must identify both the software and the qualified hardware. A valid proof of purchase includes the invoice and receipt, certificate of authenticity, box and manuals with the original product key attached. It depends on who creates the MLS (they are assembled by contractors). Licenses with SA may not be included in the Effective License Quantity column because (theoretically) an upgrade could be performed before the contract expires, which could result in an upgrade to a newer version. .