Home > Archive > MSDN > January 2006 > Technical Limit for Activation
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Technical Limit for Activation
|
|
|
| Is there generally a technical limit to how many can be activated for MSDN
products such as Windows XP or 2003?
| |
|
|
|
| that of course is a legal limit which varies between programs. Partners can
have 100+
tim
"Jupiter Jones [MVP]" <jones_jupiter@hotnomail.com> wrote in message
news:Om8IDtFGGHA.3952@TK2MSFTNGP10.phx.gbl...
> 10
> Read your Master EULA for details, or see the EULA here:
> http://msdn.microsoft.com/subscriptions/licensing/
>
> --
> Jupiter Jones [MVP]
> http://www3.telus.net/dandemar
> http://www.dts-l.org
>
>
> "MARCK" <marck@msn.com> wrote in message
> news:OrUZUUFGGHA.3176@TK2MSFTNGP12.phx.gbl...
>
>
| |
| Ronny Ong 2006-01-17, 6:57 pm |
| No, the question was about technical limit for activations, not number of
licenses. Sorry to pick nits but oversimplified statements like yours can
lead to misconceptions.
When using Product Keys supplied by MSDN Subscription, even partners are
subject to the 10 activation limit. However, partners at the Certified
Partner and Gold Certified Partner level receive Volume License keys (from
the Partner web site, in addition to the keys supplied by MSDN
Subscriptions) which means there is no technical limit for activations but
only when they use their VL. Partners at lower levels (Registered Member and
Empower) do not receive VL keys nor VL media nor access to VL media.
In terms of licenses, your reference to 100+ only applies to Gold Certified
Partners. Certified Partners generally receive 1-25 licenses for
internal/development/testing usage and 100 for training (i.e. classroom
setup) purposes. There are ways for Certified Partners to obtain additional
grants for internal/dev/test but the max total can never exceed 100.
Partners at the Registered Member level receive no licenses. At the Empower
level, 5 licenses are granted but fulfillment is strictly via 1 MSDN
subscription. Therefore, Empower activations are still limited to 10. All of
this paragraph is based on the U.S. The Partner program can vary in
different countries, but I don't believe there are any regions which receive
materially higher benefits at any level.
Furthermore, Partner licenses cannot be compared to regular licensing
because Partner licenses are time-limited. All other Microsoft licensing
(Retail, Open Business, Open Volume, Select, Government, Academic, etc.) is
perpetual. MSDN Subscribers who purchase through any of these channels will
never lose the right to use (for dev purposes) software received during
their subscription term, even after it expires. When a Partner exits the
program, it forfeits all rights to use software received during Partner
program membership. Existing installations would not stop working but they
would become illegal to continue using at that point.
"Tim" <tim> wrote in message news:OQIEQT0GGHA.2472@TK2MSFTNGP10.phx.gbl...
> that of course is a legal limit which varies between programs. Partners
> can have 100+
>
> tim
>
> "Jupiter Jones [MVP]" <jones_jupiter@hotnomail.com> wrote in message
> news:Om8IDtFGGHA.3952@TK2MSFTNGP10.phx.gbl...
>
>
| |
| Peter Oliphant 2006-01-18, 6:57 pm |
| Could someone please tell me when we started needing to hire a damn lawyer
just to understand the ramifications of installing software? I think all
these rules about installation rights are just outrageously way too complex.
And kind of ridiculous, since this can't be 'policed' very affectively (much
like the tree-sound anacdote, if a person installs a piece of software
without proper authority is this EFFECTIVELY a violation if nobody else can
detect this?).
[I actually wrote up a way to cheat, and then thought better of doing so, so
I deleted it! :)]
I still don't know what one does if they buy a new computer. I would hope
that if I buy, say, Visual Studio, and decide to upgrade or replace my
current computer that I don't have to buy another copy of Visual Studio. But
one can do this without removing from old system. That's because one very
good reason to get a new computer is that the old computer died, and is no
longer functional.
I assume transfering to a new computer therefore requires 'sweet talking' MS
into letting you register the software to your new computer. But I feel this
is too intrusive. Especially since, in my experience, MS sometimes asks for
too much info. I recently purchased a copy of Works Suite 2005. I was rather
appalled that, since I HAVE to register the product to use it after 30 days,
that a REQUIRED piece of information I had to give to complete the
registration was how many children I have! How is that any of MS's business,
and why do they have any right to ask this when I'm purchasing from them
(i.e, the money flows in their direction)? If I was asked this in an
interview for a job I could sue the company! And there is no warning on the
package: "To use this software you must give up personal details about your
family".
Anyway. MS needs to figure out a way to stop being so nosey and cumbersome
in their registration. I understand why they need to do some of this in
order to reduce piracy, but sometimes the cure can be worse than the
disease... ; )
[==P==]
"Ronny Ong" <ronnyong@killspam-bigfoot.com> wrote in message
news:ej3Hr83GGHA.140@TK2MSFTNGP12.phx.gbl...
> No, the question was about technical limit for activations, not number of
> licenses. Sorry to pick nits but oversimplified statements like yours can
> lead to misconceptions.
>
> When using Product Keys supplied by MSDN Subscription, even partners are
> subject to the 10 activation limit. However, partners at the Certified
> Partner and Gold Certified Partner level receive Volume License keys (from
> the Partner web site, in addition to the keys supplied by MSDN
> Subscriptions) which means there is no technical limit for activations but
> only when they use their VL. Partners at lower levels (Registered Member
> and Empower) do not receive VL keys nor VL media nor access to VL media.
>
> In terms of licenses, your reference to 100+ only applies to Gold
> Certified Partners. Certified Partners generally receive 1-25 licenses for
> internal/development/testing usage and 100 for training (i.e. classroom
> setup) purposes. There are ways for Certified Partners to obtain
> additional grants for internal/dev/test but the max total can never exceed
> 100. Partners at the Registered Member level receive no licenses. At the
> Empower level, 5 licenses are granted but fulfillment is strictly via 1
> MSDN subscription. Therefore, Empower activations are still limited to 10.
> All of this paragraph is based on the U.S. The Partner program can vary in
> different countries, but I don't believe there are any regions which
> receive materially higher benefits at any level.
>
> Furthermore, Partner licenses cannot be compared to regular licensing
> because Partner licenses are time-limited. All other Microsoft licensing
> (Retail, Open Business, Open Volume, Select, Government, Academic, etc.)
> is perpetual. MSDN Subscribers who purchase through any of these channels
> will never lose the right to use (for dev purposes) software received
> during their subscription term, even after it expires. When a Partner
> exits the program, it forfeits all rights to use software received during
> Partner program membership. Existing installations would not stop working
> but they would become illegal to continue using at that point.
>
>
> "Tim" <tim> wrote in message news:OQIEQT0GGHA.2472@TK2MSFTNGP10.phx.gbl...
>
>
| |
| Ronny Ong 2006-01-18, 9:55 pm |
| "Peter Oliphant" <poliphant@RoundTripInc.com> wrote in message
news:OwxmmVIHGHA.344@TK2MSFTNGP09.phx.gbl...
> Could someone please tell me when we started needing to hire a damn lawyer
> just to understand the ramifications of installing software? I think all
> these rules about installation rights are just outrageously way too
> complex.
I think you completely missed the topic of my post. I was talking about
partner-specific terms. These apply only to members of Microsoft's Partner
programs. If you are not a partner, then none of it applies to you. If you
are a partner, then you would encounter legal agreements all the time, in
the course of doing business.
> I still don't know what one does if they buy a new computer. I would hope
> that if I buy, say, Visual Studio, and decide to upgrade or replace my
> current computer that I don't have to buy another copy of Visual Studio.
> But
We were talking about Product Activation, which only applies to Windows and
Office. There is nothing in Visual Studio software which prevents you from
installing it a million times on a million computers. As long as you are the
only person using it, that's all it takes to comply with MSDN licensing.
That's pretty simple.
> I assume transfering to a new computer therefore requires 'sweet talking'
> MS into letting you register the software to your new computer. But I feel
> this
Except for certain free downloads which require registration before
downloading, there are absolutely no Microsoft products which require
REGISTRATION, and there never have been. You are confusing REGISTRATION with
ACTIVATION. Again, Windows and Office require ACTIVATION, but the ONLY
required information for ACTIVATION is Country. That's it. No name, no
address, no nothing else.
> is too intrusive. Especially since, in my experience, MS sometimes asks
> for too much info. I recently purchased a copy of Works Suite 2005. I was
> rather appalled that, since I HAVE to register the product to use it after
> 30 days, that a REQUIRED piece of information I had to give to complete
> the registration was how many children I have! How is that any of MS's
> business,
I'm sorry but you are definitely mistaken about several things. In Works
Suite 2005, only Word requires activation (because it originates from
Office). The ONLY required information for activation is Country.
There is an OPTIONAL registration process available in Works Suite 2005. If
you choose to begin the registration process, then certain fields are
required by the registration form, but you do NOT have to register at all if
you merely want to use the software. If you had actually read the screen
prompts instead of clicking arbitrarily and then jumping to conclusions as
soon as you saw a form, you would have seen that Microsoft recommends
registration but does not require it. This is a common practice by all major
software publishers.
| |
| Homer J. Simpson 2006-01-19, 6:57 pm |
| > that a REQUIRED piece of information I had to give to complete the
> registration was how many children I have! How is that any of MS's
> business,
Good grief, this is was a registration form for MS Works?
This is *Microsoft*, not the IRS. Tell 'em you're a student, you made $600
last year and you have 26 children.
> started needing to hire a damn lawyer just to understand the ramifications
> of installing software
[...]
> If I was asked this in an interview for a job I could sue the company
At the risk of getting flamed for this...you must be an American.
RELAX! They're not out to get you. Not everything ends up in ligitation.
| |
| Peter Oliphant 2006-01-19, 6:57 pm |
| >>This is *Microsoft*, not the IRS. Tell 'em you're a student, you made
How did you know? ; ) LOL
[==P==]
"Homer J. Simpson" <root@127.0.0.1> wrote in message
news:OHq3HoQHGHA.240@TK2MSFTNGP11.phx.gbl...[color=darkred]
>
> Good grief, this is was a registration form for MS Works?
>
> This is *Microsoft*, not the IRS. Tell 'em you're a student, you made
> $600 last year and you have 26 children.
>
>
>
>
> [...]
>
> At the risk of getting flamed for this...you must be an American.
>
> RELAX! They're not out to get you. Not everything ends up in ligitation.
>
>
| |
| Peter Oliphant 2006-01-19, 6:57 pm |
| Hi Ronny,
Didn't miss your point, had a point of my own to share that this thread
reminded me of . Didn't mean to reply to you directly, I was replying more
to the thread as a whole, but I had to attach it somewhere... : )
[==P==]
"Ronny Ong" <ronnyong@killspam-bigfoot.com> wrote in message
news:eWviYRJHGHA.2940@tk2msftngp13.phx.gbl...
> "Peter Oliphant" <poliphant@RoundTripInc.com> wrote in message
> news:OwxmmVIHGHA.344@TK2MSFTNGP09.phx.gbl...
>
> I think you completely missed the topic of my post. I was talking about
> partner-specific terms. These apply only to members of Microsoft's Partner
> programs. If you are not a partner, then none of it applies to you. If you
> are a partner, then you would encounter legal agreements all the time, in
> the course of doing business.
>
>
> We were talking about Product Activation, which only applies to Windows
> and Office. There is nothing in Visual Studio software which prevents you
> from installing it a million times on a million computers. As long as you
> are the only person using it, that's all it takes to comply with MSDN
> licensing. That's pretty simple.
>
>
> Except for certain free downloads which require registration before
> downloading, there are absolutely no Microsoft products which require
> REGISTRATION, and there never have been. You are confusing REGISTRATION
> with ACTIVATION. Again, Windows and Office require ACTIVATION, but the
> ONLY required information for ACTIVATION is Country. That's it. No name,
> no address, no nothing else.
>
>
> I'm sorry but you are definitely mistaken about several things. In Works
> Suite 2005, only Word requires activation (because it originates from
> Office). The ONLY required information for activation is Country.
>
> There is an OPTIONAL registration process available in Works Suite 2005.
> If you choose to begin the registration process, then certain fields are
> required by the registration form, but you do NOT have to register at all
> if you merely want to use the software. If you had actually read the
> screen prompts instead of clicking arbitrarily and then jumping to
> conclusions as soon as you saw a form, you would have seen that Microsoft
> recommends registration but does not require it. This is a common practice
> by all major software publishers.
>
>
>
|
|
|
|
|