Running an update via command line on demand

[Guest]

In my organization, we are designing a new public access system where the computers will be protected with "rollback" software so no changes are retained. Updates will be handled in a maintainance window and include Windows Updates, Anti Virus Definitions and hopefully Flash Player, Acrobat Reader and Shockwave Player. The "snapshot" of the disk is then updated.

Is there a way of running the update on demand, I have tried running the EXE that the scheduled task calls, but that doesn't seem to do much (maybe it only runs for the system account?)

I cannot rely on the automatic update happening to run in the maintainance window and I need to have output of when the update has completed whether there was or was not an update performed.

Needless to say, all this needs to be able to run silently.

Any suggestions are gratefully accepted.

Martin

[pwillener · Accepted solution]

Most likely you will find all these information in http://www.adobe.com/devnet/flashplayer/articles/flash_player_admin_guide.html

[Guest]

I had looked at this before, but had hoped i could just run a command and parse a "No available updates" or "Successfully Updated" ruturn or something. If this is the only way to do it, then it looks like I will have to have an mms.cfg with settings:

AutoUpdateDisable=0

AutoUpdateInterval=0

SilentAutoUpdateEnable=1

SilentAutoUpdateVerboseLogging=1

And if I'm reading the documents correctly, I need to then launch a web page that uses Flash to prompt the update? If so, that's easy enough, just open a web page to the Adobe page that shows when an update is successful?

I can then monitor the log file to see what is going on.

[Guest]

Ah ha: Success!

MMS.cfg set as above and then run FlashPlayerUpdateService.exe, wait a little bit and low and behold the update runs like a charm.

Sooooo....

If I clear the log, then run the update EXE I can ascertain:

1. When the update has started: The log file contains data.

2. When the update has completed: The log file ends with "=X======" plus the timestamp

3. If the process has or has not actualy found and installed an update.