Our production servers are hosted at a data-center, and are not on premises. 8 of us do access another server that is used for stage development prior to publishing to our production servers, and this server hosts VMs that imitate our production setup, however no customers connect to it. All 17 of us also do access a file server on premises that is running Server 2008 R2 Standard.

All 17 of us do access Exchange for email. We are running the Enterprise version on 3 physical servers.Īs for our actual employees, there are 17 of us, and approximately 8 of us access our production servers for administrative purposes, via 1 administrator account. The bulk of our servers are running 2008 R2, Standard. None of our customers have actual user accounts on our servers, except obviously in Active Directory and Exchange, for the email portion of our services. They do not authenticate with any of the servers that are hosting our services, except for the web server, and they are authenticating with accounts that we create for them in our web-suite. The customers only access the web-suite portion, over the internet.

There is a front-end web-suite hosted on a web server, whose data is stored in our SQL server, which is manipulated via the utility server as our software processes the incoming data. This software communicates with our back-end software that is hosted on our utility server, via both FTP and POP3 protocols, with the messaging portion being hosted on an Exchange server. It is my hope that one of you out there can help me, and I will be eternally grateful and shower you with spices for the rest of your days!īasically, we currently have around 200 customers that utilize our proprietary software that runs on computers we supply them. While the annoyingly simplistic scenarios found around the web that only go so far as explaining the obvious difference between user and device-based CALs is appreciated, I cannot, for the life of me, apply such explanations to our situation. As such, I have been trying to wrap my head around the client access portion of licensing as it relates to our particular situation, much to my agony and dismay! After being hired as a network admin at a SMB, I have come to realize that my predecessor has left us in such a state of licensing noncompliance that it literally keeps me awake at night in fear of the Microsoft men-in-black showing up at our doorstep.

Sql server 2008 r2 user cal