Find threads, tags, and users Please let me know about windows server external connector license. Thank you. Comment Show 0. I told him they really need to talk to Microsoft about it, but they are kinda afraid if they've been running out of compliance for so long that Microsoft could come down hard on them.
And that particular line that Scott just quoted confused me even more on the EC I had read that one before and we had a laugh about it. If it's not for an internal user, and not for someone you're hosting things for, then who IS EC for? I mean, anyone that connects to your network, you're hosting services for them, even if it's just AD authentication!
I think that the term "hosting services for" means that you are not hosting them for yourself. For example, we need some sort of way to provide a remote desktop session to our accounting firm so that they can use our accounting software. We pay them to use this connection they don't pay us. Consultting firms are the other big user of the EC.
It's pretty much anyone that you pay that needs access to your existing network never anyone paying you and getting the connector as part of the service for which they pay. Microsoft mentions customers using this service and I am not sure when that would apply in a non-hosted scenario. I expect that if your friends' company were to contact Microsoft and ask to get help getting their licensing on track that Microsoft would help them out without back penalties.
Microsoft is always helpful, I've heard, to companies who are trying to do the right thing that and going after people attempting to pay and asking for help pretty much means that a judge will laugh at you if you try to really go after them - refusing to let them fix the license wouldn't be in anyone's interest.
So a 32 CPU would mean like K in licensing? My question is that even after you purchase per processor license, do you need to go ahead and get a external connector license? We asked this very question of our Microsoft LARS Large Account Reseller advisor, and the answer is 'if you have the per-processor licensing, then you do not need the external connector license'.
If you're users are known e. If these web users are only accessing the server to consume IIS services then I'm fairly sure that you don't need the connector license for your Windows box just look at the Web edition as an example. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.
Create a free Team What is Teams? Learn more. Purchasing a User CAL might make more sense if your company's employees need to have roaming access to the corporate network by using multiple devices, or from unknown devices, or if you simply have more devices than users in your organization. Device CALs. With a Device CAL, you purchase a CAL for every device that accesses your server, regardless of the number of users who use that device to access the server.
Device CALs may make more economic and administrative sense if your company has workers who share devices, for example, on different work shifts.
External Connectors. If you want external users—such as business partners, external contractors, or customers—to be able to access your network, you have two licensing options:. External Connector licensing. An EC license assigned to a server permits access by any number of external users, as long as that access is for the benefit of the licensee and not the external user.
Each physical server that external users access requires only one EC license regardless of the number of software instances running. An "instance" is an installed copy of software. The right to run instances of the server software is licensed separately; the EC, like the CAL, simply permits access. Under the Per Core model, when the server software is running in the physical OSE, you must license all physical cores on the server. To determine the number of core licenses you need, count the total number of physical cores for each processor on the server, and then multiply that number by the appropriate core factor.
You do not need to purchase additional CALs. Software licensed by core. Specialty Server licensing. Specialty Servers are server-only licenses that generally do not require CALs. Specialty Servers require a server license for each instance of the server software running on a server.
0コメント