Closed saltspork closed 5 years ago
Yes, please update
i found some key IDs from the orgin of KMS vlmscd,the author mentioned an branch of py kms,https://github.com/ThunderEX/py-kms.and from the author i've found the keys we need.https://github.com/ThunderEX/py-kms/blob/master/KmsDataBase.xml. appid is the same with office2016 and other keys we could search these keys of office2016 to compare with office2019's.so that we can locate these keys we need.
@sooluck what are you talking about? The keys are available on Microsoft's website.
@sooluck what are you talking about? The keys are available on Microsoft's website.
maybe we can add these keys into client.py and kmsbase.py so that we can activate office2019?
@sooluck Keys: https://docs.microsoft.com/en-us/DeployOffice/vlactivation/gvlks / https://gist.github.com/pacoolio/3972670104cdd3fdaa596761ac685080
Apply the current PR and then change client.py
to include:
elif config['mode'] == 'Office2019':
config['RequiredClientCount'] = 5
config['KMSProtocolMajorVersion'] = 6
config['KMSProtocolMinorVersion'] = 0
config['KMSClientLicenseStatus'] = 2
config['KMSClientAppID'] = "0ff1ce15-a989-479d-af46-f275c6370663"
config['KMSClientSkuID'] = "c3b2612d-58ee-4d9b-ad9d-7568decb29f7"
config['KMSClientKMSCountedID'] = "617d9eb1-ef36-4f82-86e0-a65ae07b96c6"
It should work at least with Office. I'm unable to get it to work with Visio and Project. Seems like the keys Microsoft is providing for those aren't valid:
cscript //nologo ospp.vbs /inpkey:B4NPR-3FKK7-T2MBV-FRQ4W-PKD2B
---Processing--------------------------
---------------------------------------
ERROR CODE: 0xC004F069
ERROR DESCRIPTION: The Software Licensing Service reported that the product SKU is not found.
Please merge! This closes #6