Windows Forum

Ask something
Discussion Locked

Out of CALS on Windows 2000 Server

0 helpful
5 replies

by rguess

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

I have a Windows 2000 Active Directory Server and 2 Windows 2000 Terminal Servers.
The domain controller and 1 of the terminal servers have per connection licensing, bit the 2nd terminal server has per seat licensing. How can I change this to per connection like the rest of the servers. I am getting all kinds of CAL errors.

5 replies

by mark.thomson

In NT4 you could only go from per connection to per seat (not the other way round which was impossible unless you reinstalled NT4 server). It's likely to be the same in win2k besides here is a quote from the "Windows 2000 Resource Kit" -
"The Terminal Services component of Windows 2000 Server requires Per Seat licensing for the Windows 2000 Server Client Access License, except when you purchase the Windows 2000 Terminal Services Internet Connector License."

Sorry I couldn't be more helpful

by rkelly

The only way to convert per seat to per server licenses is to reinstall the operating system.

To do it any other way breaks your license agreement and could not be recommended.

Also notice that whilst you get loads of licensing errors you may not actually be breaking your license agreement! Per server licenses are allocated and then removed at logoff, where are per seat licenses continue to remain even in place even when people logoff. If you are worried about it conifgure a license pool and specify that this pool is used by all your users.

This discussion is closed to new replies.