This is a fairly common issue. When Adobe Reader X is being managed by Personalization Server in Environment Manager v8.1, the application fails to launch properly. It may hang altogether, or throw an error that doesn’t really tell you much of use at all.
The reason for this is that Adobe Reader X introduced a “sandbox” feature called
Protected Mode. Now, Personalization Server also virtualizes the execution of the application to some degree, so when the Adobe sandbox feature is enabled, the two clash heads, and exhibit a deadlock situation.
We don’t want to disable Personalization, so naturally the way to work around this is to disable the Protected Mode feature in Adobe Reader X. You could do the decent thing and get rid of Adobe Reader X in favour of a half-decent PDF reader (sorry, Adobe, but the bloat of your software – even after using the Adobe Customization Wizard – is beyond belief), but for a lot of enterprises, this sadly isn’t an option.
Configure a
Process Started node for Adobe Reader X (make sure you use the full path as the process name is the same for other Adobe Reader versions)
Now use a Registry Action to turn off Protected Mode as shown below. Registry Actions are under Action | Registry | Set Registry Value
Next time your users launch Adobe Reader X, Protected Mode will be disabled and Personalization of the application will take place properly.
This is a quite well-documented issue, so the bods at AppSense have quite kindly fixed it in version 8.2 of Environment Manager, if I remember correctly.
Share
