Per Seat and Per Server

[Peter]

Hi,

I have 2 servers, an SBS Windows 2000 server and an ordinary Windows 2000
server. The SBS server has 35 CAL's and the Windows 2000 server has 25
CAL's. The SBS server is an Exchange and Fax server whereas the Windows
2000 server is a file server. I have noticed that the Windows 2000 server
often prompts that have exceeded the maximum number of connections when over
25 computers access the network drive which is on the Windows 2000 machine.

Will changing the licensing mode from Per Server to Per Seat on the Windows
2000 allow it to use the 35 CAL's that is on the SBS Windows 2000 server?

Why is there such a thing as Per Server licensing mode when per seat is most
economical and there are no server products that are exclusively limited to
Per Server mode?

Thanks.

Peter

 

[\Richard McCall [MSFT]\]

Yes. The windows 2000 server is in Per Server mode with 25 licenses. This is
a concurrent connection limit and only 25 connections can be made. Change
the server to Per Seat does not restrict the server to a concurrent
connection limit.

 

[Lanwench [MVP - Exchange]]

My advice? Disable license logging (I think you can do this even in SBS) and
keep track of your licenses manually. The service is buggy, and is not
mandatory. You will be considered to be running in "per seat" mode if you
disable the service.

Check in microsoft.public.backoffice.smallbiz2000 to make sure you can do
this in SBS....