Retail, Volume and OEM?

Discussion in 'Virtualization' started by Happpy, Apr 1, 2010.

  1. Happpy

    Happpy MDL Senior Member

    Jan 23, 2010
    275
    86
    10
  2. blackranger

    blackranger MDL Senior Member

    Dec 28, 2009
    466
    33
    10
    #2 blackranger, Apr 9, 2010
    Last edited: Apr 10, 2010
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. urie

    urie Moderator
    Staff Member

    May 21, 2007
    9,039
    3,388
    300
  4. SLICuser

    SLICuser MDL Novice

    Dec 26, 2009
    32
    3
    0
    Regarding Q4:
    With volume licenses there are many types but most fall in to two categories perpetual and SA (software assurance). All current MVL are considered upgrade license and have OEM / retail prerequisite to use. Some enterprises may have early MVL for 95 / NT4 or older that meets the prerequisite license. All MVL follow the licensee not hardware.
    SA licenses are unusually the cheapest, are non-transferable and expire in usually 1 or 3 years. For example Vista Enterprise 1year SA was only $3US per system.
    Perpetual license never expire, are meant to be non-transferable but have fallen under first sale release clauses in most countries. AKA are transferable under the law.

    Some things to be aware of with VA 2.0:
    MAK and KMS dial home to Microsoft every 180 days to reactivate. If a certain number of extra hits occur your key will be automatically black listed and in the MVLA there are clauses for “penalties’ that MS may demand from your enterprise if they feel you have been “negligent” with key security.

    The MAK are used on all systems and are activated and tracked by MS.
    The KMS server is usually ran on MAK system that is part of MVLA. By securing this Key Management Server even your KMS key becomes wild, it probably will not bring down you network unlike with MAK where your companies first notification that the key has become wild will be when all the systems go into reduced functionality mode.
    If you have multiple MVLA you need to keep you number of systems accurate. I had a client that had different MVLA for each facility and accidentally used the same key on two facilities, they did not discover this until after they had accidentally BL their own key, and both facilities went in to reduced functionally mode, needless to say the client dumped Shysta as their OS after this.

    The nightmare that VA 2.0 is the number one reason enterprises are not maintaining their SA and are adopting OEM SLP based images. A55h01e Ballmer tries to blame piracy for their lack of sales; in truth it is enterprises are not upgrading their MVL due to the VA 2.0 clauses. In simple terms avoid VA 2.0 at all costs.
     
  5. vivek.krishnan

    vivek.krishnan MDL Novice

    Dec 13, 2009
    48
    7
    0
    Its not MAC but MAK : multiple activation key.

    edit: @arddrea : you got it right; didnt see it.
     
  6. msln

    msln MDL Novice

    Sep 29, 2010
    3
    0
    0
    I dont think, all ativated MS windows are unlimit and forever.
    If MS check genuine, false, it will be deactivated,
    Take care!