http://bugs.winehq.org/show_bug.cgi?id=30033 --- Comment #7 from Sean O'Brien <sean(a)techobrien.com> 2012-06-15 13:19:39 CDT --- Wow...thanks for checking that out Robert, that's fantastic insight. Since we no longer have a local MS license server for office and rely on Microsoft's own VLK activation servers, is this workaround possible? What values would you use for the two keys mentioned? "KeyManagementServiceName REG_SZ <Licence server>" "KeyManagementServicePort REG_SZ <Port of licence server>" Thanks for your help on this bug -Sean (In reply to comment #6)
Hello everybody,
for those who are working with MS Office for example in a company that provides a volume licence should have noticed that it is not possible to activate the product with the "cscript <whatever>" solution.
I analysed this visual basic script and found a workaround for this issue:
There are three different registry entries that have to be added:
[HKEY_LOCAL_MACHINE\Software\Microsoft\OfficeSoftwareProtectionPlatform]
Insert:
"KeyManagementServiceName REG_SZ <Licence server>" "KeyManagementServicePort REG_SZ <Port of licence server>"
Start MS Office (i.e. Word). Then an additional entry will be automatically created:
[HKEY_USERS\S-1-5-20\Software\Microsoft\OfficeSoftwareProtectionPlatform]
Insert: "VLRenewalSchedule REG_BINARY <any value>"
Alternatively it might be possible to copy the value of "VLRenewalSchedule" from [HKEY_USERS\S-1-5-21-0-0-0-1000\Software\Microsoft\OfficeSoftwareProtectionPlatform]
It is possible that you have to start MS Office, close it completely and restart it.
In the menu of Word go to "File - Help". You should now see that MS Office was successfully activated.
Greetings,
Robert.
-- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.