We use windows XP embedded thin clients and we recently re-imaged all of the thin clients. Now I am getting error messages about not enough terminal server licenses. I got it once from my home computer when I connected in to look at a machine, and once from a classroom machine that should have already had a valid license. However, I am the only person getting this message. I also received a message that the license server could not be contacted once, but again I am the only person getting this message and it only happened once.
From my own understanding, I should be ok on TS cals because the newly imaged thin clients should have temporary licenses until the old licenses expire. And that seems to be the case, no one has had any problems except me.
Now for the questions, why am I receiving messages like this, how can I make sure that temporary licenses are being handed out and that they are going to cover me, and are there any circumstances in which my users would start seeing these messages?
It sounds like you are using Per Device licensing. What's happened is the old license that WAS issues to the thin clients is still considered in use until it actually expired. So, now you have potentially re-issued licenses to those devices and any others your users have used. I actually had the same issue, because our users travel a fair bit and were connecting in from all over the place, leaving our precious licenses wherever they went. I flipped to Per User licensing and have NEVER had the problem since.
You can check under the Terminal Server Licensing console to see how your licenses are being dished out. I can't imagine you are the only person seeing this message, unless you've got your license count THAT close. Your users could very likely start seeing this message if you just recently reimaged those thin clients. After 90 days you can be fairly safe in assuming all the old licenses will have expired.
Dan
Why is it called "Common Sense"? It doesn't seem all that common!