Would like to Grey-out or remove the registration and updates feature under the Help Menu. I've done this with many other adobe products but no luck with Captivate 3. I work in a controlled environment and don't want users to have access to these features.
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
ORIGINAL: wrobdog
Would like to Grey-out or remove the registration and updates feature under the Help Menu. I've done this with many other adobe products but no luck with Captivate 3. I work in a controlled environment and don't want users to have access to these features.


not sure what sort of options may be available thru vendor install to do this - is it MSI, is there provision for administrative install/distribution? as a last resort you could find the component that contains the "updates" functionality and just remove it from the installation. You may end up with a help menu that still has the option but if the user clicks on it, it will do nothing.
Answered 03/04/2008 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
Yes it's a vender MSI, and i should of said disable or hide instead of remove. I've combed through all the .xml files and .js files in the package with no success.
Answered 03/04/2008 by: wrobdog
Senior Yellow Belt

Please log in to comment
0
Try removing the component or file then. It's a good bet that it's named *update*, may be an EXE, DLL or OCX. Sometimes the description in the MSI can help. Do a search with orca or wise for update. Good luck
Answered 03/04/2008 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
Hi,

I have done this in the past with some applications as my organisation did not want the users to manually update the application.

Some applications did get updating done through CA in applications which query the update files when the user clicks the update button. So you can just remove those particular CAs from your application.(But I am not sure you this will grey out the options but will definitely make sure that nothing happens when the User clicks on the update button)
I resorted to a very simple approach of going through the files installed by the application and look for clues my the names of the files such as with keywords like 'Update'. Then would go on to remove this file from the package and install. Sometimes this worked in disabling the Update options.
If you cant make out which file is run for the updates then I suggest you can install the legacy setup or vendor msi. Post installation you can run Filemon and RegMon or ProcMon, click on the update menu option and check which file is queried and you may remove them from you application and check.
One more thing the file related to updating has always been an .exe or a .dll file.

I hope this helps [:(]
Answered 03/04/2008 by: India_Repackaging
Blue Belt

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