We also generally don't rebuild PC's until they have either hit their life cycle and the user receives a new PC or a problem occurs which requires us to rebuild. Our standard way of deploying software is through SMS. This also causes greater problems when I "eventually" have to remove this software. My last resort will be to install the software one by one on each PC that has to receive it. So I am stuck trying to get this piece of software automated. It isn't always fun to make the archaic software work but in the IT field it is often not a negotiable option either. Due to policy restriction I have to use this exact piece of software. While that is exactly the behavior you would expect when generating a. exe in a gui mode and waits for user response. exe and it doesn't respond to any of them sadly.
I have tried the standard switches against the. I don't remember the exact syntax but check here for more info. If you don't have any need for user input, why don't you do a silent installation? It's using installshield so you should be able to create an answerfile (.iss) using "Setup.exe -r" (or something like that) and then reference it (setup.exe -f1\path\response.iss) in your autoit script.
0 kommentar(er)
