i have an Adobe acrobat standard package which is 9.4.1 to package and deploy.
I created an admin install of 9.0 and applied patches to make it 9.4.1

I deployed using SMS. When i logged in using another account and try to launch the shortcut, GETTING REPAIRED as no hkcu's exist.I noticed it is trying to repair from the SMS source eventhough I installed all the featues locally and also used ADDLOCAL=ALL..if the user is not having access to SMS source,its asking for credentials, which i do not want the user to get it displayed.

Whats the resolution for this? why is that its trying to repair from SMS source
Shall i proceed with putting all the admin folders inside msi so that repair happens from local cache. IF yes...what is the process
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
Install the package on an XP machine, and look in the eventlog after the repair. There should be an entry there telling you exactly which component in the msi is triggering the repair and what keypath was missing on the machine. It could be other things besides HKCU keys, like files in the userprofile, advertised dll's, etc...

As a matter of fact, since Windows Installer goes looking for the MSI in the original install location, it's looking to get the files contained in the package (the cached version of the msi on the local machine does not contain the files), so there's probably a file missing somewhere.

PJ
Answered 01/13/2011 by: pjgeutjens
Red Belt

Please log in to comment
0
is it possible to put all the admin folders in the SMS source folder inside MSI to resolve from looking into SMS source.
Answered 01/13/2011 by: rvrajendra
Orange Belt

Please log in to comment
0
is it possible to put all the admin folders in the SMS source folder inside MSI to resolve from looking into SMS source.

no, or not in an easy way at least. I suppose you could put a copy locally and then change the registry entries for the SourceList under HKCR\Installer\Products, so Windows Installers looks on the local machine instead of the network.

Have you already identified the file (I guess it's a file) that's triggering the repair?

PJ
Answered 01/13/2011 by: pjgeutjens
Red Belt

Please log in to comment
0
I identified the component which triggering the repair, one HKCU registry key....so what can I do now
Answered 01/16/2011 by: rvrajendra
Orange Belt

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