Software Compliance
  • Home
  • What We Do
    • Services
    • Tools
    • Experience
  • Resources
    • FAQ
    • Agreements
    • Documentation >
      • Brochure
      • Datasheet
      • Security Measures
      • ComplianceWare >
        • Software
        • Hardware
        • Cloud Configuration
  • Company
    • Contact Us
    • About Us
    • Careers
  • Latest
  • Search

Software Vendor Performance FY2020

24/2/2021

0 Comments

 

Vendor results can be a telling indicator of what might lie ahead

We regularly connect with the ITAM Review as a reliable source of information in the software domain and of interest this month is a comprehensive report from Rich Gibbons on the financial performance of some key software vendors - from the $5.6B loss of Google Cloud to the 29% rise in operating income (Q2) of Microsoft.
You'll find the full report here.
In summary ...
  • AWS saw revenue increase 29% to $45.3 billion, with income up 47% to $13.5 billion;
  • Google Cloud reached $13.1 billion for the financial year, an increase of 47% however incurred loses every quarter with an overall loss of $5.6 billion for the financial year;
  • IBM's overall revenue was down 5% to $73.6 billion however cloud revenue was up 19% to $25.1 billion well supported by Red Hat revenue up 18%;
  • Not a great year for Micro Focus with an annual revenue of $3 billion (a 10% drop on 2019) with a $3 billion loss for the financial year ($2.8 billion of which was a write down on a large chunk of the ill-fated HPe purchase from 2017);
  • At the midway point for Microsoft revenue was up 17% to $43.1 billion with operating income up 29% to $17.9 billion - a very healthy start to their financial year;
  • SAPs total revenue was €27.3 billion 1% down year on year, with cloud revenue €8.08 billion, representing a rise of 17%.
Some marked differences in performance - particularly in the cloud space, with a watch and ready advice for some of the poorer performers - we all know where they head when times are tight ... 
Picture
... the perceived quick gains of the audit trail.
0 Comments

Are You A Microsoft Open License Customer?

30/9/2020

0 Comments

 

If so ... Changes are coming.

Microsoft have announced that as of January 1st 2022 the Open License Program will be withdrawn for its commercial customers.
From then on, if you're still wanting to procure perpetual software licenses you'll need to do so through a Cloud Solution Provider (which your current license partner might well already be).
Picture

What do you need to do?

All services, products, and offers in Open License program today will remain available until January 1, 2022. To plan for future purchases, ask the partner you’re currently buying software licenses from about your options. Your partner can help you decide the best steps for you, whether that’s new licenses or online services subscriptions. If you don't have one, you can Find a Microsoft partner.

Are there any other options available?

Yes - depending on what you want to purchase you can make use of the Open Value or the Open Value Subscription program:
  • ​The Open Value program is recommended for future purchases that include Software Assurance.
  • The Open Value Subscription program program doesn’t offer perpetual software licenses but is a lower-cost subscription that gives you rights to use the software during the agreement’s term and also includes Software Assurance.
Here's a reminder of the differences between the current programs:
Picture
So nothing alarming in this announcement, more just an evolution of a 20 year old program to align with Microsofts contemporary go to market structures. While 2022 might seem some time away you can be sure the changes will begin to emerge through 2021, so just something more to be aware of and prepare for in the ever changing world of software licensing!
0 Comments

Changes to Microsoft SA Benefits

28/12/2019

0 Comments

 

New for 2020 - Microsoft to reduce Software Assurance Benefits

Changes to Microsoft's SA Benefits have been announced  effective 1st February 2020 which will see the end of some of the most useful aspects of the program, in summary:
  • all cloud services will be retired from Deployment Planning Services in favor of FastTrack deployments;
  • removing Azure training from eligibility and training days will no longer be used to convert to Planning Services days; and
  • ​beginning in February 2021, support eligibility criteria and replacement of incident-based support with as-needed support and credit toward Unified Support.
