Scripting - Wait for install
I'm running into an issue with scripting an install. I have a two part deployment that I want to do, a base install and then a service pack, and while I have the box checked "wait for startup" which I was lead to believe will hold the script from moving on until that command is complete, it just continues on it's merry way and of course the service pack can't install while the main client is installing. Is there anyway to get this to actually give it the proper time to finish? I saw on another post you could use "start /Wait" at the beginning of your command line to force this behavior but when I add that the launch just fails so maybe that is no longer used. Here is a rundown of my script -
Unzip “$(KACE_DEPENDENCY_DIR)\Image.zip†to “$(KACE_DEPENDENCY_DIR)â€Â. Edit[/align]Unzip “$(KACE_DEPENDENCY_DIR)\iss.zip†to “c:\â€Â. Edit[/align]Run the batch file “Delete_LNK†with params “â€Â. Edit[/align]Launch “$(KACE_DEPENDENCY_DIR)\Image\setup.exe†with params “-s -f1C:\main.iss -f2c:\upgrade.logâ€Â. Edit[/align]Unzip “$(KACE_DEPENDENCY_DIR)\icons.zip†to “C:\Documents and Settings\All Users\Desktopâ€Â. Edit[/align]Run the batch file “Firewall†with params “â€Â. Edit[/align]Launch “$(KACE_DEPENDENCY_DIR)\Image\Service Pack\setup.exe†with params “-s -f1C:\sltsp.iss -f2c:\sp.logâ€Â.T[/align]dthTgh[/align]Step 7 runs long before step 4 is ever completed. Not sure what my options are other then running 2 separate scripts but I would prefer not to do that. Any suggestions?
Unzip “$(KACE_DEPENDENCY_DIR)\Image.zip†to “$(KACE_DEPENDENCY_DIR)â€Â. Edit[/align]Unzip “$(KACE_DEPENDENCY_DIR)\iss.zip†to “c:\â€Â. Edit[/align]Run the batch file “Delete_LNK†with params “â€Â. Edit[/align]Launch “$(KACE_DEPENDENCY_DIR)\Image\setup.exe†with params “-s -f1C:\main.iss -f2c:\upgrade.logâ€Â. Edit[/align]Unzip “$(KACE_DEPENDENCY_DIR)\icons.zip†to “C:\Documents and Settings\All Users\Desktopâ€Â. Edit[/align]Run the batch file “Firewall†with params “â€Â. Edit[/align]Launch “$(KACE_DEPENDENCY_DIR)\Image\Service Pack\setup.exe†with params “-s -f1C:\sltsp.iss -f2c:\sp.logâ€Â.T[/align]dthTgh[/align]Step 7 runs long before step 4 is ever completed. Not sure what my options are other then running 2 separate scripts but I would prefer not to do that. Any suggestions?
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
cblake
13 years ago
Create multiple tasks in the same script.
Task 1 is the main installer and it's last step is to create an entry in the registry or something that can be verified in task 2. Task 2 verifies the existence of the entry (or some other litmus test like the application files being present, or a certain version) and the success phase of task 2 installs the SP.
Task 1 is the main installer and it's last step is to create an entry in the registry or something that can be verified in task 2. Task 2 verifies the existence of the entry (or some other litmus test like the application files being present, or a certain version) and the success phase of task 2 installs the SP.
Posted by:
craig.thatcher
13 years ago
We've run into this with several scripts. We've coped with this by pinging the kbox a couple of hundred times as a timer to make sure the previous task completed.
Posted by:
bcreasey
13 years ago
Cblake: I've tried moving the Service pack to the second task but it still runs before this software is completed with it's install. Very strange. The only thing I can think of is that the setup starts up another process and then closes letting Kace think it's complete when really the other process is still running.
Craig, that is also a good suggestion. I need to delay something like 15 minutes so that's going to be a lot of pinging.
I'll keep looking for a solution. If anyone else has any suggestions let me know. Thanks.
Craig, that is also a good suggestion. I need to delay something like 15 minutes so that's going to be a lot of pinging.
I'll keep looking for a solution. If anyone else has any suggestions let me know. Thanks.
Posted by:
dchristian
13 years ago
bceasey,
Have you thought about doing the service pack as a distribution?
I would make a label that looks for a successful install of the base program.
If the base program is there, install the service pack.
If you wanted to get really fancy, the last thing in the script should be to make the machine check in.
That way the service pack is installed right away.
Have you thought about doing the service pack as a distribution?
I would make a label that looks for a successful install of the base program.
If the base program is there, install the service pack.
If you wanted to get really fancy, the last thing in the script should be to make the machine check in.
That way the service pack is installed right away.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.