Link to home
Start Free TrialLog in
Avatar of Walter Curtis
Walter CurtisFlag for United States of America

asked on

SharePoint 2016 Licensing - the same as 2013?

In SharePoint 2013 licensing was controlled at the user (or a container) level via PowerShell. This article describes how that is done:

 https://technet.microsoft.com/en-us/library/jj219627(v=office.15)

I think SharePoint 2016 is the same, but I can't find any confirming information from Microsoft. If anyone has a link to an official article from MS pertaining to the licensing model it would be appreciated.

Thanks
Avatar of Tim Edwards
Tim Edwards
Flag of Canada image

Avatar of Walter Curtis

ASKER

Thank Tim. But unfortunately that does not answer the question. The link in my post will explain the situation to you I think.


Have a good one...
ASKER CERTIFIED SOLUTION
Avatar of Greg Burns
Greg Burns
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks for the info Greg. I have not been able to test in 2016 so that is very good to know.

At my last company we used those settings and controlled licensing tightly. It works really well. You have an AD group for Enterprise licensing, and when you add a user you can see the Enterprise features being enabled and when the user is removed the features are disabled or gone totally from their menus. I am going to implement that now in 2016 but I wasn't able to find definitive information or able to test if it was still the same in 2016. You post makes me feel confident that it is still a part of SharePoint 2013.

Many thanks, I appreciate the help...
Thanks

btw, my last sentence about should say "Your" help.. and of course SharePoint 2016, not 2013.
My pleasure!  I didn't know that this feature actually trimmed menus and the user experience. I just thought users would get an error if they tried to access a site with the wrong licensing.
The UI of the features had different behavior depending upon what they were. Some of the more obvious changes were BI web parts. As standard user not all of the BI web parts were available, but with Enterprise license in use the web part were present. And other things like that. As I think about it, there may not have been anything grayed out, but I think some things that were clicked on may have thrown a popup stating they were not available because it was not licensed or something like that.

As I mentioned, you can assign the license to users and/or groups. I used an AD group so help desk could do it once I had it set up. Another cool thing, depends on the MS contract probably, but the licenses were month by month and the licenses could transfer to other users.

Thanks again for the help. Have a good one...