7x31/py-kms
1
0
Fork 0
mirror of https://github.com/SystemRage/py-kms.git synced 2025-09-29 00:49:20 +08:00
Code Issues Packages Projects Releases Wiki Activity

Updated Manual (markdown)

Matteo ℱan
2018-03-01 22:52:38 +01:00
parent 30166cf0f1
commit ff1f8949b8
1 changed files with 27 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
Manual.md

@@ -20,11 +20,13 @@ To remember you can't activate Windows 8.1 ( and above ) on a KMS server hosted
## About GVLK keys
The GVLK keys for products sold via volume license contracts ( renewal every 180 days ) are published on Microsoft’s Technet web site.
* Windows: http://technet.microsoft.com/en-us/library/jj612867.aspx
* Windows: https://technet.microsoft.com/en-us/library/jj612867.aspx
* Office 2010: http://technet.microsoft.com/en-us/library/ee624355(v=office.14).aspx#section2_3
* Office 2010: https://technet.microsoft.com/en-us/library/ee624355(v=office.14).aspx#section2_3
* Office 2013: http://technet.microsoft.com/en-us/library/dn385360.aspx
* Office 2013: https://technet.microsoft.com/en-us/library/dn385360.aspx
* Office 2016: https://technet.microsoft.com/it-it/library/dn385360(v=office.16).aspx
There are also not official keys for consumer-only versions of Windows that require
activation renewal every 45 days ( Windows 8.1 ) or 30 days ( Windows 8 ).
@@ -442,8 +444,8 @@ user@user ~/path/to/folder/py-kms $ python client.py 0.0.0.0 1688 -v DEBUG
```
or if you want better specify:
```
user@user ~/path/to/folder/py-kms $ python server.py 192.168.1.102 1688 -v DEBUG
user@user ~/path/to/folder/py-kms $ python client.py 192.168.1.102 1688 -v DEBUG
user@user ~/path/to/folder/py-kms $ python server.py YOUR_IPADDRESS 1688 -v DEBUG
user@user ~/path/to/folder/py-kms $ python client.py YOUR_IPADDRESS 1688 -v DEBUG
```
You can also put further parameters as defined below:
@@ -480,6 +482,26 @@ You can also put further parameters as defined below:
-f of --logfile <LOGFILE>
Create a "LOGFILE.log" logging file. The default is named "pykms_client.log".
## Activation Procedure
Briefly the product asks for a key during installation, so it needs to enter the GVLK. Then user can set connection parameters, while KMS server must already be running on server machine. Finally with specific commands activation occurs automatically and can be extended later every time for another 180 ( or 45 ) days.
#### _Windows_.
***
![win1](https://user-images.githubusercontent.com/25354386/36869547-74d05076-1d9c-11e8-9dee-1ff641449c7c.png)
0. Run a Command Prompt as Administrator ( you are directly in ```C:\Windows\System32``` path ).
```//nologo``` option of ```cscript``` needs only to hide startup logo.
1. This is facoltative, it's for unistalling existing product key.
2. Then put your product's GVLK.
3. Set connection parameters.
4. Try online activation, but... if that fails with error ```0xC004F074``` you’ll most likely have to configure your firewall that it accepts incoming connections on TCP port 1688.
So for Linux users: ```sudo ufw allow 1688``` ( to remove this rule ```sudo ufw delete allow 1688``` )
5. Attempt online activation (with now firewall enabled ).
6. View license informations ( if you want, it's facoltative ).
## 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. This is not valid for Office's products, so Office, Project and Visio must be volume license versions. Newer version may work as long as the KMS protocol does not change.