Contact us: +44 (0)1582 464 740


Contact us

UK No.
0370 4050508

Int'l No.
+44 (0)1582 464740

Ask us a question

Keep in Touch


Are you ready for Microsoft Windows Server 2016 licensing changes?

Please note this is an update to our previous blog: Microsoft Teases Us with Windows Server 2016 Licensing Details

When Microsoft Windows Server 2016 was introduced the licence metric changed from processor to physical cores.

To work out the licensing requirements the below data will be required for each physical server:

  • Processor count
  • Core count
  • Number of OSE running per Server

Microsoft Windows Server 2016 is sold in two-core packs (like SQL Server). Each pack costs approximately 1/8th of a current Windows Server 2012 licence.

The minimum requirements for core licences are 8 cores per physical processor and a minimum of 16 core licences per physical server.

However, the main ‘gotcha’ with this licence metric change is when your current agreement comes up for renewal. Existing customers who have Software Assurance will transition from processor based licensing to core based.

Microsoft will apply a conversion rate, which covers the minimum requirement of 8 core licences per processor and 16 core licences per physical server.

However, if your physical server has more cores than the minimum requirement you are eligible to receive additional core licence grants where you only pay Software Assurance.

Be aware that there are conditions that need to be met in order to receive additional core licence grants.

Other ‘gotchas’ to look out for are:

  • Unlike Windows Server 2012, 2016 Editions have different features beyond the number of OSE’s allowed per licence.
  • It is worth noting that for 2016 it no longer references Virtual OSE’s, only OSE’s.
  • Don’t forget that you still need your Windows CALs!

If you need help with your Microsoft Windows licensing why not join us on our Microsoft Training courses:

Licensing Essentials for Microsoft

Advanced Licensing for Microsoft

Alternatively, please contact ITAMS.

T:  03704 050508

Is SAM more aligned to Finance or IT?

Software Asset Management (SAM) is a business practice that involves managing and optimising the purchase, deployment, maintenance, utilisation and disposal of software applications within an organisation. To efficiently run SAM, support and interaction are required from a number of areas within the business:

  • Operations/IT need to provide data from discovery tools/Active Directory/Anti-Virus/SCCM etc.;
  • Operations/IT need to support, maintain and run any SAM tools and databases;
  • Commercial/Finance need to supply Purchase Order and Contract information;
  • Commercial/Finance will be the interface for software audits.

Although these stakeholders are responsible and accountable for the information required, it must be decided who will ultimately own the service line, govern it and create the policies.

The majority of the information that feeds SAM comes from tools that are managed by IT. Also, as well as SAM relying on hardware information, it can provide analysed data and reports back to IT to support refresh, maintenance, decommissioning, leasing, end of life and data quality etc. With this in mind it could be considered that SAM is more aligned to IT as that is where the data comes from and they also benefit from the analysis.

However, SAM is about software – including licensing, compliance and audits. If a piece of hardware is operating how it should but is not licensed correctly, it is not IT that will bear the financial burden. Consequently, it would make sense that the ownership of SAM sits with Finance.

SAM must be policed. Policies need to be written and adhered to by all stakeholders. There is significant service compliance and governance involved due to its cross functional nature. If there is a Service Integration and Management (SIAM) function in place at the company, its aim is to seamlessly integrate interdependent services from various internal and external service providers into an end-to-end service, in order to meet business requirements. SIAM should therefore police SAM however Finance would still be ultimately accountable.

To conclude, it is generally understood that SAM should be aligned to Finance due to the implications of the software finances. However, they cannot manage this alone and will need IT and other areas to be responsible and accountable for the data they provide and policies they must adhere to. A governing board will ensure this.

For any further help or advice around SAM, please contact ITAMS.

T:  03704 050508

What is an ELP?

ELP stands for Effective Licence Position and is related to a specific software vendor or product.

Being able to create an ELP is fundamental to keeping on top of your product compliance for audit defence and to support ongoing SAM activities such as optimisation and cost control.

Read Blog

Key Points to Consider When Looking for a SAM Service Provider

Many of our customers have a relationship with one or several SAM Service Providers to help with different parts of a SAM solution or to design and manage the entire solution, but it is often the case that the chosen provider(s) do not have the right capabilities to suit their requirements.

Read Blog

For further information on SAM Service Providers and how to select them, please sign up to receive our complimentary guide:

‘Appointing and Managing a SAM Service Provider’

The Core Components of SAM

Many organisations believe that a SAM Tool will solve all their SAM issues.

However, this is not the case.

For your organisation to be successful in SAM, the following five components of SAM are all key and should be considered carefully as part of your SAM programme.

Read Blog

For more information on how to successfully manage SAM within your organisation, download our guide:

‘Benchmark your SAM Position for Software Audits & Renegotiations’

The Importance of Designing and Implementing Effective SAM Processes

Many organisations attempt to manage their software licence compliance through a number of sporadic processes, procedures, tasks and activities split across different departments which are not centralised.

Implementing centralised SAM processes will enable your organisation to manage your software licence compliance more effectively and help you to achieve a mature SAM service by ensuring that the people, processes and policies within your organisation are aligned and that your organisation is working towards a common SAM strategy.

Read Blog

The BREXIT Effect

Have you considered what the potential effects on your software licensing costs could be following the UK’s decision to leave the EU?

Our latest blog looks at some of the key considerations you need to take into account following this historic decision.

Read Blog