Wednesday, December 05, 2012 10:44 AM
I have a website on which users can create their own login credentials. The server environment consists of six front-end servers, running the website and each running a SQL server instance, and two clustered back-end servers running SQL server (each cluster consists of two servers). Al servers are running in the physical environment (no virtualization).
How many External connectors do I need?
- 10 EC's, one for each server
- 6 EC's, one for each front-end server. The back-end servers aren't beiing accessed by the users
- 4 EC's, for the back-end server only. The six front-end servers are running web server workloads
- 2 EC's, for the back-end servers, one per active/passive cluster. The six front-end servers are running web server workloads
- any other sugestion?
Wednesday, December 05, 2012 12:57 PM
Have you seen this thread Question about External Connector Licensing.
for OS Licensing:
- For licensing questions, I suggest contacting Microsoft Licensing Center for detailed explanation. http://www.microsoft.com/licensing/contact-us.aspx
- For licensing questions, please call 1-800-426-9400 (select option 4), Monday through Friday, 6:00 A.M. to 5:30 P.M. (PST) to speak directly to a Microsoft licensing specialist. Worldwide customers can use the Guide to Worldwide Microsoft Licensing Siteshttp://www.microsoft.com/licensing/index/worldwide.asp to find contact information in their locations.
Regards, Ravikumar P
Wednesday, December 05, 2012 1:26 PM
I'd already seen the thread you're pointing to. I don't think that information is relevent anymore because of the changes in the recent Product Use Rights and the Microsoft Product List of December 2012. In the Product List i found this:
Using Windows Server 2012 as a Web Server: When Windows Server 2012 Standard or Datacenter is used as a Web Server you do not need CALs to access the software. A “Web Workload” means:
Web Workload (Internet Web Solutions): “Internet Web solutions” are publicly accessible and consist solely of web pages, websites, web applications, web services, and/or POP3 mail serving. For clarity, access to content, information, and applications served by the software within an Internet Web solution is not limited to your or your affiliates’ employees.
You may use the software in ‘Internet Web Solutions’ to run:
- web server software (for example, Microsoft Internet Information Services), and management or security agents (for example, the System Center Operations Manager agent).
- database engine software (for example, Microsoft SQL Server) solely to support Internet Web solutions.
- the Domain Name System (DNS) service to provide resolution of Internet names to IP addresses as long as that is not the sole function of that instance of the software.
After reading this, I think I only need the EC's for the Back-end servers. The front-end server are purely running "Web workloads"...