Hi..

I just made an MSI package to change som registry settings in Adobe reader 9X.

When a new user login, i can see that the Active setup "SID" actually is copied to the HKCU, but the registry settings is not set..

But if i delete the key from HKCU and let the use log in again, the settings is applied..

Does Adobe reader somehow repair it self, at first login so the settings are override (Like a active setup), and my active setup is useless?

Its not an option to change the Adobe Package.

any ideas?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I consider you create an MST for Adobe Vendor MSI...

If this is the case Ur MSI shortcut must be advertised so that the HKCU reg key settings are installed during the launch of shortcut using advertised mechanism... so use active setup is not required....
Answered 01/26/2012 by: mahendraKumar
Senior Yellow Belt

Please log in to comment
0
Remember, though, that Adobe's MSIs don't much like packager-authored transforms. You should use the appropriate Adobe Customization Tool to create them.
Answered 01/26/2012 by: VBScab
Red Belt

Please log in to comment
0
no, its not an option to customise the Adobe package with MST file.

I have to found another solution.. To clarify

i need to enable Javascript in one domain. this is a HKCU settings, and therefore i need the activ setup.

its possible for me to deploy an MSI file to that domain, but the Adobe package is distributed from the top level.

when the MSI is applied, it works for the user that installed the MSI, but when a new user logs in to the PC, Javascript is disabled.

In the HKCU\Software\microsoft\active Setup i can see the key is "imported" from the HKLM hive.

If i delete this entry from the HKCU next time the user logs in, it will work..

So i guess that adobe has its own "active setup" everytime a new user login, that override my settings. Thats the hurdle.. :-)
Answered 01/26/2012 by: pzymex
Senior Yellow Belt

Please log in to comment
0
Er...why not simply use Group Policy? You can then restrict the "deployment" to a small test group and, once you're happy, add 'Authenticated Users' to the scope.
Answered 01/26/2012 by: VBScab
Red Belt

Please log in to comment
0
yes, i now implemented it by a group policy.. with a preferences..

Thanks for input..

Jens
Answered 01/27/2012 by: pzymex
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity