Many products contain Auto-update features. Firefox, Adobe products, Quicktime, etc. all have features that can be enabled to check for and install updates when they are available. Has anyone here changed products to point to an internal data source for updates rather than the web? We would like to be able to provide updates on a network share that the application looks at and updates from when needed.

Any advice would be appreciated. Thanks.

0 Comments   [ + ] Show 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.


It's going to depend upon the product in question. Many systems management applications can manage third party patches - such as KBOX, SCCM/SMS, and others. You can also create your own method for deploying patches (i.e. via logon scripts or custom applications). However, I doubt that many of these applications allow automatic updating via the application pointing to an internal server. If so, it will definitely be application specific (meaning what works for Quicktime won't work for Adobe Acrobat).
Answered 11/23/2009 by: airwolf
Tenth Degree Black Belt

Please log in to comment
I think creating a script at logon can be an option that will search for the update file on the network share on the particular folder and if found starts applying the patch.
I havn't tried this option but it seems to be achievable.

But, it would be interesting to know what others say on this topic.

Answered 11/24/2009 by:
Orange Belt

Please log in to comment
At the risk of sounding pompous, I'd say that anyone with any experience with vendor installation routines shudders with horror at the prospect of allowing ANY of them to automatically update the contents of a lunch box, much less the workstations in their enterprise. The first release of Symantec Endpoint Protection v11 would have been an abject lesson in how to really irritate sysadmins if we'd let it loose "as is".

Download updates, pull them apart and test them and their impact on your build and applications and only once you're happy that they're not going to destroy your environment should you deploy them, which you would do using your deployment mechanism. Control, control, control...
Answered 11/24/2009 by: VBScab
Red Belt

Please log in to comment
My thoughts exactly Ian...

You need to control everything that occurs so the desktop estate is of a standard that you can vouch for.


Answered 11/24/2009 by: dunnpy
Red Belt

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