Q: Exitcode from SUF6 when using site installation tools

[bitfix]

Hi,

Anyone who knows how to get a usefull exit code when running a installation created with SUF6.

I need to install a program on 500+ computers in a company. I want to be able to detect whether each one was successfull, by using the exit code from running the installation in silent mode from a batch installation.

Thnx Henrik

[JimS]

In Actions, on the After Installing tab you could use the Submit to Web action to send you an email letting you know the installation was successful.

You can run a .bat file first to get the IP address of the computer, so you have a way to identify what computer is sending you the email.

An example batch file can be found here:
http://www.robvanderwoude.com/batexamples_gk.html#G

[csd214]

You can ”identify the computer” with the Built-in Variable %LANIP% in Setup Factory (not necessary to run a .bat file).

If the 500+ computers are connected through a LAN, you can create your own installation log (action “Write to text file”) and use whatever variable you want (like %LANHost%, %LANUser% or user defined variables).

[bitfix]

I have got some ideas by now, and also some new information - like the LANIP variable - thats great!

Your suggestions are fine, but they require some knowledge of the network like email or logfile. Unfortunately I have no exact knowledge of the customer nor the network.

But I think the SUF dev. team should create the possibility to return af falurecode for silent installations. SUF can do almost anything else, why not this. Its quite easy to implement.

I finally solved my problem by writing a wrapper in Delphi, that extracts the SUF installation to a temp dir, run it, and then wait for the uninstall registrykey for the installed program, to appear - or at worst timeout. The returned code was 0 for OK or 1 for timeout. But it's not everyone who can do that. My solution works for all Win. versions, and need no log or mailing etc. BUT it did require external programming.

Bye

[JimS]

Good call csd214, I guess I had Bat files on the brain that day.