![microsoft lync licensing microsoft lync licensing](https://www.manageengine.com/products/desktop-central/images/lync4.png)
- #MICROSOFT LYNC LICENSING SOFTWARE#
- #MICROSOFT LYNC LICENSING LICENSE#
- #MICROSOFT LYNC LICENSING PLUS#
- #MICROSOFT LYNC LICENSING WINDOWS#
#MICROSOFT LYNC LICENSING PLUS#
Then purchase the appropriate number of CALs.įor example, a customer who wants to deploy the Business Intelligence edition running in six VOSEs, each allocated with four virtual cores, would need to assign six SQL Server 2012 Business Intelligence server licences to that server, plus the CALs to allow access.įor SQL Server Standard and Enterprise editions you can licence individual VMs using the per-core model.
#MICROSOFT LYNC LICENSING LICENSE#
Simply purchase one server license for each VM running SQL Server software, regardless of the number of virtual processors allocated to the VM.
#MICROSOFT LYNC LICENSING WINDOWS#
I’m going to assume you’re running Windows Server 2012 Datacenter edition on these boxes just for simplicity and I haven’t included details of the VOSE OS.įor SQL Server Standard and Business Intelligence editions you can licence individual virtual machines (VMs) using the server + CAL model.
#MICROSOFT LYNC LICENSING SOFTWARE#
Regular readers of the licensing blog will be saying “I bet this has something to do with Software Assurance (SA)”. SQL Server Licensing in a virtual environment. Also you don’t require a separate CAL for every SQL Server a SQL Server 2012 CAL allows access to all the SQL Servers within the organisation.Ī simple way of determining the edition and licensing of SQL Server 2012 is below. SQL 2012 CALs will allow access to all previous versions of SQL Server. Licence the server(s), determine the number of unique users and/or devices accessing the SQL Server and purchase the appropriate number and type of CALs. See this link for the processors in question and what to do.įor server and CAL, SQL Server works in the same way as any other Microsoft server + CAL product. Certain AMD processors need to have a multiplication factor of 0.75 applied to the core count. So in our example above we would purchase four SQL Core licence SKUs to cover eight cores.ģ. SQL Server 2012 core licences are sold in packs of two: each SKU covers two processors. So if you have a dual-core, dual-processor machine you would need to count that server as a dual, four-core processor and purchase licences for eight cores, despite only having four cores in total.Ģ. You need a minimum of four core licences per processor. Once you have that you need to remember three things:ġ. Software partitioning doesn’t reduce the number of cores you need to licence. To find out the appropriate number of cores you need to licence, simply count the number of cores in each physical processor in the physical server. Currently SQL Server 2012 and BizTalk Server 2013 are the only Microsoft products licensed per-core. We are talking per-core here and not per-physical processor, unlike Windows Server 2012.
![microsoft lync licensing microsoft lync licensing](http://icons.iconarchive.com/icons/ziggy19/microsoft-office-mac-tilt/256/Lync-icon.png)
This is summarised below.īefore I present a little flowchart which might make you decision easier, let me clarify a few things about per-core licensing.
![microsoft lync licensing microsoft lync licensing](http://2xom5j4aqh9o3quhfzkge6t1.wpengine.netdna-cdn.com/wp-content/uploads/2017/06/O365-Admin.jpg)
The Enterprise edition is licensed per core (no CALs required), Business Intelligence is licensed per server and client access licence (CALs) and the Standard edition can be licensed using either method. SQL Server is available is three main editions Standard, Business intelligence and Enterprise. SQL Server Licensing in a physical environment. You’re going to approach licensing differently depending on whether you’re deploying SQL Server in a physical or virtual environment. However with SQL Server 2012 Microsoft has done a great deal of simplification so it’s easy to understand the basics. Just when you think Microsoft licensing is straightforward and you’ve got a pretty good grasp on it, along comes SQL Server which has historically been the exception to the licensing rules.