I'm sure you know that ThinApp Office 2010 is not activated on the first run. This is a documented known issue.
If you have a clean sandbox and run the ThinApped App, and go to the "info" backstage, it will show as unactivated. Only after the second or third run will it be activated.
This is not a big issue during the first month, as no nag is shown anywhere. Most users will not notice that.
But.... After 1 month from capture, if you run a Office 2010 app on a clean sandbox it will trigger a nag saying "unlicensed software", red titlebar, etc. This is the regular Office way to work when not contacting a KMS for more than 1 month. App thinks it was installed since capture time, without contacting a KMS.
The problem is that the ThinApp is broken somehow, and only after the second run will activation kick. And you can't run OSPP.vbs before the app runs, because it will only see physical Office Software License Services even when run from inside the ThinApp (ex.: cmd). While this does not pose a problem in a legal way (what is important is the invoices and records), your users will see that red nag, and think that somehow you are running unlicensed software. Also, some less informed auditor may not like this kind of thing!
Is there any fix for this issue?
Thanks.
PS: this is for KMS licensing; I have a KMS key with enough activations and enough invoices 