/build/static/layout/Breadcrumb_cap_w.png

Acrobat 5.0.5 (Full) - Word startup template

Hello,

<n00bie alert!>

I have created an MSI for Adobe Acrobat v5.0.5 (Full version) - this includes all the patches etc. up to 5.0.10.

As part of the installation, an integration template is copied to the Word 'startup' directory. I have created a new component for this and added it to the main feature. The pdfmaker.dot file is the key file of this component.

This file gets deleted on PC reboot due to a network synchronisation we do between client PC and the network. I want to have the MSI reinstall the Acrobat integration template when Word is started. However, this doesn't appear to be happening for some reason.

I thought that if a components key file was missing, the MSI would automatically fire to reinstall it. Is this not the case?

Thanks in advance for any assistance you may be able to render with this.

Regards,

Mark.

0 Comments   [ + ] Show comments

Answers (2)

Posted by: carefree 19 years ago
Senior Yellow Belt
0
For self-repair to be activated you must attempt to access the keypath. When you launch Word, the keypath for Acrobat is not accessed. Word only checks its own keypaths. You will likely find the self-repair will work when you launch Acrobat??

The only way Word will start the self-repair is if that component is in your Word MSI... If you wanted to add this to your Word (of Office) package I recomend using the Custom Installation Wizard. There is a step in here which allows you to add your own files to the package. After the CIW, do as little as possible to the package, recompiling in Wise etc will break the CIW package. Apply any minor changes through ORCA.

Alternately, the "Word startup" directory is in the user profile. Do you use roaming profiles? GPO's and default network profiles could help add the file to the "Word startup" folder.

Good luck! [8D]
Posted by: fatman 19 years ago
Yellow Belt
0
Thanks, carefree.

I have discovered that as part of the Adobe Acrobat installation, the Adobe Assistant is installed to the Start Menu 'Startup' folder for all users. This fires at reboot and causes the MSI to reinstall and replace the missing Word integration template.

However, I think potentially adding this via a GPO is a good idea. (The above relies on whereabouts the directory synchronisation occurs and where the MSI reinstalls - if at all.) Think I will look at the GPO as well.

Thanks for your assistance - much appreciated!

Regards,

Mark.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