Deployment Planning Services
FastTrack is now Microsoft's primary implementation support offering applicable to Azure, Microsoft 365, and Dynamics 365 engagements. All on-premises Deployment Planning Services offerings and the respective engagements will be available until January 2022 and you can continue to redeem your deployment planning days through the current process from qualified partners or Microsoft Consulting Services to help you plan your deployment—whether on-premises or in hybrid environments. ​
Training Vouchers
Training vouchers can still be used until January 2022 with the exception of Azure training, which will be removed from the Software Assurance course catalog in February 2020. The Training Vouchers benefit will be fully retired on January 1, 2022. 
The right to access training vouchers expires with your Software Assurance coverage. If you create a training voucher before the expiration of your Software Assurance coverage, the voucher remains valid for 180 days after the date it was created.
Software Assurance E-Learning was replaced with Microsoft Learn  on November 1st 2018, which offers a free-of-charge way to learn about Microsoft products and services. Instructor-led training is available, and Microsoft are introducing role-based courses and advanced workload courseware, along with new certifications. ​
24x7 Problem Resolution Support
Customers will no longer earn a limited number of support incidents based on spend, agreement type, and product(s) but instead will get as-needed support with a Software Assurance spend of $250,000 or more annually. ​
Starting in February 2021, customers that spend more than US$250,000 per year on Software Assurance will get as-needed basic phone support for Severity A and online support during business hours for Severity B and C with a 24-hour response time. Customers will also have the option to upgrade to Microsoft Unified Support.  
Customers that spend less than US$250,000 per year on Software Assurance with no enterprise support agreement (Premier/Unified) will be directed to a partner for support or purchase Professional Support incidents from Microsoft.
So time to review all of your enrollments and make sure you convert all of your SA Benefits to get full value out of your investment in these programs. As a refresher, take a look through the list below.
Picture
0 Comments

New SQL Server SA Benefits

24/11/2019

0 Comments

 

Check out this October announcement - It could save You Thousands!

Microsoft recently announced a new SQL Server SA benefit that is well worth reviewing – it could either release some currently consumed cores or save you buying more for any clustered environments you have now or are planning.
Starting Nov 1st, every Software Assurance customer of SQL Server will be able to use three enhanced benefits for any SQL Server release that is still supported by Microsoft:
  • Failover servers for high availability – Allows customers to install and run passive SQL Server instances in a separate operating system environment (OSE) or server for high availability on-premises in anticipation of a failover event. Today, Software Assurance customers have one free passive instance for either high availability or DR
  • Failover servers for disaster recovery NEW – Allows customers to install and run passive SQL Server instances in a separate OSE or server on-premises for disaster recovery in anticipation of a failover event
  • Failover servers for disaster recovery in Azure NEW – Allows customers to install and run passive SQL Server instances in a separate OSE or server for disaster recovery in Azure in anticipation of a failover event
So considering a typical architecture per diagram below the number of SQL Server core licenses required to operate this topology would be only 12 cores as opposed to 24 cores in the past:
Picture
​Now the FAQ’s in the announcement included a specific question as to the versions that were covered and was answered in the affirmative by a Microsoft representative:
Q1. Is this applicable to old SQL Server versions like 2014 & 2016?
Answer for Q1: Yes. The benefit applies to all supported releases of SQL Server.
Which raises the question – why do we once again see a potential conflict in the Product Terms which appear to qualify the benefit to SQL Server 2019 only:
4.2 SQL Server 2019 – Fail-over Rights
For each of its Primary Workloads, Customer is entitled to:
  • One Fail-over OSE for any purpose, including high availability, on any Server dedicated to Customer’s use (subject to their new  Outsourcing Software Management clause); and
  • Two Fail-over OSEs specifically for disaster recovery purposes:
  1. one on any Server dedicated to Customer’s use (subject to their new Outsourcing Software Management clause) and
  2. one on Microsoft Azure servers 
We shall (again) seek clarification from Microsoft. In the meantime, check out more comprehensive information and examples in the accompanying Licensing Guide.
0 Comments

Clarifying Microsoft 365 On-Premise Rights

7/10/2019

0 Comments

 

 Lets Straighten out On-Premise Rights Included with M365 

