Configure licensing in SharePoint Server 2013

SharePoint 2013

Applies to: SharePoint Server 2013 Enterprise, SharePoint Server 2013 Standard

Topic Last Modified: 2016-12-16

Summary:Learn about new licensing functionality and how to configure licensing in SharePoint Server 2013.

The steps in this article apply to the Standard and Enterprise versions of SharePoint Server 2013.

In this article:

In Office SharePoint Server 2007 and SharePoint Server 2010, when companies purchased a SharePoint Server Enterprise client access license (CAL) and deployed a server running SharePoint Server Enterprise, all users who accessed that server could use the full enterpr ise feature set. There was no way to determine the CAL that a specific user had. The only way to ensure that only users who had an Enterprice CAL accessed Enterprise features was to have separate Enterprise and Standard server deployments.

In SharePoint 2013, farm administrators now can assign licenses to users and enable license checks. With this new functionality, you can ensure that only users with the appropriate license can use a specific feature. This SharePoint Server license implementation is managed by using new Windows PowerShell cmdlets. By default, licensing is disabled in SharePoint Server. Administrators can opt to enable it by using Windows PowerShell.

User licenses are "assigned" by mapping claims to a known type of license. For example, a claim can be an Active Directory Domain Services (AD DS) Security group. By mapping the "ContosoFinanceDept" security group to an "Enterprise" license, you assign an Enterprise license to all members of that group. Users who log on to SharePoint Server are assigned claims. SharePoint Server examines the claims of users to determine their license. If a user does not have a license to use a particular feature, that feature will be blocked at runtime for them.

You must use Windows PowerShell to create mappings for license types and to return user license types. There is no user interface for this feature.

To configure licensing support in SharePoint Server 2013, complete the following steps in this order:

  • Return a list of supported licenses

  • Create mapping objects

  • Add mapping objects

  • Enable licensing

To avoid licensing error messages, perform the Enable licensing step last.
To configure licensing by using Windows PowerShell
  1. Verify that you have the following memberships:

    • Securityadmin fixed server role on the SQL Server instance.

    • db_owner fixed database role on all databases that are to be updated.

    • Administrators group on the server on which you are running the Windows PowerShell cmdlets.

    An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 cmdlets.

    If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about Windows PowerShell permissions, see Add-SPShellAdmin.
  2. Start the SharePoint 2013 Management Shell.

    • For Windows Server 2008 R2:

      • On the Start menu, click All Programs, click Microsoft SharePoint 2013 Products, and then click SharePoint 2013 Management Shell.

    • For Windows Server 2012:

      1. On the Start screen, click SharePoint 2013 Management Shell.

        If SharePoint 2013 Management Shell is not on the Start screen:

      2. Right-click Computer, click All apps, and then click SharePoint 2013 Management Shell.

    For more information about how to interact with Windows Server 2012, see Common Management Tasks and Navigation in Windows Server 2012 R2 and Windows Server 2012.

  3. At the Windows PowerShell command prompt, type the following command:

    $a = New-SPUserLicenseMapping -SecurityGroup <yoursecuritygroup> -License Enterprise
    $a | Add-SPUserLicenseMapping


    • $a is the variable that stores the mapping object that is to be used as the input for the Add-SPUserLicenseMapping cmdlet.

    • <yoursecuritygroup> corresponds to a security group in Active Directory.

For more information, see Get-SPUserLicense Get-SPUserLicensing Add-SPUserLicenseMapping New-SPUserLicenseMapping Remove-SPUserLicenseMapping.

We recommend that you use Windows PowerShell when performing command-line administrative tasks. The Stsadm command-line tool has been deprecated, but is included to support compatibility with previous product versions.