From our understanding of Microsoft SQL licensing, there are two options:
1) Server/CAL - this means one needs to buy MS SQL Server license and then a CAL per named user. Since this is for named user, that means no matter how AF manages connections between the AF Server and the SQL Server, the end user must have as many CAL as there are users (or devices).
2) Per processor - this means one needs to buy MS SQL Server license that is priced based on # of physical processors hosting the SQL Server. Note this is per physical processors and not # of cores. With this licensing model, you would not need to buy CAL's and thus removes the need to count and keep track of the # of users.
From reading through Microsoft’s Client Access License documentation, it appears as though a CAL would be required for each downstream user (ie: someone connecting via PI System Explorer):
I would suggest engaging in a conversation with your Microsoft Account Manager to discuss the details of their CAL licensing.
You may also like to reference: http://blogs.technet.com/b/volume-licensing/archive/2014/03/10/licensing-how-to-when-do-i-need-a-client-access-license-cal.aspx
By the same logic, does one also need Windows Server CALs to allow for users to remotely connect to a PI Data Archive using PI client tools (e.g., DataLink)?
1 of 1 people found this helpful
In accordance with Microsoft Server licensing, then 'yes'. As you are using services provided by a Windows Server (in particular and especially the Windows AD login) then you should have a Windows CAL for each remote client.
This isn't really an OSIsoft licensing issue though, this is Microsoft.
Note the brief at the top of the document:
If the workstations in your organization are networked, you likely depend on network server software to perform certain functions, such as file and print sharing. To access this server software legally, a Client Access License (CAL) may be required. A CAL is not a software product; rather, it is a license that gives a user the right to access the services of the server.
Of particular importance is to not that it doesn't say 'if you use Windows file and print sharing', it simply says '..depend on network server software..', this might be DHCP, DNS, AD etc etc.. if it's a Windows-based software service and doesn't have a specific exemption license model (like IIS, SQL) then you would require a Windows Server CAL for each person.