Following the release of the productivity servers; Lync 2013, Exchange 2013, and especially SharePoint Server 2013 a common question that crosses our desk is, “how do I license Office Web Apps Server for the new 2013 products?” In this post, we will be covering the basic licensing of the new Office Web Apps Server.
With the consumerization of IT, and the proliferation of devices in the workplace, it is now as important as ever that the licensing model you use is delivering the most value to your business. Our volume licensing programs can offer the flexibility and improved manageability to ensure your CAL licensing model is optimally matched with your organization’s needs. If your business needs change and you want to switch from your current method of Client Access Licensing (CAL) there is an opportunity to switch from Device to User CALs or vice versa. That opportunity comes when you renew Software Assurance (SA) on your CALs.
What’s the difference, aren’t they both for disaster recovery? Fail-over Rights and “Cold” Disaster Recovery Rights serve two different, but similar purposes. For SQL Server, “Cold” Disaster Recovery (DR) Rights are a Software Assurance (SA) Benefit while Fail-over Rights do not require SA coverage, but to get the maximum benefit of Fail-over Rights you will want to consider SA coverage for your SQL Server licenses. In this post we will go into more detail on the differences and similarities between the two.
Understanding how your software is licensed and knowing what your rights are includes having an understanding of the licensing stack, knowing the licensing terms in various documents that apply to your use of the software, and how licensing documents affect one another. If you are a Volume Licensing customer, this is especially important to optimize your use rights.
Microsoft publishes the Product Use Rights, commonly known as the PUR, on a quarterly basis. Because the use rights and license terms change, knowing which PUR you should be using when evaluating a licensing model, contemplating a purchase or downgrade, and evaluating compliance is important. Here is a basic explanation.
What can I do when I am not ready to move to the latest product or I have a legacy application and need to run a prior version of Microsoft Software? I see only the latest products for sale.
Let us explain your Downgrade Rights!
A common question that comes across our desk, especially around new Product launches is: “I have active Software Assurance (SA) coverage on my licenses and a new version has just been released. My SA is about to expire, do I have rights to this new version?”