A quick internet search is likely to find conflicting views on what on-premise rights you are granted with your M365 Subscription particularly in relation to server software. Many sites will state that you gain only user access rights with your USL licenses, ie. essentially a CAL license entitlement, and that you are still required to acquire the server licenses for the likes of Exchange and Sharepoint.
Simply, that's not correct.
Firstly though, be sure of the M365 Subscription you are dealing with as each will offer different content and scope. The CAL/ML equivalency table of the Product Terms provides a good overview to this:
Picture
Note for example that the common business E3 and E5 plans provide both Base and Additive access rights for Exchange and SharePoint Server. But what about the Server Licenses?
​A quick browse through the FAQ of the M365 Site provides the first hint that certain Server software is indeed included:
Picture
But we all know that relying on commentary - even on the Microsoft site - is not enough ...
... so where to?
The Product Terms of course.
The definitive descriptor of Microsoft's Software licensing terms.
While the respective sections covering the likes of Exchange or SharePoint Server software don't provide any clues, the Microsoft 365 section clearly articulates the entitlement (page 57 of the October 2019 document):
Picture
Assuming all of your users are properly licensed (and they should be) your on-premise Exchange, SharePoint and Skype for Business Server installations are covered!
... and that includes back-versions of course under the Universal License Terms part 3 - "Rights to Use Other Versions and Lower Editions".
So no need to True-Up those on-premise Server licenses for Exchange or SharePoint, and who isn't keen for less overhead and more funds right?!
0 Comments

Changes To Microsoft Licensing

11/8/2019

0 Comments

 

terms related to outsourcing rights and dedicated hosted cloud services Change 1-Oct.

Microsoft’s off-premise outsourcing terms are changing October 1, 2019, evidently to clarify the distinction between on-premises/traditional outsourcing and cloud services, and create more consistent licensing terms across multitenant and dedicated hosted cloud services, the core of the changes being:
 
  • On-premises licenses purchased without Software Assurance and mobility rights cannot be deployed with dedicated hosted cloud services offered by “Listed Providers” being Microsoft, Alibaba, Amazon (including VMware Cloud on AWS), and Google (the changes don't apply to any other providers - yet - and if/when they do you'll get 12 months to get compliant).
  • Microsoft licenses with License Mobility through Software Assurance can now be used on dedicated hosted cloud services with any Listed Provider who is also an Authorized Mobility Partner.
  • Microsoft licenses with Software Assurance can be used with the updated Azure Hybrid Benefit, including on the newly launched Azure Dedicated Host.
Now there’s one statement that seems to negate it all (page 3 of the FAQ) given all of the Listed Providers are currently in the Authorized Mobility Partner list which we’re seeking clarification from Microsoft for (italics added):
 
Do the updates to the Outsourcing Software Management clause affect my rights to deploy licenses with an Authorized Mobility Partner? License Mobility through Software Assurance rights will be expanded to permit deployment of licenses with License Mobility coverage with Listed Providers’ dedicated hosted cloud services for those Listed Providers who are Authorized Mobility Partners. (and importantly) Rights to deploy licenses on Authorized Mobility Partners’ shared servers are not impacted by the outsourcing update.
But that aside, lets dissect it all ...
Picture
Firstly, what exactly are “dedicated hosted cloud services”? Microsoft’s states this to be the “services offered by major public cloud providers typically with elastic, ondemand, pay-as-you-go resources, like their multitenant cloud services.” Multitenant cloud services? Wouldn’t that be the opposite of dedicated?? Well for the Listed Providers examples given are “Azure Dedicated Host, Amazon EC2 Dedicated Hosts, single tenant nodes from Google” – all dedicated – and “VMware Cloud on Amazon Web Services (AWS)” – so perhaps the/an exception being SDDC architecture. 
The first thing to note - the change won't impact the use of existing software versions under licenses purchased before October 1, 2019 so you can continue to deploy and use software under your existing licenses on servers dedicated to you, just not workloads under licenses acquired on or after October 1, 2019 (and don’t forget that just performing a Software Assurance renewal doesn't affect your perpetual use rights for existing versions). And secondly, rights to deploy licenses on Authorized Mobility Partners’ shared servers are not impacted by the outsourcing update.
So what to be wary of …. as usual, the limitations:
  • Use of Windows Enterprise licenses with Listed Providers dedicated hosted cloud services will require Windows VDA E3/E5 user licenses, so if you’re in this situation but have existing SA coverage or E3/E5 subscriptions you’ll have until October 1, 2020 to migrate away from the Listed Provider if you want to avoid having to buy these additional licenses.
  • A number of products do not have License Mobility through Software Assurance and are therefore not permitted to be run with Listed Providers’ dedicated hosted cloud services, such as:
    • Office Professional Plus
    • Windows Server (although you can move your External Connector licenses)
    • Core Infrastructure Server (CIS) Suite
    • System Center Suites (excepting Standard/Datacenter Management Servers)
