Question Locked

MS server CAL question

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

Greetings all,

Got a Windows2003 server with 5 CALS.

Problem, it was set for per device instead of per seat.

[b]Can I change this on-the-fly?[/b]

There is an average of 2 or 3 people logged in during busy times.

There are 11 total users (counting Administrator) and the server is bitch'en at me over this. Has been that way for years.

[b]Error message in Event Monitor:[/b]

[i]"Source:LicenseServer
Computer:HQSQL

The product Windows Server is out of Licenses. Use Licensing from the Administrative Tools folder for more information on which users are out of compliance and how many licenses should be purchased."[/i]

In the Licensing, it lists 11 users, and all 11 have the yellow triangle with the "!".

Licensing mode is per user.

31 replies

by ---tk---

change it on the fly... I recently did, go into terminal services configuration and click on "server settings", you should see it.

by jdclyde

I just didn't want to break it.

Did I mention I can find the software and invoice, but not the actual license for this?

Second question, I used Magic Jellybean to pull the server key, is there a separate number for the extra cals?

by cmiller5400

Unless they are Terminal Services CAL's, that's another ball game.

by jdclyde

don't look down your nose at us winders people! :p

by jdclyde

This server has 5 cal windows and 5 cal sql2005.

by jdclyde

the more I read the MS site, the less I understood where I stood with this.... :D

by ---tk---

I feel that... I researched the hell out of it a while back, and MS seems to give you the run around with it all.... One page they tell you this and the other page its something different. I have a friend that had to go through something like this. Ill send him an email and see how he dealt with it.. From what I remember he actually had to call MS to get the numbers or re-issued numbers (dont quote me on that though LOL).

by Member 25348569

And told you Jack Sh:t... Where, I ask myself, is the downside?

OK, I'm racked by thumbguilt so I will read on.

:D

by shasca

We don't even try to figure it out anymore. we just contact ASAP and tell them what we need, # we need and let them figure it out for us. They will have to answer to MS if it's wrong. We are kinda whimpy tho.

by darryl~

Q. Will I be allowed to switch between Windows Device CALs and
Windows User CALs? What about TS CALs?

A. If your Windows CALs are covered under Software Assurance (SA),
you have a one-time right to convert Device CALs to User CALs mid-
contract. You can also convert those Windows CALs from Device CALs
to User CALs, or vice versa, when you renew your SA contract. If
your Windows CALs are not covered under SA, you may not switch;
your choice is permanent. This also applies to TS CALs.

And really, there shouldn't be a problem at all:
All TS CALs have an expiration date of 52-89 days. Licenses that
are not used (because the client does not connect to the TS
anymore) will automatically be returned to the LS after the
expiration date. In the meantime, your new clients
will get a temporary TS CAL, which is valid for 90 days.

Note that these time periods are choosen to make sure that your
temporary license lasts long enough for the old license to become
available again. So if you are reaching the end of the 90 day
temporary license period without having TS CALs available, it
means that you have, at least during some time period, connected
with more clients than you have licenses, and you simply have to
buy extra TS CALs.

by jdclyde

that I am scurrying through...... :D

Every bit helps. If nothing else, when/if I do have to call MS I can sound like I almost know what I am talking about.... ;\

by jdclyde

is the damage has already been done, years ago.

The only paper trail I have are invoices. :(

by shasca

You need to bounce it off a MS authorized vendor for compliance. Nun of us dolts will ever be able to fully understand MS Lie-sensing. CYA is your friend.

We both know the chances of an MS audit are nill, but we all still need to do what ever we can to be compliant. Get some help from a pro. You won't regret it

by cg it

W2003 comes with 5 built in. you make those per device or per user. If you choose one and later want to change you can but only once.

Additional CALs are purchased per device or per user. These you can not change. TS CALs are totally seperate from Server CALs.

unless your server hosts all services [one server to rule all] your are restricted to what the CALs are by the types of CALs you buy [exclude the built in CALs which can only be changed once, and the TS CALs].

Since your a multi-server environment, you should only buy user CALs.

Rule of Thumbs: uses access only one server = device CAL
users access more than one server = user CAL
Terminal Server, buy TS CALs for the Terminal Server [which comes with 5 built in CALs under the W2003 Server base O/S but are not TS CALS.

by jdclyde

users that access multiple two servers, but only a few users at a time.

we already have at least 5 cals purchased per server.

question, if a server dies, i don't suppose we can transfer the 5 cals, can we? :D oh wait, MS we are talking so of course we can't.....

by cg it

their like licenses. As long as you don't use OEM :) and you have the correct # can't see why not.

Remember, the server has built in licenses , 5 ea. soooo.... if the server dies and you move to new hardware, no problem with the CALs. you buy extra CALs which are really licenses [use to come on floppys no less]. you load em up and all is good.

Server dies and you restore from backup... no problems, server dies and you do a fresh install, no problems, server dies and you move to new hardware, no problem.

But if you install the CALs and try to do it again on another network, you've got problems. The licensing server service will not like it.

by cg it

Its the # of servers users will access on a network.

Device CALs work only for 1 server access. User CALs work for multiple server access. User CALs do not work for Terminal Server access. gotta have Terminal Server CALs.

If you have more than 1 server users will be accessing, you should purchase or have purchased User CALs.

by jdclyde

12 users might access the same server, but never more than three at a time.

this is one big clusterphuck.

by cg it

12 users accessing more than 1 server 12 user CALs.

12 users accessing more than 1 server and all accessing a TS server, 12 user CALs and 12 TS CALs.

by the 'g-man.'

Device CAL's - Used per device to access x servers - a device can be a PC, phone or whatever.

User Cal's - Used per user to access x servers - a user is always a person on any device.

The highest number of which is what you will normally need to cover for basic server access.

Why both - sometimes you may have more or less devices to users (or vice versa) so it covers both.

You could have 100 PC's and only 1 user cal, thing is only one user could use all those machines.

You could have 100 users and only 1 device cal, that would be fine but then why have 100 users to 1 machine - university's!!

by jdclyde

Right now, it is set per user (right?) instead of per device.

It has been this way for two years now.

Other than getting an error message to ignore, does this really hurt ANYTHING on the server?

by cg it

but like XP in a workgroup, you hit the limit of connections, the next one won't be able to connect.

by ---tk---

My friend replied, "If he has the invoice, then he should have a login to the eOpen site
that Microsoft provides. This will have all of the information that he'll need for his documentation."

This discussion is closed to new replies.