External Connector License Price
- Is the Windows Server External Connector available at the release of Windows Server 2016? Yes, the Windows Server External Connector license will still be available to license external users’ access to Windows Server. Also, an external connector is required for each Windows Server the external user is accessing.
- An External Connector license cost US$50,500 and provided the right for an unlimited number of nonemployee clients to access a single physical Exchange Server machine. If nonemployees accessed multiple physical Exchange servers, each of those physical servers required its own Exchange Server External Connector license.
I've just found something quite strange while talking with a Microsoft Licencing representative and I wanted to run this past the community to see if this is something that anyone is aware of a change.
I was asking a question around licencing SQL Server/ Windows Server which led to me being recommended an External Connector licence for a Website that does not use Windows Users.
Windows Server External Connector Software Assurance Open No level Government Qlfd Windows. Code, Product name, License type, Net price, Actions.
I boiled this down to the basic scenario of:
Server 1:
Windows Server 2008 R2, running IIS 7.5, using a custom public facing Website using an home grown authentication mechanism (i.e. not Local Windows Users, or AD users) where the number of users (authenticated or not) is indeterminate.
Server 2:
Windows Server 2008 R2, running SQL Server 2008 R2.
The Website on Server 1 connects to SQL Server on Server 2 using a SQL authenticated login.
The licencing that is required is:Windows Server Licence for Server 1Windows Server Licence for Server 2SQL Server 'Per Processor' LicenceAND An External Connector Licence for Server 2.
This seems preposterous as it triples the cost of the windows licence for Server 2. Also, as far as SQL Server is concerned, there are no multiple Clients connecting, only 1 'device' that then provides a massive 'Value-add' on top of just the data from SQL Server.
My question, has anyone come across this before? It seems like this is wrong as the above, I would imagine, is the most common scenario for most .NET software houses that create web sites, and, having worked for a few, I've never heard of this!
I've seen this question:
However, it's not really got enough information on the scenario etc. and also doesn't quote any proper resources.
I would appreciate it if someone could actually point to a section within a reputable site about this, rather than just a link to the generic 'Client licences' page.
Martin3 Answers
Just a few additions to the otherwise excellent previous answer:
each individual license covers 2 cores:This is wrong. Each core license covers one core, as you may expect. The fact is that the SKU, the product reference you may purchase, is a pack of 2 core licenses. This pack can be divided into 2 single core licenses if you need to when assigning your licenses to your servers. As a side note, I would be glad to know the name of the 'brilliant' guy who created this SKU at Microsoft, as it adds a lot of confusion and generates a lot more work to my industry, the Software Asset Management (SAM).
I would go with Microsoft on this since they are the ones that would do the software audit:This is wrong as well. Microsoft never does software audit on their own. They always delegate this to third parties. As a consequence, the inside knowledge of licensing rules is usually very poor at Microsoft and I strongly advice to ask licensing professionals instead, such as SAM consultants.
Regarding Martin's comment, the Microsoft Licensing people we deal with (an LAR) think differently:A LAR, or LSP as it is now their new name, is usually a pure reseller and its licensing knowledge is usually very poor also. Their goal is to sell the most, not to make sure their customers are compliant, and optimized even less. I am not surprised they think differently. Again, ask SAM professionals instead.
Best regards,Gilles
An External Connector License is in place of a Windows Server User/Device CAL:http://www.microsoft.com/licensing/about-licensing/client-access-license.aspxhttp://www.microsoft.com/licensing/about-licensing/product-licensing.aspx
An External Connector is defined as:'An External Connector (EC) license is an alternative to CALs for each server that external users will access. External users are users who are not employees or onsite contractors. 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 instances running. The right to run instances of the server software is licensed separately; the EC, like the CAL, simply permits access. EC licenses, like CALs, are version and functionality specific. They must be the same version or later than the server software being accessed. The decision on whether to acquire CALs or an EC for external users is primarily a financial one.'
A Server Processor/Core License allows unlimited connections - whether internal or external (as long as you cover all the cores in your machine). For the SQL Core license (separate from Server : times the number by 1 for Intel, and .75 for certain models of AMD): http://go.microsoft.com/fwlink/?LinkId=230678 (page 7-9).
Server 1: If it is a workload webserver, IIS does not require CAL's for external connectors - IIS is exempted ( http://microsoftlicensereview.com/category/external-connectors/ ). The Windows Server does require User/Device Server CALs (if it is licensed that way) for employees or onsite contractors. For offsite users who authenticate to the server, not only for website related information, if it makes more sense to purchase the external connector license rather than User/Device CALs for these users, then you would want to do that.
Server 2: In addition to similar license as above for this server, the SQL Server would require either: Per Core License (each individual license covers 2 cores, you need as many licenses as the core factor for your machine); OR 1 SQL Server license + User/Device Cals for all users who connect to the website on Site which is pulling SQL data.
This keeps you from doing multiplexing, which is described here:http://www.microsoft.com/licensing/about-licensing/briefs/multiplexing.aspxhttp://go.microsoft.com/fwlink/?LinkId=230678 (page 17).
Here is an article that explains it further (she mentions offsite contractors, which is different than onsite contractors - which would need a User/Device CAL):http://www.networkworld.com/community/blog/microsoft-cals-and-external-connector-license
So, it would appear that since the user is connecting to the SQL server via the web application on Server 1, and not authenticating to Server 2 (if Server 1 connects to SQL directly with string rather than authentication), it would not seem like the External Connector license is not needed on Server 2 (but I would go with Microsoft on this since they are the ones that would do the software audit).
Mere jeevan saathi 2006 full movie free download hd. Hope that helps.
You need everything you mentioned as well as an External Connector license for Server 1.
IMO Microsoft being expensive is a baseless myth. How much will you pay a system admin to manage this stuff over the next 3 years (the usual release cycle for these products)? These products are far easier to develop for, maintain and debug compared to open source alternatives.
MonstieurMonstieurNot the answer you're looking for? Browse other questions tagged sql-serverwindows-server or ask your own question.
Core licenses are sold in packs of two (a 2-pack of Core Licenses), and packs of 16 (a 16-pack of Core Licenses). Each processor needs to be licensed with a minimum of eight cores (four 2-pack Core Licenses). Each physical server, including single-processor servers, will need to be licensed with a minimum of 16 Core Licenses (eight 2-pack of Core Licenses or one 16-pack of Core Licenses). Additional cores can then be licensed in increments of two cores (one 2-pack of Core Licenses) for gradual increases in core density growth.
Windows Server Standard and Datacenter editions continue to require Windows Server CALs for every user or device accessing a server (see the Product Terms for exceptions), or Windows Server External Connector licenses for servers accessed by external users. In addition to the base Windows Server CAL or External Connector license, some functionalities will continue to require the purchase of an Additive Access License. These are CALs or External Connector licenses, which provide rights to access additional or advanced functionalities such as Remote Desktop Services or Active Directory Rights Management Services.
External Connector (ec) License Price
The Azure Hybrid Benefit lets you bring your on-premises Windows Server license with Software Assurance to Azure. Rather than paying the full price for a new Windows Server virtual machine, you will only pay the base compute rate.
Azure HUB enables customers’ use of Windows Server on Microsoft Azure through Azure Virtual Machines (“Base Instances”). Azure HUB does not include the cost of Base Instances, and Base Instances do not include Windows Server. Each set of 16 Windows Server core licenses with Software Assurance (and each Windows Server processor license with Software Assurance), entitles customers to use Windows Server on Microsoft Azure on up to 16 virtual cores allocated across two or fewer Azure Base Instances. Each additional set of 8 core licenses with Software Assurance entitles use on up to 8 virtual cores and one Base Instance.
In order to provide customers with a variety of options to license Windows Server, Microsoft makes licenses for Windows Server available to Service Providers for sale to customers as part of Service Provider solutions. This is done through agreement between Microsoft and Service Providers. Pricing for these Windows Server licenses that are provided by the Service Provider is set by the Service Provider.