SHUTDOWN.EXE - DEVICE NOT READY
I placed this in the scripting section but it seems not so many read that area.
I have 12 apps that are being installed in sequence via a massive batch file I made. All of this is happening during the GPO startup event. I need to do this in this manner because half are MSI and the others are install sheild exes. I make it to the point where I need to perform a reboot before the process can continue. I place the line shutdown -r -f in my batch. These are windows XP SP3 devices. I get the error "device not ready". I looked all over and see references to remote shutdowns and this being an issue pre SP1. There is nothing mentioned about how to do this in SP3. I also tried using PSCEXEC and got the same results although PSEXEC placed output saying the process had begun although it never actually did restart the PC.
Has anyone had to string multiple MSIs and EXEs into a monster batch and restart in the middle? Is there another options besides SHUTDOWN to do this? I'm in a pinch here so any advice is definetly appreciated.
jimm
I have 12 apps that are being installed in sequence via a massive batch file I made. All of this is happening during the GPO startup event. I need to do this in this manner because half are MSI and the others are install sheild exes. I make it to the point where I need to perform a reboot before the process can continue. I place the line shutdown -r -f in my batch. These are windows XP SP3 devices. I get the error "device not ready". I looked all over and see references to remote shutdowns and this being an issue pre SP1. There is nothing mentioned about how to do this in SP3. I also tried using PSCEXEC and got the same results although PSEXEC placed output saying the process had begun although it never actually did restart the PC.
Has anyone had to string multiple MSIs and EXEs into a monster batch and restart in the middle? Is there another options besides SHUTDOWN to do this? I'm in a pinch here so any advice is definetly appreciated.
jimm
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
darkfang
14 years ago
There's a good chance that you can strip the .msi from these InstallShield .exe. Then, you will have to configure them to remove any LaunchCondition they may have but it will make your deployment much easier (and without a reboot between installation)
Posted by:
JimmPanik
14 years ago
Sorry for not clarifying... the Install Shield installers are not the ones that house an MSI inside, these are the old school setup.exe routines. I've tried just about everything I can think of and haven't figured out why I can't simply have a shutdown command in a strtup script.
jimm
jimm
Posted by:
PackageExpert
14 years ago
ORIGINAL: JimmPanik
Sorry for not clarifying... the Install Shield installers are not the ones that house an MSI inside, these are the old school setup.exe routines. I've tried just about everything I can think of and haven't figured out why I can't simply have a shutdown command in a strtup script.
jimm
Perhaps you have to repackage those legacy Setups into an MSI...
Posted by:
anonymous_9363
14 years ago
Perhaps you have to repackage those legacy Setups into an MSI...That would certainly be my gambit. Good suggestion. At least then you can produce a log for each and determine where the hold up is, if it still exists once you have the MSI versions.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.