Question Locked

Best Licensing model for Windows 2003 server with Multiple User connections

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

I have a small network with around 10 users/XpProWorkstations, one windows 2003 STD RC2 server with a total of 15 CALS purchased

Each user runs with a locked down account, with additional accounts on the machine for tasks such as scheduled Backups, and running certain apps with additional rights (configured to access the server using the Locked down account user)

So each single user could in theory have 3+ active connections (from a single physical workstation) to the server (2 using the same userid, and the backup account using a seperate userid). Additionally note that ghost connections are sometimes a problem, where the user may have 2 or 3 extra connections show in CompMgmnt/sharedFolder/Session, that when you end them, a message about not being a valid session is displayed before they are removed (but which still are being counted towards the 15 CALS).

The server was configured on a "Per Server" basis (15 CALS entered); but now seems to be locked in a "Per user or device" basis (as the only option is now to add "Per User or Device" licenses - not sure what happened there - I was just going to increase the "Per server" cal count to get around this [as we are still hopefully legit with having more CALS than paired users/machines], and noticed that I couldn't)

Anyhow, Getting Licensing popup warnings on the server (15 "Per Server Purchased", reached 14 shown in the license manager); and after digging around in the event log have also seem some "No License Available for SMB"

We've tried to ensure that we're legit with the licenses; but we're still going a bit Nutty with these license issue, with some connections being rejected and causing instability.

I've read through the MS licensing, and the more I look into, the more confused I am

Anyone have any advice on what is would be the best licensing method for the above scenario?

Thanks

4 replies

by cg it

best practice: if users will only connect to 1 server, use device CALs.

If users will connect to more than one server use User Cals.

So if you have 1 server on the network running active directory and have 19 computers, then buy 19 device CALs. You can then have any # of users on the network as the CALs are for devices connecting to the server not users.

If you have 2 or more servers on the network, you buy as many user CALs as the users you have. That user CAL allows the user to connect to any of the servers on the network.

by wil_tmp

Hi CGIT

I hate MS licensing ? Makes my brain hurt every time I have to look at it... lol

I think it?s the combination of the type of license (User or Device), and then the License mode on the server (Per Server or Per user/Device) which is the root cause for the confusion that I'm having. Referring to ?Device CALS? and then ?User CALS? in the license type as different items, followed by the Server ?Per User or Device? as a single item?

So to reconfirm the 2 license types:

A) ?Device CALS? related to a single physical device (irrelevant to user accounts or sessions being used on said device) connected to a server with unlimited user session connections against the server. (As an example, we could have 1 Device CAL, assigned to the device on the server) and run windows Quick user Switching with 50 users logged into to the server without any licensing issue ? Sound right?)

B) ?User CALS? relate to a single user session being able to access a server which is not tied into the physical device (where each user session must have a corresponding CAL). Basically the user is allowed 1 connection from any device (but not concurrently without using additional User CALS)

Now how would the server ?Client Access Mode? ("Per User or Device" vrs "Per server") tie in to the above license types?

From what I?ve read, I?d want to go with ?Per User or Device Mode? which would allow me to have ?Device? or ?User? CALS connect up to multiple Servers concurrently. Which looks to be the better choice should another server be added later on with no additional CALS being added.

Sound about right?

PS. Any idea if you can migrate User Cals to Device Cals, or if it even matters ? (We have 3 sets of "5 W2k3 server CAL 2003 5 Ctl User CAL" in addition to the 5 Generic User/Device CALS)

Thanks for your responses

paul

by cg it

device CALs are great if you have a small[er] # of computers but lots of users AND only 1 server.

User CALs allow a user to connect to a # of servers on the network [more than 1 server]. you don't need a CAL for every server with user CALs.

the per seat and per server licensing is for the built in 5 CALs you get with the Windows Server operating system. You can change those only once. So say you opted for device CALs on a Windows Server 2003 Standard Edition because you had 1 server, small # of workstations but ran 2 shifts so you had a large # of users than computers.

So you grow and add a server to the network. you can opt to change from device to user CALs [for the built in 5 CALs] BUT you would have to buy user CALs [so you waste the device CALs but at this point you already probably had the ROI on them].

This discussion is closed to new replies.