thinapp and office 2010 issues

Discussion in 'Microsoft Office' started by boogerlad, Mar 14, 2011.

  1. boogerlad

    boogerlad MDL Novice

    Aug 4, 2010
    16
    0
    0
    I have followed communities.vmware.com/thread/263698?start=0&tstart=0 and blogs.vmware.com/thinapp/2011/02/quick-start-guide-for-deploying-office-2010-using-thinapp-461.html and I still have the issue of 30 day activation issue, even though I activated with codyqx4's activator. Is there anything I can do to make it activate properly? I also ran each office app 5 times and restarted too to make sure that kms would activate properly.
     
  2. pantagruel

    pantagruel MDL Member

    Aug 30, 2007
    206
    623
    10
    #2 pantagruel, Mar 22, 2011
    Last edited: Mar 26, 2011
    Basically, to keep ThinApped Office Professional Plus 2010 activated you need to set the KMS Host Server address during the ThinApp packaging process. You can use a 'real' KMS server address or the ZWT keygen server address (127.0.0.1). My explanation below assumes you'll be using the ZWT keygen, which I package with Office 2010 for a complete self contained package. 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.

    Just follow the guide for 'Capturing Office 2010 on Windows XP SP3 with Volume Activation (KMS) installer' at blogs.vmware.com/thinapp/2011/02/quick-start-guide-for-deploying-office-2010-using-thinapp-461.html and between step 10 and 11 do the following:

    (1) Copy the ZWT keygen to the root of C: drive - do not open at this point.

    (2) Open a command prompt and enter:

    For 32-bit Windows: cscript "C:\Program Files\Microsoft Office\Office14\OSPP.VBS" /sethst:127.0.0.1
    For 64-bit Windows: cscript "C:\Program Files (x86)\Microsoft Office\Office14\OSPP.VBS" /sethst:127.0.0.1

    This sets the desired KMS server, and you should see a message to that effect.

    Close the command box, and continue with steps 11 to 15. When creating the package, create an entry point for the keygen which is now on the root of C: drive. For example, I have entry points for Excel, Winword and the keygen, you may want more, depending on your installation..

    Now, once you have Office 2010 packaged, copy the bin folder out of the VM to your desktop, and close the VM. 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. Just close this dialog box, and close WinWord. 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. Continue to close and reopen Winword, checking under File - help for activation status until it activates. It shouldn't take more than a few times before it tells you that it is activated.

    There may be other ways to skin this cat. For the time being I think this is the cleanest way. Lemme know how it goes for you.

    ZWT KMS Keygen:

    Size: 76.0 KB (77,824 bytes)

    File: Keygen.exe
    CRC-32: bb5638c1
    MD4: 312a47fb3084ae5f0383ffa659a7b401
    MD5: b3b9295385f4e74d023181e5a24f4d83
    SHA-1: 191d401b0afdb39aa6a6b6c2dfb366e5e64be2ba

    Created with the HashCheck Shell Extension. HashTab is cool, too.
     
  3. a_catalin

    a_catalin MDL Member

    Mar 4, 2011
    166
    62
    10
    Thank you very much, I will try...