\"/updatesetup\" and \"/update\" coupling

[alexzakharov]

I noticed that there is a direct coupling between running "/update" and "/updatesetup": specifically one MUST run "/updatesetup" before running any "/updates".

This seems like an unnecessary dependency. Some of our clients dont care about the windows task but do want to have the ability to run the "/update" script from the start menu.

How can I make these two steps independent? Basically, right after the install I want the clients to be able to run "/update" right away, whether or not windows update task has been set up.

On a related note, as far as setting up the windows update task - what was Installaware's rationale for forcing the user to run "/updatesetup" as an INDEPENDENT step? Wouldn't it make more sense to run "/updatesetup" automatically as the last step of the install process? or is there some technical reason/philosophy why it cant/shouldn't be done?

thanks,

alex

[MichaelNesmith]

InstallAware did this in that way to provide maximum resemblancy to the behavior of Windows Update itself. This was to improve the user experience by providing an already familiar workflow that most users should already be familiar with from their base Windows installation.

Of course, you have the full sources to the update script. There is absolutely nothing that goes on under the hood here. If you look at the update script, you can trace how the code executes line by line - checking for each command line parameter, and so on.

Just customize to suit your requirements! If you believe your customizations are of general interest, please feel free to post them in the Sample Scripts section of this forum, so other users can benefit from your work as well!