"After many months of waiting, Microsoft finally released the Beta 3 version of Windows Server 2008 (previously codenamed 'Longhorn'), a major milestone pre-release version of the next version of Windows Server (more recently, a CTP, or Community Technical Preview, version was distributed to beta testers in June 2008). Windows Server 2008 has evolved quite a bit over time, and though the project hasn't suffered from the many feature drops and problems that dogged Windows Vista, there are certainly a few surprises in Beta 3 and the June CTP. Here's what you need to know about Windows Server 2008."
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-08-26
Is this all what your MS salesman have told you or what you have come up with yourself?
And I'm not sure what you are doing with IIS that would require you to have server CAL's to connect to it.
Many websites run IIS as their webserver and they certainly don't have CAL's for every single visitor.
And in cases where that webserver has SQL server in the backend, they certainly don't have SQL CAL's for every single visitor.
If you insist on what you are saying, I can only suggest you have a long talk with your MS salesman to clear up all the questions regarding your setup. Is this salesman someone from MS or from some company that resells licenses btw?
In either case, I'd get a second opinion from someone that's independent of the first, and if possible, make sure at least one of them is actually from MS. Obviously you shouldn't tell either that you talk to the other.
Member since:
2006-11-30
in my setup, the clients connect to IIS which in turn connects to sql. IIS uses a predefined SQL account. When the clients connect to IIS they also supply a predifined windows server user so that the dll which is hosted in IIS could be run. The dll handles all sql traffic.
So as you can see, the clients don't connect to the sql server directly. The only difference between your suggested setup and mine is that in my setup A and B are the same machine.
Putting "proxys" between clients and a server doesn't reduce the number of cals required!!
So I still need 20 SQL cal's, because I need cals for all machines that connect to the sql server.
I also need 20 windows server cals because the client machines connect to IIS.