Are there any alternatives? Well, besides any SPLA or otherwise ‘bundled’ licensing options available with the provider service, enter the Microsoft Azure Hybrid Benefit (!) where, solely with Azure Dedicated Host, there are exceptions (!!) if you happen to have current SA or equivalent subscription rights. And what might the Azure Hybrid Benefit provide:
  • the option to license by virtual machine (Datacenter or Standard), or to license by physical host, but allocate core licenses only for the number of cores available to you (Datacenter only)
  • use is governed by the Online Services Terms (OST) and therefore does not require base CALs
  • permits you to host solutions on Azure for access by your customers
  • equivalent of on-premises fail-over rights for SQL Server, and in the case of SQL Server Enterprise Core licensed at the host level, the equivalent of onpremises unlimited virtualization rights
  • Both SQL Server and Windows Server are eligible for Disaster Recovery Rights and new version rights
Oh … and don’t forget – to make use of License Mobility through SA, you must ensure that you:
  • Run your licensed software and manage its OSEs on shared servers under the terms of your volume licensing agreement;
  • Deploy your Licenses only with Microsoft Azure Services or qualified License Mobility through Software Assurance Partners; and
  • Complete and submit the License Mobility Validation form with each License Mobility through Software Assurance Partner who will run the licensed software on their shared servers.
For more information check out the Microsoft Announcement and associated FAQ's
0 Comments

Microsofts New Licensing Terms Site

16/6/2019

0 Comments

 

A New And WeLcome Direction in Consolidated, Direct, Licensing Information

Microsoft announced the 1st June 2019 as the date at which the new 'Licensing Terms Site' will replace the current downloadable document versions of the Product Terms (PT) and Online Service Terms (OST) (although at date of this publication it is still stating "under construction and for preview use only.")
Not only ​is this intended to consolidate the myriad of licensing documents and material rife across Microsoft sites, but according to the FAQ (available here) will also ease navigation through filters available by program and product, and also introduce a new 'compared-to' function which allows users to compare changes (albeit post 1st June 2019) to 'current' use rights going forward - a useful utility!
So what does it look like? - the landing screen as below (see it for yourself here):
Picture
A quick test run found the site easily navigable, presenting targeted information based on your selection in the familiar format of the Product Terms structure. Of course it can't solve the 'knowledge complexity' invariably attached to licensing - you basically still need to know what you are looking for, and then be able to apply what you find to your own situation.
A quick delve into the SQL Server section highlights the information then available by edition:
Picture
All in all though a timely advance in the overall licensing landscape that would be welcomed across other vendors with similarly broad and complex license terms and models, which makes us wonder ...
 ... is it too much to hope for a cross-industry standard? 
0 Comments

WINDOWS AND SQL SERVER 2008 END OF SUPPORT

23/9/2018

0 Comments

 

Extended Support for SQL Server 2008 and 2008 R2 will end on July 9, 2019.
Extended Support for Windows Server 2008 and 2008 R2 will end on January 14, 2020.

With many companies still running programmes of work to migrate from Windows Server 2003 news that the end of ES for Windows Server 2008 is less than 18 months away is sure to cause some angst, and more so if you're also reliant on SQL Server 2008 which ends in 10 months!
Picture
Picture
What will 'end of support' mean? ... it will mean the end of regular security updates, and with the extent of hacks and attacks going on at any time - and the (legitimately) tough regulatory position on data protection - that would be a concern to all.
Now there are of course some options available at this stage to address this exposure:
  1. If you are an Azure customer, Extended Security Updates will be available for free in Azure for 2008 and 2008 R2 versions of SQL Server and Windows Server to help secure your workloads for three more years after the end of support deadline.
  2. If you run on-premise installations, you will be able to purchase Extended Security Updates for three more years as long as you have Software Assurance or Subscription licenses under an Enterprise Agreement enrollment.​ 
