![]() ![]() At this point double click on the keygen (which you created an entry point for) and leave its command window open, and open Winword again. Just close this dialog box, and close WinWord. Fire up Winword from within the bin folder and it'll open and tell you that it's not activated and that you have 30 days left to activate. ![]() Now, once you have Office 2010 packaged, copy the bin folder out of the VM to your desktop, and close the VM. For example, I have entry points for Excel, Winword and the keygen, you may want more, depending on your installation. ![]() When creating the package, create an entry point for the keygen which is now on the root of C: drive. This sets the desired KMS server, and you should see a message to that effect.Ĭlose the command box, and continue with steps 11 to 15. (1) Copy the ZWT keygen to the root of C: drive - do not open at this point.įor 32-bit Windows: cscript "C:\Program Files\Microsoft Office\Office14\OSPP.VBS" /sethst:127.0.0.1įor 64-bit Windows: cscript "C:\Program Files (x86)\Microsoft Office\Office14\OSPP.VBS" /sethst:127.0.0.1 Just follow the guide for 'Capturing Office 2010 on Windows XP SP3 with Volume Activation (KMS) installer' at /thinapp/2011/02/quick-start-guide-for-deploying-office-2010-using-thinapp-461.html and between step 10 and 11 do the following: This method takes advantage of the fact that the KMS client (Office 2010) automatically searches for the KMS host at the address set (127.0.0.1) and attempts activation/reactivation. My explanation below assumes you'll be using the ZWT keygen, which I package with Office 2010 for a complete self contained package. You can use a 'real' KMS server address or the ZWT keygen server address (127.0.0.1). Basically, to keep ThinApped Office Professional Plus 2010 activated you need to set the KMS Host Server address during the ThinApp packaging process. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |