Skip to main content

SharePoint 2013 Licensing model

SharePoint 2013 licensing model has changed bit for user scenarios. it has been slightly change from the SharePoint 2010 server user licensing model.

SharePoint Server should be license under two categories.

  • Server License
  • Client Access License (CAL)

Server License

Each SharePoint server in the farm should be license under SharePoint server license. Apart from the windows server licenses, SharePoint server should be licensed. This can be done when the time of installation of the SharePoint server.

The SQL servers in the SharePoint farm should be installed according to the SQL server licensing model.

Client Access License (CAL)

After that SharePoint farm should hold licenses for client access. These licenses are reviewed in the audit process and does not require any key in activation.

Depending on the user accessing organization requires to have CALs.

Intranet and Extranet CAL requirements

Assume organization setup a intranet and which is having users from internal AD , authentication providers. If all the user sources are with in the intranet and users are part of the organization; then each user needs a CAL to access the SharePoint server. CAL requirement is still valid for users who access the SharePoint server via internet.

Assume via authentication providers (Ex:- Membership Provider) , SharePoint is extended for Selected External Users (Named External Users) and Users are external and not part of the organization; thus no CAL is required for the user Access.

Internet CAL requirement

Assume SharePoint installation is as a public facing site and anonymous users are accessing the to view the content. thus these users does not require any CAL for accessing the content.

Reference : Microsoft

Labels:

Comments

Post a Comment

Popular posts from this blog

Complete guide to Install SharePoint in a Three Server Farm using AutpSPInstaller

This article will be divided to three sections Setting up the Environment and Service Accounts Getting Ready with AutoSPInstaller Online Configuring the XML using Online Editor and Installation Setting up the Environment and Service Accounts AutoSPInstaller Online is one of a great project that facilitate Automated SharePoint installation including Sharepoint 2010, 2013 and 2016. Auto SP Installer provides a powerful way to deploy and configure a single-server development environment to multiple-server SharePoint farm. Reference: https://autospinstaller.com/ Before doing anything we will set up the environment for SharePoint three server Farm. Will name these servers as SPWFE - Share Point Front End Server SPAPP - Share Point App server SPDB - DB server Please find the reference for SharePoint minimum requirement and practices from https://docs.microsoft.com/en-us/SharePoint/install/install-sharepoint-server-2016-across-multiple-servers For the the medium segregation, we have to create...
Post a Comment
Read more

How to Customize New Item Form to take parameters from Query String in the SharePoint 2010

In here I'm going to explain how to customize the SharePoint Item From to take parameters from Query String and set them as default values using SharePoint designer. Using this you can open a new Item From by providing parameters as query string. For an example you can customize one item Display form and taking query String Parameter from that and view New Item view for another list by providing default values using the Query String.     Steps Open the SharePoint designer and go to list and libraries and open the list that you want. Click the New and create a New Insert View by providing the name of the view.   Then created one will come to the list. then click and open the view. Then default New Item Screen will be loaded as follows. Then Delete the default list view and make that empty. You can delete the controls by selecting the area in the design view, If it fully cleared you can view the following message from the designer. Then go to SharePoint...
6 comments
Read more

Motion Eye Docker compose File

Docker compose files are comes in handy when considering container orchestration. Below example shows my docker compose files and folder structure. ---- Your Folder (motioneye)   -- etc   -- lib   -- docker-compose.yaml You can run the docker compose file using docker-compose -d , and etc and lib folder will be automatically populated in the initiation. --- Below shows the content of the docker-compose.yaml file. version: '3' services:   nodered:    image: "ccrisan/motioneye:master-amd64"    container_name: motioneye    restart: always    user: root    ports:      - 8765:8765    volumes:      - "/etc/localtime:/etc/localtime:ro"      - "./etc:/etc/motioneye"      - "./lib:/var/lib/motioneye"
Post a Comment
Read more