[THIN] Re: per device or per user 2003 licensing.
- From: "Joanne Determann" <joanne.determann@xxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Fri, 30 Jun 2006 06:38:30 -0400
Good idea, Rick. I will call them back today. I'm glad I read your rant.
I'll be happy to say "unacceptable" to MS.
________________________________
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Rick Mack
Sent: Thursday, June 29, 2006 4:16 PM
To: thin@xxxxxxxxxxxxx
Subject: RE: [THIN] per device or per user 2003 licensing.
Hi Joanne,
We've had this issue with a number of our customers.
The per-device licensing really doesn't work in any scenario where
machines are being rebuilt reasonably often, unless you're willing to
buy extra CALS to cover the overlap.
Microsoft could have used something a bit closer to how DHCP handles
address allocations but that'd be too easy. Or maybe a hardware ID that
is acually reproducible for a particular device (eg based on MAC address
which is kind of unique) so it keeps the same TS CAL? Or maybe just
concurrency licensing ?
Sorry, didn't mean to start ranting, but Microsoft have had years to
sort this out :-(
Per-user licensing is the easy way out for them at the moment because it
isn't enforced at all. So there are no licensing issues, YET!
However unless they supply you with replacement per-user TS CALs you
will actually be running in an unlicensed configuration in the event of
a software audit. In addition when per-user licensing starts being
enforced, I suspect that license management isn't going to be any easier
because the end result will be the same. Can you imagine per-user
licensing for an educational organisation or any large organisation ?
Microsoft actually have a legal responsibility with the per-device
licensing mechanism problems. At the point where it stops you from
carrying out your business, when you can prove that you have more CALs
then physical devices, they become legally liable. It isn't a bug, which
is well covered by their EULA, it's by design and it's broken.
Ask Microsoft support for more per-device TS CALs, for free. At first
they'll refuse and suggest you just rebuild the licensing database (go
back to scratch) and reload your CALs, activate etc. Point out to them
that that's not acceptable and that it's affecting your business. Insist
and you'll get them.
If enough people did that, we might just achieve something.
regards,
Rick
Ulrich Mack
Volante Systems
________________________________
From: thin-bounce@xxxxxxxxxxxxx on behalf of Joanne Determann
Sent: Fri 30/06/2006 1:30
To: thin@xxxxxxxxxxxxx
Subject: [THIN] per device or per user 2003 licensing.
I'm having an issue with my per device licensing mode. We have been
rebuilding clients like mad (switching OS and because summer
power/humidity issues things die) . Anyhow some of my devices had been
issued 2 or 3 licenses. And now I have about 15 licenses that are tied
up and so a couple of clients can't logon.
MS support recommend changing to per user so this wouldn't happen again.
Is this really the way to go?
Thanks,
Joanne
########################################################################
#############
This e-mail, including all attachments, may be confidential or
privileged. Confidentiality or privilege is not waived or lost because
this e-mail has been sent to you in error. If you are not the intended
recipient any use, disclosure or copying of this e-mail is prohibited.
If you have received it in error please notify the sender immediately by
reply e-mail and destroy all copies of this e-mail and any attachments.
All liability for direct and indirect loss arising from this e-mail and
any attachments is hereby disclaimed to the extent permitted by law.
########################################################################
#############
Other related posts: