mirror of
https://github.com/SystemRage/py-kms.git
synced 2025-09-29 00:49:20 +08:00
Updated Manual (markdown)
29
Manual.md
29
Manual.md
@@ -485,10 +485,12 @@ You can also put further parameters as defined below:
|
|||||||
## Activation Procedure
|
## 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.
|
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_.
|
#### _Windows_
|
||||||
***
|
***
|
||||||

|

|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
0. Run a Command Prompt as Administrator ( you are directly in ```C:\Windows\System32``` path ).
|
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.
|
```//nologo``` option of ```cscript``` needs only to hide startup logo.
|
||||||
@@ -497,10 +499,31 @@ Briefly the product asks for a key during installation, so it needs to enter the
|
|||||||
2. Then put your product's GVLK.
|
2. Then put your product's GVLK.
|
||||||
3. Set connection parameters.
|
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.
|
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``` )
|
So for Linux users ( server-side with server.py running ): ```sudo ufw allow 1688``` ( to remove this rule ```sudo ufw delete allow 1688``` )
|
||||||
5. Attempt online activation (with now firewall enabled ).
|
5. Attempt online activation ( with now firewall enabled ).
|
||||||
6. View license informations ( if you want, it's facoltative ).
|
6. View license informations ( if you want, it's facoltative ).
|
||||||
|
|
||||||
|
#### _Office_
|
||||||
|
***
|
||||||
|
Note that you’ll have to install a volume license ( VL ) version of Office. Office versions downloaded from MSDN and / or Technet are non-VL.
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
0. Run a Command Prompt as Administrator and navigate to Office folder ```cd C:\ProgramFiles\Microsoft Office\OfficeXX```, where XX = 14 for Office 2010, 15 for Office 2013, 16 for Office 2016.
|
||||||
|
1. As you can see, running ```/dstatus```, my Office is expiring ( 14 days remaining ).
|
||||||
|
2. Only for example, let's go to uninstall this product.
|
||||||
|
3. This is confirmed running ```/dstatus``` again.
|
||||||
|
4. Now i put my product's GVLK ( and you yours ).
|
||||||
|
5. Set the connection parameter KMS server address.
|
||||||
|
6. Set the connection parameter KMS server port.
|
||||||
|
7. Activate installed Office product key.
|
||||||
|
8. View license informations ( in my case product is now licensed and remaining grace 180 days as expected ).
|
||||||
|
|
||||||
## Supported Products
|
## 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.
|
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.
|
||||||
|
Reference in New Issue
Block a user