zydronium/py-kms
1
0
Fork 0
mirror of https://github.com/Py-KMS-Organization/py-kms.git synced 2025-08-05 08:21:29 +02:00
Code Issues Projects Releases Packages Wiki Activity

Merged docker/README.md into docs (#103)

Browse source 
* Merged docker/README.md into docs

* Minor reformulations
Added references

* Moved docker section one up, because they are not really start parameters

* Fix links

* Moved the supported products section into documentation, as it does not fit the usage topic
This commit is contained in:
Simonmicro 2020-10-16 22:58:56 +02:00 • committed by GitHub
parent de1c115967
commit c979f42da9
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
4 changed files with 103 additions and 122 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/Documentation.md
View file

@ -324,6 +324,11 @@ Where command line options are:
</tbody>
</table>
## Supported Products
Note that it is possible to activate all versions in the VL (Volume License) channel, so long as you provide the proper key to let Windows know that it should be activating against a KMS server. KMS activation can't be used for
Retail channel products, however you can install a VL product key specific to your edition of Windows even if it was installed as Retail. This effectively converts Retail installation to VL channel and will allow you to activate
from a KMS server. **However, this is not valid for Office's products**, so Office, Project and Visio must be always volume license versions. Newer version may work as long as the KMS protocol does not change...
## Further References
* <sup>[1]</sup> https://forums.mydigitallife.net/threads/emulated-kms-servers-on-non-windows-platforms.50234
* <sup>[2]</sup> https://forums.mydigitallife.net/threads/discussion-microsoft-office-2019.75232