Windows Forum

Ask something
Discussion Locked

Per Seat versus Per Server

0 helpful
9 replies

by adam a.

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a site that is running Windows NT4 SP6a with 9 Win9x workstations. We have a 10 user license set at Per Server. We also have SQL Server 7.0 installed on this same same server which also has a 10 user Per Server license.

Usually, in this situation, I'd be fine with Per Seat as it is unlikely that this site will grow beyond 1 server and 9 users for the next year or two (rural location).

Extra licenses seem to be used up when people try to print or when they try to access a VB runtime app that queries an SQL database we have running.

Should I be using per seat or per server? Or a combination of both? (ie: Per seat for NT and per server for SQL?)

Cheers in Advance
AA

9 replies

by jlouis45

it is good to use per seat license than per server. Per seat would mean that in case anybody is not using that resource but still can logon the the network and once the user has exited from the application you get a license so that the other can useit. But when you say per server then irrespective of the client seats your license would be used up.

by kthurston

In almost any case, I would choose per seat licencing. It will allow you to expand with greater ease and management capabilities. When running in per seat mode, the client holds the licence so the server doesn't have to. This way any of your clientscan connect to any resource at any time they need. Just be sure you have all of your Client Access Licenses in order.

by Member 35772270

I would try the per seat option and if that didn't clear up the problem, I would consider turning the License monitoring service off as long as I stay legal.

by adam a.

Changed to per seat and still getting license violations. One thing I HAVE noticed, though...

On this site, some bright guy decided that all nine users should use the same NT account (user). So at any one given time, you can expect the user 'USER' to be concurrently logged in on nine PCs. I don't know if that contributes to problem, though.

by adam a.

hmm.. forgot all about this one.

All answers were helpful, but in the end I went with per seat for NT and per server for SQL (as our software uses it a little different, I suspect).

This discussion is closed to new replies.