Application Virtualisation Project

Thinapp and Creative Suite 5 – removing the fonts

My ThinApp’d copies of CS5 applications were taking along time to start, up to two minutes per application which is fine if you’re patient, but if you’re expecting a startup time similar to that of a locally installed program then you start to wonder what’s gone wrong…

So I thought I’d try and make them start faster, the biggest improvement seemed to occur when I deleted the %FONTS% directory from my capture (I also got rid of some other folders I didn’t think should be there, such as the driveC and so on, they had almost nothing in them. My .dat files are only about 200MB lighter now, but the speed up in starting times is drastic, down to about 30 seconds as a result.

As all three applications had the same “standard” fonts I decided to just make the fonts available to each machine as an installable MSI following instructions much like these ones. I also had a quick look over here: http://blogs.vmware.com/thinapp/2010/01/thinapp-troubleshooting—repost.html and followed their advice about turning off the automatic services.

ThinApp CS5 and RES – fixing the permissions issue

In a previous post I talked about ThinApp’ing Adobe Creative Suite CS5 and how to disable all the prompts so that end users aren’t bothered all the time. I then ran into a different issue, due to the way that Adobe code their products they write a file to “Program Files Common”, which of course with ThinApp is redirected, without read/write access for the current user. This then breaks roaming profiles as the file can’t be copied to and from the server.
Continue Reading →

Enlarge 4 Comment

ThinApp Adobe Creative Suite 5 (CS5) – Disabling all the prompts

So, there are quite a few bits and bobs out there about CS5 but none that tell me all the things I want to know in once place.

Let’s start by point out the useful “thinapphelper” tool for those of you who aren’t aware of it: http://www.cis.nl/thinapphelper – it’s a nifty tool that allows you to inspect everything that’s going into a build, the most useful part of this for me is that it allows me to delete any temporary files that I may not want to be within the package.
Continue Reading →

Enlarge 1 Comment

ThinApp – Discovering vregtool.exe to examine .tvr files

Note: There is a bug in ThinApp 4.7.0 (update expected end of April 2012) that stops this from working.

As part of my deployment of Adobe Creative Suite 5 via ThinApp I had to capture an installation of Adobe Acrobat Pro 9.3 – the project pages on this were helpful, and I deleted the locally installed PDF printer before completing the capture but I obviously missed something because each time I started the application as a new user I got a prompt for the Customer Experience / Improvement programme or whatever. No amount of using procmon could lead me to the file that was being changed, until I realised it was a registry key. And then I realised that I should have made sure this didn’t happen before I finished my capture, and then I was sad.

But, all was not lost, I noticed in the roaming thinstall directory that there was a file called “Registry.rw.tvr” and I thought “that sounds like it might contain registry information”, and sure enough it DOES. It contains the incremental sandbox changes to the registry, so all I needed to do was inspect it, identify the relevant value and then put that back into the ACTUAL thinapp build. I found this blog post which guided me in the right direction and I also found I guide for vregtool.exe in ThinApp 4.6, which provided some more info.

So, once I’d established that I just threw the .tvr file out into a text file (which is the same format as the HKLM/HKCU files in the root of the build directory) and copied across the relevant stuff, rebuilt and voilla!

vregtool.exe "..\Captures\Adobe Acrobat 9.3.0\Registry-CustomerImprovementProgram.rw.tvr" ExportTxt .

Enlarge 0 Comment

Application Virtualisation

For one of my first projects this year I’ll be looking at Application Virtualisation – streamlining application deployment by creating single executable files which can then run on any workstation, there are some obvious advantages to this such as centralised deployment and maintainance, as well as the speed at which new applications can be provisioned using such methods.

See all posts relating to this project