Thank you. I checked out the link but this means i still have to activate office after the rearm.....
Because we run a refresh every time a user logs off the next reboot they have to activate again.....which at some point those keys will be blocked after so many activations.
my solution would be activating the gold image / master image with office 2010 on it then do linked clones of this. which will have activation on it so when users login they are already activated.
Any joy anyone? i can't believe that no one has actually done this?
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).
Hi Jon thanks.
Just wanted to check with thin app don't you need to install it on the one you are going to capture? activate it? i read somewhere i think that you have to activate it again even with thin app install.
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!
thank you Jon, I might give that ago just need to go set it up.
Just one quick question since its a thinapp how did you associate all the file extensions to use the approrpate application provided by thin app?
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).
I've just tried the thinapp for office 2010.
Sadly when doing it i did activate the office package hoping it does not ask for activation once the thin app has been built.
But once i launch the thin app for office it still requires activation.
how did you get past this?
I'm asking because we run a refresh after log off scheme......on our floating pools so having it asking to activate is not good for us.
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
Is there anyway to avoid activation with KMS?
My linked clones are refreshed every time teh user logs off.....this would mean they have to activate it every time they log back on.
Eventually the serial key they are using will be blocked after so many activations.
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.