http://bugs.winehq.org/show_bug.cgi?id=30033
--- Comment #10 from robspaulo@freenet.de 2012-06-19 03:51:11 CDT --- Do you have at least one computer that works with Windows OS? If so what variables are in "[HKEY_LOCAL_MACHINE\Software\Microsoft\OfficeSoftwareProtectionPlatform]"? Are there also those variables "KeyManagementServiceName" and "KeyManagementServicePort"? If they exist do these variables have some values?
This was the way I went by analysing the VB script. I also had a Virtual Box Windows installation with MS Office 2010 where activation was no problem.
Maybe some very intersting information for this topic are also described here: http://technet.microsoft.com/de-de/library/ff793438.aspx It is explained for MS Windows activation only but maybe it helps.
Greetings.
(In reply to comment #9)
Microsoft offers companies two ways to activate their volume licenses: KMS and MAK. KMS relies on a central server within the company, and is apparently what you have. MAK connects to Microsoft's central servers, and is what my employer and Sean's have. The workaround you posted may work for KMS activation, but those of us with MAK-activated licenses can't even test it without knowing what values to put for License server and Port of license server.