I've been working on a CMD script to update workstations from Lotus Sametime 7.0 to Sametime 8.0.1 version. The setup.bat file IBM supplied with the software provides a complex command line running an MSI built SETUP.EXE file with numerous switches that works flawlessly while logged in to Windows, but craps out when trying to run pre-gina. It bombs without an error, terminates my script without advancing further or waiting the full timeout set up for application installations (20 minutes, it bombs about 2-3 minutes into it). The log file it creates (install.log) is no help. I'm desperately trying to automate the process, as manually installing the update for 150-200 clients (and rising) would be a LOT more work than tweaking the package. Plus it introduces more human factor into it than I want: I've got a document for the manual process, and our technicians are good, but I don't want to put extra work on them if I can help it, and my instructions are a bit arduous. Suggestions or tips?

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


I got it figured out!! I had to map u: as part of my CMD batch, since MSI installs seem to want that mapping to exist. I also did add the ALLUSERS=1 to the setup.exe command line with all the other switches (not sure if I had to, but it didn't crash). Now all I have to do is incorporate the Windows firewall exception for the new version of Sametime and probably let the user know pre-populating the username in the XML config file is not worth the trouble because it populates once they type it the first time and stays there.
Answered 07/10/2008 by: evv_appdude
Yellow Belt

Please log in to comment
ORIGINAL: evv_appdude
I got it figured out!! I had to map u: as part of my CMD batch, since MSI installs seem to want that mapping to exist.
For clarity, in case new packagers read this and get confused....MSI installs don't need any mapping. Yours may do but that doesn't mean they all do.

Sorry to nit-pick, but experience shows that newcomers pick up on broad statements like this and will battle for hours and hours trying to work things out.
Answered 07/11/2008 by: VBScab
Red Belt

Please log in to comment