I read the info about Elements and removed the offending InstallShield properties as per the advice here and tested it locally and it all worked great. I made an mst to remove the reader install because we deploy it Enterprise wide. I cleaned out 2 MS dll's that we deploy with Office and its pretty clean now.

I can deploy it via GPO now.......but....and here is the bite.

Workstation deployed......no problem
User Assigned with install at login....no problem.
Published to users......big problems.

Seems the Adobe install tries to register the PDFMakerX.dll in user context and a whole bucnh of other dlls as well. Seems Adobe "insists" that the user is a local admin, and also some of the HKCR keys arent being written and it self repairs on launch. Also the shortcut is in Allusers and thats a no no for published apps.

I think there is also a problem with redirected My Documents but I have to investigate that further.

Anyone else had these problems?

I love headaches :)
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


Ok so if you if want to publish Adobe Elements to users......forget it.

Adobe have sett all their custom actions to run in the User Context and if the user isn't an admin....then the dll's dont get registered at all. You will have to deploy it workstation based or user based "install at login".

Adobe is no help at all and say that wont support GPO installs of their apps.......what planet are they on?
Answered 04/03/2004 by: MSIMaker
Second Degree Black Belt

Please log in to comment