Check out this blog post, http://terenceluk.blogspot.com/2012/01/problems-activating-microsoft-office.html, and see if it's applicable.  

Have you considered using a ThinApp packaged version of your Office distribution? this would prevent having to activate the software everytime because you aren't truly "installing" it when you load from the thinapp package. (if thinapp isnt your choice, look at other application packaging options).

We generally have a "thinapp" machine we have set aside to create our packages on. You have to license ThinApp so yea that could be an issue, and then you need to run it in capture mode, install your app (office in this case), activate or properly license/key that software, then stop your capture. The resulting package is activated and ready to go already. At that point the package is portable to any system you want to run it on.

Delivering the packages to the actual pool view guests is tricky and we've modified our method several times, but currently its done via AD Group Membership and a loop in our logon script. After the logon .vbs enumerates all groups a user is a member of (AppRole_Office for example) it then does a ThinReg of that package into the system via some more groups and custom attributes. Usually this part only takes a few additional seconds during the logon process, as it doesn't install the app just the package which is on a network share.

Hope this helps!

File extensions as well as any possible launch point are defined when you are completing the package. Basically it will say which executable files are allowed to start the application, and which files are associated will actually be written into the registry. The portions of registry that changed during install are also wrapped into the package for mobility. When you run it on a separate client, those registry modifications are stored in the app cache (usually somewhere buried in your user\AppData folder).

Dear Chris

Since you creates a linked clone pool for VDI, then you need Oslo a KMS license for office 2010

But if you are going to thinApp office then I strong recommended you to go use thinApp 4.6.1 or higher

Sent from my iPad

KMS activations will not expire. That is the way!

Need some help with the Office activation on Horizon 7.8 Farm.  I am using Instant clones and have been fine with Office 2010 on the desktops until yesterday.  We are now suddenly getting the Office activation box when opening Office on the virtual desktops; I am a little confused as to why and how to fix it permanently.  We ARE using KMS activation and there are more than 5 requests (see below).  This post talks about "rearming Office 2010" however, if I am understanding correctly that is only a temporary fix.  We need a permanent fix.

Appreciate the help!!

Did you make an changes to office, is it on an appstack or something similar, or installed directly. I've seen this when a change to office was made, usually I just reinstall office.

Office is installed on the Master Image, not an AppStack.

No changes were made to Office.