| Revision as of 10:21, 5 December 2006 editNorthgrove (talk | contribs)Extended confirmed users2,905 editsmNo edit summary← Previous edit | Revision as of 16:19, 22 January 2007 edit undoSchmuckyTheCat (talk | contribs)Extended confirmed users, Pending changes reviewers, Rollbackers23,945 edits re-order sectionsNext edit → | ||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| '''Volume License key''' ('''VLK''') is the term used by ] to denote the ] used when installing ] licensed under Volume Licensing, which allows a single product key to be used for multiple installations. This form of licensing is typically used in ], ], and ] institutions, with prices for Volume Licensing varying depending on the type and size of the setting. Microsoft software available through the Volume License program include ], ], ] and many others. | '''Volume License key''' ('''VLK''') is the term used by ] to denote the ] used when installing ] licensed under Volume Licensing, which allows a single product key to be used for multiple installations. This form of licensing is typically used in ], ], and ] institutions, with prices for Volume Licensing varying depending on the type and size of the setting. Microsoft software available through the Volume License program include ], ], ] and many others. | ||
| ⚫ | Since Volume Licensing bypasses ], VLKs have been exploited by ] since the advent of this service. The ] key is a prominent example of VLK exploitation. Although to some this may seem like an easy way to circumvent ]'s ] feature, each VLK is uniquely linked to the company from which it was purchased. Therefore, should the software be installed on more computers than it was licensed, Microsoft can hold the company responsible, and ] the product key in extreme cases. | ||
| ==Volume Activation 2.0== | ==Volume Activation 2.0== | ||
| Starting with ], VLKs will be replaced with Multiple Activation Keys (MAKs) that either activate copies through a local Key Management Server (KMS), which in turn reports back license usage to Microsoft, or activates directly in communication with Microsoft. Hosts activated via a KMS have to report back to that ] once every 180 days. This change in design was made in order to deter piracy, as pirated copies of products often used VLKs. This differs from previous Microsoft products in which VLKs simply bypassed product activation and will aid Microsoft in tracking down and disabling key access for companies somehow violating their license agreement. | Starting with ], VLKs will be replaced with Multiple Activation Keys (MAKs) that either activate copies through a local Key Management Server (KMS), which in turn reports back license usage to Microsoft, or activates directly in communication with Microsoft. Hosts activated via a KMS have to report back to that ] once every 180 days. This change in design was made in order to deter piracy, as pirated copies of products often used VLKs. This differs from previous Microsoft products in which VLKs simply bypassed product activation and will aid Microsoft in tracking down and disabling key access for companies somehow violating their license agreement. | ||
| Line 10: | Line 7: | ||
| ] will still use the Volume Activation 1.0 system despite being released in the Vista timeframe. | ] will still use the Volume Activation 1.0 system despite being released in the Vista timeframe. | ||
| ==Illicit use== | |||
| ⚫ | Since Volume Licensing bypasses ], VLKs have been exploited by ] since the advent of this service. The ] key is a prominent example of VLK exploitation. Although to some this may seem like an easy way to circumvent ]'s ] feature, each VLK is uniquely linked to the company from which it was purchased. Therefore, should the software be installed on more computers than it was licensed, Microsoft can hold the company responsible, and ] the product key in extreme cases. | ||
| Volume license keys have also been used incorrectly on Windows XP installations where the owner had a retail or OEM license to Windows XP but the person doing the installation (such as a computer repair shop) did not want to bother with activation, used ] software, or did not have access to the original license. | |||
| Volume license keys that have been abused have been blocked by Microsoft, starting with Windows XP Service Pack 1. Microsoft argues that it does not need to cater to the needs of those who did not pay for their software. Microsoft even developed a new key verification engine for Windows XP Service Pack 2 that could detect illicit keys, even those that had never been used before. Several ] consultants have condemned the move by Microsoft, saying that leaving a large install base unpatched from various security holes is irresponsible due to the fact that this unpatched install base can be leveraged in large scale Internet attacks, such as ] used to send ]. Others have come to Microsoft's defense, arguing that Microsoft should not have to provide support for illegal users. After much public outcry, Microsoft elected to disable the new key verification engine. Service Pack 2 only checks for the same small list of commonly used keys as Service Pack 1. This method does not completely prevent piracy, as users can generate new VLKs that will not be detected as pirated. Users of existing installations of Windows XP can also change their product key by following instructions from Microsoft. | |||
| A small number of keys have been completely banned by Microsoft and cannot be used with any CD that has been ] with Service Pack 2. If an original Windows XP CD (or a slipstreamed copy with Service Pack 1) is used to install Windows XP, the key is accepted; however, the system will not allow any newer updates (including Service Pack 2) to be installed. Microsoft has also released the ] (WGA) program, which requires users of Windows XP (and other recent operating systems) to activate their copy before downloading updates and certain programs from Microsoft's website. | |||
| ===FCKGW=== | |||
| FCKGW are the first five characters of the ] that was commonly used to bypass ] in early versions of ]'s ] operating system. The key is obsolete, as it has been blacklisted by Microsoft updates since August 2004; despite this, it is regularly a symbol of ] ] pride. Dubbed the "devils0wn" key, this particular key came with the first ] release of the final version of Windows XP. This version was supplied by a group calling themselves "devils0wn" 35 days before the official retail release on ], ]. This key was made famous partly due to the fact that it is featured in a popular image circulated on the ] before the retail launch of Windows XP. In the image, the key is written on a CD-R containing the leaked operating system and held in front of a digital Microsoft sign counting down the days until the release of Windows XP. | |||
| ==External links== | ==External links== | ||
Revision as of 16:19, 22 January 2007
Volume License key (VLK) is the term used by Microsoft to denote the product key used when installing software licensed under Volume Licensing, which allows a single product key to be used for multiple installations. This form of licensing is typically used in business, government, and educational institutions, with prices for Volume Licensing varying depending on the type and size of the setting. Microsoft software available through the Volume License program include Windows XP, Windows Server 2003, Microsoft Office 2003 and many others.
Volume Activation 2.0
Starting with Windows Vista, VLKs will be replaced with Multiple Activation Keys (MAKs) that either activate copies through a local Key Management Server (KMS), which in turn reports back license usage to Microsoft, or activates directly in communication with Microsoft. Hosts activated via a KMS have to report back to that key server once every 180 days. This change in design was made in order to deter piracy, as pirated copies of products often used VLKs. This differs from previous Microsoft products in which VLKs simply bypassed product activation and will aid Microsoft in tracking down and disabling key access for companies somehow violating their license agreement.
However, these new local key servers are known to already having been used as new attack vectors to enable piracy, such as opening them for Internet access, which is a violation of the EULA. It's possible such "rogue servers" will be, or are, modified to not communicate with Microsoft, and rather report that generated MAKs are valid. Such keys would likely still fail Windows Genuine Advantage tests though.
Microsoft Office 2007 Enterprise Edition will still use the Volume Activation 1.0 system despite being released in the Vista timeframe.
Illicit use
Since Volume Licensing bypasses activation, VLKs have been exploited by software pirates since the advent of this service. The FCKGW key is a prominent example of VLK exploitation. Although to some this may seem like an easy way to circumvent Microsoft's product activation feature, each VLK is uniquely linked to the company from which it was purchased. Therefore, should the software be installed on more computers than it was licensed, Microsoft can hold the company responsible, and blacklist the product key in extreme cases.
Volume license keys have also been used incorrectly on Windows XP installations where the owner had a retail or OEM license to Windows XP but the person doing the installation (such as a computer repair shop) did not want to bother with activation, used disk cloning software, or did not have access to the original license.
Volume license keys that have been abused have been blocked by Microsoft, starting with Windows XP Service Pack 1. Microsoft argues that it does not need to cater to the needs of those who did not pay for their software. Microsoft even developed a new key verification engine for Windows XP Service Pack 2 that could detect illicit keys, even those that had never been used before. Several security consultants have condemned the move by Microsoft, saying that leaving a large install base unpatched from various security holes is irresponsible due to the fact that this unpatched install base can be leveraged in large scale Internet attacks, such as trojan horses used to send spam e-mail. Others have come to Microsoft's defense, arguing that Microsoft should not have to provide support for illegal users. After much public outcry, Microsoft elected to disable the new key verification engine. Service Pack 2 only checks for the same small list of commonly used keys as Service Pack 1. This method does not completely prevent piracy, as users can generate new VLKs that will not be detected as pirated. Users of existing installations of Windows XP can also change their product key by following instructions from Microsoft.
A small number of keys have been completely banned by Microsoft and cannot be used with any CD that has been slipstreamed with Service Pack 2. If an original Windows XP CD (or a slipstreamed copy with Service Pack 1) is used to install Windows XP, the key is accepted; however, the system will not allow any newer updates (including Service Pack 2) to be installed. Microsoft has also released the Windows Genuine Advantage (WGA) program, which requires users of Windows XP (and other recent operating systems) to activate their copy before downloading updates and certain programs from Microsoft's website.
FCKGW
FCKGW are the first five characters of the CD key that was commonly used to bypass product activation in early versions of Microsoft's Windows XP operating system. The key is obsolete, as it has been blacklisted by Microsoft updates since August 2004; despite this, it is regularly a symbol of warez geek pride. Dubbed the "devils0wn" key, this particular key came with the first warez release of the final version of Windows XP. This version was supplied by a group calling themselves "devils0wn" 35 days before the official retail release on August 28, 2001. This key was made famous partly due to the fact that it is featured in a popular image circulated on the Internet before the retail launch of Windows XP. In the image, the key is written on a CD-R containing the leaked operating system and held in front of a digital Microsoft sign counting down the days until the release of Windows XP.