This is a new type of application update procedure I've created to allow for a few important features:
• Automatically leverage Patch Management File Source configuration for application deployment • Deploy new versions of an application without having to change the procedure -- just run it again • Allow for quick modification to deploy new applications by just editing a few lines
sure you're using Kaseya 6.0.1 which now supports 'global' variables --
check for this under System --> Configure, you should see your
version number at the top. If you need 6.0.1, just contact support.
import the procedure, just extract the XML and import it with the Agent
Procedures -> Import button, clicking either a private or public
folder first which the procedure will reside.
As soon as you import, as mentioned in the description of the procedure, be sure edit the procedure and change the two 'Schedule
Procedure' steps at the bottom to reference this specific procedure
If you have systems setup to use the Kaseya server as the file
source (usually not the case), you should download the application's EXE
to the public files folder of your Kaseya server. You can easily upload
it with the Agent Procedures -> Manage Files button.
In the case of Firefox-Windows, the actual URL we'll be using will be
located at http://files.kaseya.com/sftp/appupdates/firefox-windows/firefox-windows-url.txt
-- this text file contains the URL of the file you need to grab.
You will see 'firefox-windows' is a variable in the procedure -- this allows
us to quickly change the variable to match a common file and folder
structure on our site so myself or other Kaseyans can update these
variables to pull down the latest version of an application, negating
the need to import a new procedure every time. Ideally, you could
schedule this procedure to run regularly to keep Adobe Flash for Non-Active X browsers up to
Be sure to check the Agent Procedure log as you are testing out this
procedure, as I did my best to log down exactly what is happening with
the procedure for troubleshooting purposes. You can also use the
procedure log to enhance your Executive Summary to show how many times
the application has been updated, or to view the results of a large
number of systems with a Log -> Agent Procedure log report.
Please post any feedback -- I'm looking forward to seeing how well this is received :)
Benjamin Lavalley, Sr. Product Marketing Manager, Kaseya
Hi. Thanks for this awesome post. I am only wondering how I can report on the number of times updated/installed?
Any assistance would be great. Thanks.
I'll try to get that posted up later this week with some screenshots. It is a matter of modifying the Exec Summary to queue off the agent procedure log , looking for a particular key word from this procedure that would indicate Firefox updated.
Thanks, but we need german versions.
Is it possible to deploy this procedure with IT Center? It seems that we don't have the ability to upload a file to the server, so I had to delete the step where it queries the Firefox exe on the server, and without that step it appears that deploying the script fails.
I don't know about the availability of file management within IT Center, but you should be able to setup the File Source under Patch Management to either Internet or File Share and the procedure will not attempt to write the file from the Kaseya server.
This procedure will also now deploy Firefox 3.6.13.
Updated to deploy Firefox 4.0!
Updated for Firefox 4.0.1
This link; download.mozilla.org defined in the firefox-windows url txtno longer works.
Can this be updated?