Windows Forum

Ask something
Discussion Locked

Windows 2000 Server Licensing

0 helpful
11 replies

by ben

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

I have just deployed a Win2k Server, with 5 Win2k Pro. Clients, and 3 Win98 Clients. All is going remarkably swimmingly but... I keep getting reports that SMB Server is running out of licenses - I have 10 CALs configured for per server licensing. Also, in the Licence manager it tells me on the summary screen that 6 licences have been reached, but in the server details it says 13 - how is this possible with only 8 machines?? In the open sessions view, it tells me that I have six users connected and seven machines - with the [machinename]$ accounts - with user icons next to them?! I am not a trained server administrator but have had to do it because no-one else will. Any assistance, as ever, much appreciated!

Ben.

11 replies

by dc1

Switch your licensing to per seat. Per server licensing is based on connections being made to the server where as per seat is a client license.

by ben

See! I'm not going mad... Have (tentatively) checked with MS, but not on the known bugs list (apparently), and any further digging will levy charges (?150 UK!! - that's like a lot of dollars, right?)

Can we disable the license manager in 2K? I've not seen anything that implies this might be possible. I know I'm licenced, and surely manual tracking ought to be an option unless MS have another agenda here. Are we approaching the days when software usage and licensing will be automatically monitored, and violations reported, over the Internet - I fear this is not far off.

Anyway, think there is more discussion required on this topic so I'll leave the thread open for now.

Cheers chaps+chapesses,

B.

by ben

Is it as simple as that? In all the literature MS recommends that a small single server network like ours one should opt for per server. Not that I trust that MS have my best interests at heart, but will this really solve my problems? It's a one-off move as I understand it, and cannot be "undone". Please excuse my caution!

B.

by mckaytech

I have to disagree - I don't think it's just that simple.

I've been reviewing the licensing requirements in preparation for a W2K migration and while it is apparent that the licensing scheme is different for W2K than NT4, you're seeing some contradictory data that suggests to me that simply changing to "per seat" isn't going to correct the problem.

License Manager is correctly reporting the number of concurrent user sessions (6) but the SMB server is not. Historically, the best way to resolve such problems has just been to disable the License Manager and track the required licenses manually. That is not an option for W2K Terminal Services, but I believe it's still possible under plain ole W2K Server.

I would encourage you tofollow your caution and assume something else is going on before making the change to per-seat licensing. If I come across anything useful in my current research, I'll pass it on.

paul

by na_paul

I have seen this also, where each computer uses two licenses, one for the user and another for the computer. Both will use licensed connections until they run out and then use unlicensed connections.
No where have I seen (in any Microsoft literature or training or anywhere else) that you have to buy two licenses per user/computer combination.
Does anyone know what the deal is?
Changing to per seat mode does not change anything.

This discussion is closed to new replies.