So if it's free for Azure customers, what does it cost if I'm not? ... 
75 percent of the full license cost of the latest version of SQL Server or Windows Server,  purchased annually to cover only the servers that require the updates.
Ouch.
But wait, there's more. If you happen to run any IBM software under Windows Server, and you also run those servers in a virtualised environment, you need to be aware of an often overlooked limitation under IBM's sub-capacity rules. And that relates to 'Eligible Technologies'.
A quick glance through the regularly updated table by our ILMT development friends could come as a bit of a shock if you happen to still be running Windows Server 2003 - it's no longer an eligible technology - take a look at the snippet below under VMware:
Picture
You can view the entire list here. 
And if it's 'not eligible', what does that mean? Basically that you'll need to revert to manual counting for that environment, and for which IBM provides a particularly onerous method and template as an Excel workbook downloadable here.
So taking the Windows Server 2003 omission as an example it's fair to expect that we'll see Windows Server 2008 drop off in equally quick time. Not only then is there a compelling cost imperative due to Extended Support, but an equally expensive overhead with IBM sub-capacity tracking and reporting as well (remember - you need to generate your sub-cap domain usage quarterly).
​Time to act!
Microsoft have an advisory page here that is worth checking which also provides links to their end of support resource center for further advice and assistance. And if you're looking for a better tool than perhaps a spreadsheet for you IBM sub-cap reporting we have just the ticket with our ComplianceWare application - we recommend you check it  out here!
Picture
Picture
0 Comments

Windows Server 2019

21/4/2018

0 Comments

 
Well the new edition of Windows Server is now imminent - Microsoft have announced its GA for the second part of 2018 - with innovations across four key areas being Hybrid cloud, Cyber-Security, Application Platform and Hyper-converged infrastructure, all built upon the popular, solid foundation of Windows Server 2016.  
So what does that all mean?​
Hybrid cloud brings the management of servers across on-premise and Azure together with the Server Manager first demonstrated at Ignite in September 2017.

​Code named Project Honolulu the console provides easy integration to Azure services (such as backup) without disrupting applications or infrastructure.

​ Check more here.
Picture
Cyber-Security takes on three themes of Protect, Detect and Respond, with the introduction of Shielded VM's to protect virtual machines from compromised or malicious administration, and Windows Defender Advanced Threat Protection.
The Application Platform has improvements targeted at developers across Windows Server containers (including Kubernetes under beta) and Windows Subsystem on Linux that allows Linux containers to be run side-by-side with Windows containers.
​And the Hyper-converged cloud solutions are designed for flexibility and scale to offer high performance, manageability and security as a fully-deployed configuration, all administered through the Server Manager. 
From a licensing perspective Windows Server 2019 will follow the current per-core metric, and include full support for System Server clients (also to release as a 2019 edition).
If you'd like to see more you can access the preview build via Microsoft's excellent Insiders program which just requires a simple registration - access it here or  if you'd just like some more information you can just check out the Release Notes.
Hard to believe 2019 is not too far away already ...
0 Comments

PROCESSOR DESIGN - Kernel Leak

5/1/2018

0 Comments

 

How might it affect performance and licensing? 

