Thread: Licensing M$ products

Hi All,

I posted this in gen chit chat on the off-chance someone might know the answer to this despite it not being software used by web hosts...

Share Point

With regards to their licensing model I was slightly confused as to whether you need a license for each node (as in web server) that your running it on - even if its just for load balancing?

Or you only pay additional licenses if its multiple instances that are specific installs (i.e, dont point back to the original MSSQL db).

Cheers

Hmm, MS advised us that if you are running in AD authentication mode (i.e. not SQL forms etc) then you are up for CAL licensing, so you had better sit down.
Our best option was W2k3 Web front end(s), and SQL per processor license for the back ends. We tie the sites to the servers rather than provide NLB or failover, but were advised that W2k3 Std and NLB would be fine with base cals too. To be fair we've had different stories from the license re-sellers to MS, so take care.

Originally Posted by PeteK

then you are up for CAL licensing

That was my understanding, which is why despite being asked for it, we've avoided for now ...

Originally Posted by othellotech

That was my understanding, which is why despite being asked for it, we've avoided for now ...

Double checked the email, and thankfully it does confirm so long as your authentication is SQL based and not AD then user CALs are not required... (wipes brow somewhat...)

Originally Posted by PeteK

but were advised that W2k3 Std and NLB

Not sure about the licencing for this off the top of my head, but imho steer clear of NLB unless you want headaches for a wide variety of reasons. Don't get me wrong, I'm certainly not an MS basher (quite the opposite infact), but NLB is one thing that should never have been brought into this world.

Originally Posted by markcastle

Not sure about the licencing for this off the top of my head, but imho steer clear of NLB unless you want headaches for a wide variety of reasons. Don't get me wrong, I'm certainly not an MS basher (quite the opposite infact), but NLB is one thing that should never have been brought into this world.

Lord we wouldn't use it, hence having instances tied to W2k3 Web servers. The SQL is clustered, but front end is just split and in the event of hardware failure we would fix it or re-point the users to another front end server..