I am also having this issue.  I use MAK Keys for activation and cannot get Thinapped Office to work without the license error.

Can you please make sure you followed all the steps mentioned here: http://communities.vmware.com/docs/DOC-15556

Thanks

Lakshman

So the document that you supplied does not work. At least not for me. Plus the one step in that dsocument you supplied says NOT to install the App-V kit. I HAD to load it. THere was a step that is needed with one of the scripts in App-V kit. If you don't use it they you will fail. What I ended up doing was following this guide first:

VMware: VMware ThinApp Blog: Quick-start guide for deploying Office 2010 using ThinApp 4.6.1

The next step that they don't tell you is that you need to dissconnect from the network durn instlal of Office so it does not try to activate. I use a KMS server for my stuff. Once I did that, complied and tested. It was not activated the first run but the secone run. tada! It is activated.

Nxion,

1. App-V kit is not required, please don't install it along with Office 2010.

2. No need to disconnect from the network. You should not try activating Office before Postscan.

Lakshman,

I'm sorry but your they steps that you attached did not work for me. I was just letting the posters know what I did to get it to work. There is something in the App-V kit that I used that worked for me. I no longer have the issues as far as activation. I tried to many, many different ways before I found that using part of App-V kit and disconnecting from the network to install Office worked.

Like I said they steps that attached may have worked for you but they did not work for me. There maybe other ways to capture Office 2010. I have found another solution. I wanted to let everyone know what I found because I can't be the only one that found this.

I know in the document it makes a note of saying that the reason that the repair popes up for Office and failes is because of whitespace. That was not the case. I cleaned the whitespace out and it still did not work. I still get that error.

In reality there have been instances where I have followed the project files to the letter and it did not work for me unless I added steps of my own.

Nxion,

The steps mentioned in the blog are tried and tested, not sure why it didn't work for you.

Have you checked your KMS server? Are you able to activate Office on different machines?

I'm ready to help you activating Office 2010 ThinApp without the use of App-V or disconnecting the network.

Please send the package.ini file to lprakash@vmware.com.

Thanks

Lakshman

Lakshman wrote:

Nxion,

The steps mentioned in the blog are tried and tested, not sure why it didn't work for you.

Have you checked your KMS server? Are you able to activate Office on different machines?

I'm ready to help you activating Office 2010 ThinApp without the use of App-V or disconnecting the network.

Please send the package.ini file to lprakash@vmware.com.

Thanks

Lakshman

Lakshman,

I appreshaiate for the additional help but as I stated in a previous post I was able to resolve the issue with activation. My Office 2010 is thinapped and deployed. I no longer have the licence issue. You right, I'm not sure why the other steps did not work. Really if you look at this instance.There isnt just a one size fits all when it comes to ThinApp. I had to modify the steps, adding a few to get it to work for me. Now I'm not saying that your way is wrong, but I had to use a differant set of steps to get it to work.

To answer your question, yes  I can activate other machines and office from my KMS server.