As the full implications emerge with the design of Intel's (and potentially others) x64 processor (see more at the Register here) we await with interest a response from software vendors as to how the corresponding issue of licensing will be answered and resolved.
Given patches are now being released (eg. AWS EC2 5th January, Azure the 10th January) the resultant performance impacts will become the subject of intense scrutiny. Why? well if, as reported, processing power diminishes anywhere from 5 to 30 percent how will customers be compensated?
Processor and Core based software has been dutifully acquired on the basis of the underlying performance of the chipsets on which the products are run (consider IBM's PVUs, Microsofts Core minimums etc). Now though, if that proves to be erroneous, surely a remedy must be made available to the customer who has paid for a defined - and benchmarked - level of processing power?
Take the scenario whereby a customers current 2,000 PVUs can no longer deliver the required throughput and needs a further 500 PVUs in order to deliver the same capability - you would be right to expect no additional charges to apply given there is no improvement in performance surely? And what about needing more hardware just to achieve the current level of demand, or a Cloud vendor purchasing an array of new servers in order to provision more vCPUs for their PaaS / SaaS customers just to meet the same CPU cycles ?
That all costs money, so ... Who Pays??
Which then presents an intriguing conundrum for the chip makers and the software vendors. Presumably there will be a vast re-benchmarking exercise (and consider chipsets produced in the last 10 years are potentially affected) the question then being, what is to be done on the basis of the results? Compensation? Free License Grants? Reduced Annual Maintenance fees??
So we expectantly await vendor responses once the focus on getting fixes out shifts to the underlying and associated commercial dilemma confronting the industry. What can you do in the meantime? Firstly, make sure you have current performance metrics that you can measure any degradation against, and then pose these questions to your vendor Account Manager, your Sales Rep, your Software Specialist - ask how any performance issues you experience might be remediated in the immediate term, and request an open and regular communication channel to stay informed as it all progresses ...
We firmly believe - if the projected performance impacts do transpire -  this issue will prove to be one of the most perplexing problems to emerge in the IT industry in many years. 
Watch this space for further updates as more unfolds.
0 Comments

3 Licensing Tips to End The Year

27/12/2017

0 Comments

 
While these three little snippets might not seem particularly sensational they are worth noting precisely for that reason - they are likely lurking in the background, ready to cost you money when you least need it!
1. IBM License Management Tool (ILMT)
Picture
OK, so we all know that under the IBM sub-capacity rules we must produce a report from ILMT every quarter right? And we know that we must sign and date that record, and keep them all as an artefact that may be required during any audit too, right?

​All good, then the tip:
 Make sure you have configured ILMT correctly and fully for VM Management. ​
What's so important about VM Management in ILMT? If not properly configured it will default to 120 PVUs per core, so you could be over-reporting without being aware. How can you tell if its configured? Firstly, it shows a status on the Dashboard, and secondly, if not configured servers will be displayed with a serial-like number beginning with 'TLM_VM' or similar.
If you need more information on how to configure just look here.
2. Microsoft Subscription Licensing.
Picture
Microsoft in many ways have led the industry in a shift to SaaS offerings backed by subscription based licensing. While this may appear to have a favourable ROI initially, there are other Time-Value commercial components to consider.
Firstly, you need to be aware that your licensing is now not only visible but manageable real-time by Microsoft. So from a commercial perspective there is now no locked-in pricing for the typical 3 year term of an Enterprise Agreement, instead you will see price increases built-in year on year in your CPS. And more so, there is no 'True-Up' benefit whereby you would pay essentially half the cost in the year in which you deployed the product - you now 'reserve' the additional licenses you need to be drawn down, and you start paying from that month onwards.

​The tip?
Make sure you consider TVM with subscription changes in your ROI / Cost Comparisons.
And the last tip for 2017 ... a favourite topic here at Software Compliance ... processor to core conversion.
3. No 'unpacking' of Core Licenses​
So a quick tally of the number of core licenses across your Windows Server fleet divided by 16 gives you your number of 16 Pack licenses required right?
Picture
Wrong! ... A license pack is applied to a server, so where you have say a 12 Core server you need to assign 6 x 2 Core packs - you can't assign 12 from your 16 Core pack, and then apply the other 4 elsewhere. A nasty - and potentially expensive error - if not properly considered in determining your conversion.
And so ends 2017 ... we look forward to a busy and productive 2018 for us all!
0 Comments

A condensed guide ... Microsoft Processor to Core Licensing

16/11/2017

0 Comments

 
Gone are the more simplistic days of Microsoft Per Processor licensing when there was a basic assignment of a single license to a processor, unlimited use and access, all available across multiple editions of software. Indeed, Microsoft were touting per processor as a major point of difference looking back to even SQL Server 2008, going as far as to claim ‘thought leadership’ when it came to competitor licensing models aligned to multicore processors.

From 2016 though (and noting the GA of SQL Server 2017 from October 2017), following their conformance and gradual demise of the processor metric, there are now primarily three Per Core licensing models:


  1. The Per Core model used by SQL Server and BizTalk Server;
  2. The Per Core/CAL licensing model used by Windows Server (Standard and Datacenter edition) following the release of Windows Server 2016;
  3. The Management Servers (core-based) licensing model used by System Center (Standard and Datacenter edition) following the release of System Center 2016.

So let’s take a look at 2 more common server products afflicted by this change, SQL Server under (1) and Windows Server under (2) – and if you are intending to use Self-Hosting or SPLA rights note that there are further considerations not covered here, the context of this blog contained to licensing acquired under Microsoft’s Volume Licensing offerings (refer: Microsoft Commercial Licensing)
SQL Server 2016
​

With SQL Server 2016 Per Core licensing, each server running software or any of its components (such as Reporting Services or Integration Services) must be assigned an appropriate number of SQL Server 2016 core licenses. The number of core licenses needed depends on whether you are licensing the physical server or individual virtual operating system environments (OSEs), across either edition.
Picture

​Unlike the Server+CAL licensing model, the Per Core model allows access for an unlimited number of users or devices to connect from either inside or outside an organisation’s firewall. With the Per Core model, you do not need to purchase client access licenses (CALs) to access the SQL Server software.
​
When running SQL Server in a physical OSE, all physical cores on the server must be licensed, noting software partitioning does not reduce the number of core licenses required except when licensing individual virtual machines (VMs). A minimum of four core licenses are required for each physical processor on the server,  with the use of hyper-threading not affecting the number of core licenses required when running in a physical OSE, only those licensed under individual virtual machines (which are still subject to the four core minimum).
So with the basics understood you’ll then want to familiarise with what you gain with the addition of a Software Assurance subscription…
Key SQL Server SA Benefits
​
  1. License Mobility: If you are deploying to a server farm with technology such as VMware’s vMotion you’ll need SA for license mobility, now extended to cloud providers that are Microsoft Authorised Mobility Partners;
  2. Unlimited VMs: don’t be mistaken by the ‘Enterprise’ license denotation – without SA you can only run up a maximum number of VMs (with unlimited vCores) equal to the number of core licenses assigned to the server, and without SA that means having to buy more licenses should you exceed the maximum;
  3. Failover Rights: A secondary server used for failover support does not need to be separately licensed for SQL Server as long as it is passive (ie. not serving data, such as reports to clients running active SQL Server workloads, nor performing any “work”, such as additional backups being made from secondary servers) and the primary SQL Server is covered with active SA, noting the licenses must cover the higher number of associated server cores in the HA coupling.
And be cautious – the components of a SQL Server license cannot be separated. While management tools and other software identified as additional or supplemental software such as product documentation, client connectivity tools, software add-ins, and Software Development Kits (SDKs) can generally be distributed and run on any number of devices for use with a licensed instance of SQL Server software, other licensed components such as the SQL Server Database Engine (DB), SQL Server Services for Windows, Master Data Services (MDS), Analysis Services (AS), Integration Services (IS), Reporting Services (RS), and Data Quality Services (DQS) will require licensing if deployed to other servers. You can find more details of the components at: SQL Server Software Components
And for Non-Production: Effective April 1, 2016, SQL Server Developer Edition became a free product, available for download from the Microsoft Dev Essentials program as a potential alternative to the likes of a Visual Studio subscription. SQL Server 2016 Developer Edition is a fully featured version of SQL Server software—including all of the features and capabilities of Enterprise Edition--licensed for development, test, and demonstration purposes only.
Windows Server 2016
​

For both Standard and Datacenter editions, the number of core licenses required equals the number of physical cores on the licensed server, subject to a minimum of 8 core licenses per physical processor and a minimum of 16 core licenses per server (sold in 2-Core and 16-Core packs).
Picture

​Which means being very careful when you tally your overall requirement – make sure you account for the 16-Core per server minimum across any single CPU servers you might have in your inventory where you might otherwise under-allocate (where <16).

And the differences in the editions?
  • Standard: When all cores on the server are licensed (subject to the minimums), you can deploy two OSEs or two Hyper-V containers and unlimited Windows Server containers.
  • Datacenter: When all cores on the server are licensed (subject to the minimums) you can deploy unlimited OSEs, Hyper-V containers, and Windows Server containers.
(and if you're looking for a definition of containers, look no further - go here)
So, To Finish …
Bear in mind that in both cases you will still need to account for the CAL requirements if necessary (and remember to count all direct and indirect users/devices, ie. no multiplexing), typically via the likes of a Core CAL Suite or equivalent, which as an example provides the following licenses:
​
  • Windows Server CAL
  • SharePoint Server Standard CAL
  • Exchange Server Standard CAL
  • System Center Configuration Manager Client Management License
  • System Center Endpoint Protection Client Management License
  • Skype for Business Server Standard CAL

​Noting that the likes of SQL Server CALs and Dynamics/CRM CALs must be acquired separately.
Microsoft have provided a very helpful Licensing Brief across Core Licensing that I would also recommend reading for more information.
0 Comments

NOT TO BE MISSED ...

11/2/2017

0 Comments

 
Well the New Year is now in-play and completing a major Year-2 True-Up for a large Microsoft Enterprise Agreement provided a prompt to refresh on the Windows Server 2016 conversion prior to those nasty renewals that come around so soon.

Much like the SQL Server 2014 migration the Windows Server 2016 shift (which started from October 2016) presents an opportunity for customers with active SA to transition their processor based licenses to core based ensuring coverage is gained across the full physical cores in their environment.

Essentially, where you have a ‘server density’ of 8 cores or less per processor and 16 cores or less per server a full license grant is assumed – there is no need to record your environment as you’ll get the full complement of licenses by default.

If however your server density is higher there’s some work to be done! You’ll need to ensure your entire Windows Server landscape is inventoried and formally documented ready for the expiration of your current SA, at which point you’ll only pay the additional SA, not additional licenses. But if you are not prepared and time gets away on you there’s potentially significant cost down the track as those uncounted cores come to light (the dreaded audit perhaps), so it pays to get organised and active way before your renewal date.

And as a postscript - if you're using subscription licenses be aware that although you can vary down at anniversary, if you varied up at any time during the year - well that applies from the date of install.
0 Comments

... windows server 2016 by a nose!

7/12/2016

0 Comments

 
Well it would seem the big change is the move to (physical) core based licensing for Windows Server 2016, now offered as just two major editions - Standard or Datacentre - with an 8 core license minimum per processor and 16 core license minimum per server (sold in 2-core packs), subject to the accompanying User or Device CALs of course.

What does it all mean? Well the price for 16 core licenses for Standard or Datacentre is being touted as the same as the current pricing for one 2-processor 2012 R2 Standard or Datacentre, but an additional 2-cores will increase the price of server licensing by 25%.

Properly converting your processor licenses to cores is an imperative - if you don't get the numbers right (particularly with VM's running on the Standard edition) you could face some significant costs down the track due to the 2 VM maximum (ie. all physical cores must be licensed again for any VM increment above each 2 VM maximum).

The good news - as with the SQL Server conversion if your SA is current the license grant will cover no less than you have now (ie. all physical cores), so get counting and make sure you have the right artefacts to validate your entitlement at renewal time!


0 Comments

... And the winner is

14/10/2016

0 Comments

 
The latest talk suggests another imminent update by Microsoft in its licensing domain, just where is yet to be seen. Of late though, the changes have been largely positive - certainly the conversion to the Product Use Terms as opposed to the Product Use Rights format (which had morphed into a near undecipherable amalgamation of the varied products and license models) was a welcome change. And the simplification across the server products - take SQLServer with its narrowed editions and rationalised licensing - may well signal a more plain, coherent licensing programme to be front of mind. With the recent release of the new Enterprise Agreement structure what else might be in store is hard to predict, but we're all for a simplified model - a gold medal to the vendor that gets there first!
0 Comments
    • ​+
    • +
    • +
    <
    >

    Categories

    All
    Agreements
    Appliances
    Audit
    BCP & DR
    Cloud
    Compliance
    ComplianceWare
    Contracts
    Forums
    IBM
    Intel
    Licensing
    Mainframe
    Microsoft
    Negotiating Deals
    Oracle
    Partnering
    Red Hat
    Roles
    Software Metrics
    SQL Server
    Windows Server

    Archives

    February 2021
    January 2021
    December 2020
    November 2020
    October 2020
    September 2020
    August 2020
    July 2020
    June 2020
    May 2020
    April 2020
    March 2020
    February 2020
    January 2020
    December 2019
    November 2019
    October 2019
    September 2019
    August 2019
    July 2019
    June 2019
    May 2019
    April 2019
    March 2019
    February 2019
    January 2019
    December 2018
    November 2018
    October 2018
    September 2018
    August 2018
    July 2018
    June 2018
    May 2018
    April 2018
    March 2018
    February 2018
    January 2018
    December 2017
    November 2017
    October 2017
    September 2017
    August 2017
    July 2017
    June 2017
    May 2017
    April 2017
    March 2017
    February 2017
    January 2017
    December 2016
    November 2016
    October 2016
    September 2016

Unravelling license complexity for Business
ACN 623 529 751

Privacy Policy | Terms of Use
Copyright © 2016-2021 (SWC) ​​

  • Home
  • What We Do
    • Services
    • Tools
    • Experience
  • Resources
    • FAQ
    • Agreements
    • Documentation >
      • Brochure
      • Datasheet
      • Security Measures
      • ComplianceWare >
        • Software
        • Hardware
        • Cloud Configuration
  • Company
    • Contact Us
    • About Us
    • Careers
  • Latest
  • Search