Hi ,

I have deployed Acrobat reader version 8 through SCCM and it deployed successfully in all clients. Since the users required to disable the automatic update of acrobat reader we modified the package by writing a custom action to delete a file named Updater.API after acrobat reader is installed and the same was working fine in virtual machines. But when i redeployed the same to clients through sccm. It shows that the package has been installed successfully in client in sccm. But when i check in client machine the application folder shows the dtae when i deployed the package without any modification. Kindly advice how to overcome this problem.

Thanks & regards,
S.Yuvaraj.
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
Have you actually deployed the final installation to clients or are they using the package you had before you come up with the modification?
Answered 05/24/2009 by: dvdzonenz
Purple Belt

Please log in to comment
0
Yes I deployed the final installation to client
Answered 05/24/2009 by: Yuvaraj_Subramanian
Senior Purple Belt

Please log in to comment
0
Was it a transform for the native MSI, or did you actually repackage it?
Answered 05/24/2009 by: DeployTech
Orange Senior Belt

Please log in to comment
0
It is a transform for native MSI. Also when i check the log file in client it shows that Skipping action: DisableAutomaticUpdate (condition is false). Please Note that I have written a script for deleting a file which has a condition as NOT INSTALLED.
Answered 05/24/2009 by: Yuvaraj_Subramanian
Senior Purple Belt

Please log in to comment
0
Did you use the Adobe Customisation tool? I have found that the tool is more effective for turning off the updates that Adminstudio or Wise (and it's just a checkbox).
Answered 05/26/2009 by: DeployTech
Orange Senior Belt

Please log in to comment
0
No I did not use the adobe customization tool.Instead i used the script to delete an file named as "Updater.api".
Answered 05/29/2009 by: Yuvaraj_Subramanian
Senior Purple Belt

Please log in to comment
0
Try the tool, it works well.
Answered 06/02/2009 by: DeployTech
Orange Senior Belt

Please log in to comment
0
Hi I finally found the solution for this problem. We have written a custom action with conditionas NOT Installed using wise package studio. Since the package has been already installed this conditon fails and the script is not working. Finally we first run the uninstallation advertisement and again the run the new advertisement for new package installation. It worked. Thanks for all your help to solve this problem.

Thanks & Regards,
S.Yuvaraj.
Answered 06/03/2009 by: Yuvaraj_Subramanian
Senior Purple Belt

Please log in to comment
0
Why not support the custom action during install and repair?
Condition: NOT Installed or (REINSTALL and NOT PATCH)
Answered 06/03/2009 by: AngelD
Red Belt

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