I'm having a difficult time understanding and finding good information on Client Access Licenses. I've done a ton of reading and research so I know the basics. I know I want a Per Server setup which the server is already configured for. I have 20 Client Access Licenses. The server's main role is Active Directory using Group Policy, file sharing and anti-virus using Trend Micro SMB. I'm not running Terminal Services. When I go to control panel and chose Licenses, I have two options... Per Server or Per Seat. I chose Per server and click OK. It says that the number of concurrent licenses is Zero and I don't have an option to add additional licenses. How do I configure Windows 2003 Server R2 to allow me to add and manage licenses? Thanks.

I've been working with CALs since NT 3.51 and I've never had to bother with listing them in a domain controller. Terminal Server is an exception to that, as MS has a totally separate licensing function for TS CALs.http://support.microsoft.com/kb/814593Just out of curiosity, are you *sure* you want per server? In my experience, per seat is more user friendly. When you choose per server, the server cuts off the connections to it when the total # of licenses is reached. When you use per seat, the same user could be connected to the server from 5 different computers and it doesn't matter. It's the same user and the server will allow all connections.Basically, if you have the same users using your server day in and day out, you want Per Seat. If you have a constant shifting of people (let's say you have 3 shifts of 20 people working over a 24 hour period) and you *know* that none of those peoples' time logged in to the server will overlap, then you'd want 20 Per Server CALs.In my experience, MS has allowed customers to more or less be on the honor system when it comes to Windows Server CALs.

Max, Thanks for your help. I agree that Per seat is the best option for our environment. You clarified that very well. I was wondering if there was any harm in turning on License Logging so I can see how many licenses are being used? Thanks.

There's no harm in turning it on, but I think you'll be disappointed with what you see. Per seat license logging has always been very spotty and the info you get from the logging service isn't very usable. At least, that has always been my experience. I haven't tried license logging in Server 2003, though. Perhaps it has gotten better.Glad I could help.Max.