Supressing Reboot
I have an setup.exe file that I need to distribute. We have all the kinks figured out except one - some of the machines need to have MDAC updated to 2.7.1. This is build into the installshield installer to check for MDAC and update it if it's not at version 2.7.1. This results in some of the workstations rebooting immediatley after the install. We are using Patchlink to send out the package, and it would work fine on all the workstations that have the latest MDAC, but for the ones it updates, at the end of the install it forces a reboot. Is there any possbile way to kill the reboot request without having to ask the vendor to re-code it's installer?
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
MSIMaker
20 years ago
After an MDAC update you MUST reboot.
If you don't then the session will use the loaded version until you do.
MDAC is an app, but its a base upgrade and MS forces you to reboot on purpose.
If you don't then the session will use the loaded version until you do.
MDAC is an app, but its a base upgrade and MS forces you to reboot on purpose.
Posted by:
primags
20 years ago
Well, I don't mind rebooting, but if it's a forced reboot, when it's sent out it could force the users computer to reboot without giving them the chance to save their work. If we can supress the MDAC reboot, we can allow them the usual reboot policy of an hour or so (they hit a snooze button), and then save there work, and then they will be rebooted. I tried the REBOOT="ReallySuppress" at the command line with no luck.
Posted by:
MSIMaker
20 years ago
I don't think you will get around it with MDAC.
It will try to replace Protected Windows System files and some of them will be most likely loaded into memory....so thats why MS forces the reboot.
I don't know how you are deploying it but I dont see a way around it unless you can upgrade MDAC prior to sending the app down.
Do you have Wake on Lan? Or maybe your deployment tool can schedule the job for after hours?
It will try to replace Protected Windows System files and some of them will be most likely loaded into memory....so thats why MS forces the reboot.
I don't know how you are deploying it but I dont see a way around it unless you can upgrade MDAC prior to sending the app down.
Do you have Wake on Lan? Or maybe your deployment tool can schedule the job for after hours?
Posted by:
primags
20 years ago
Darn. I thought about doing it at night, but since we are 24/7 (hospital), it will not work.
I was thinking about sending MDAC out before the install, but users have to have admin rights to install MDAC, even if we push it through our Patch utility...so..no good on that one either.
I am guessing I will have the users do a manual install through an icon in the Novell Application Launcher window, so they will expect a reboot when manually installing.
I was thinking about sending MDAC out before the install, but users have to have admin rights to install MDAC, even if we push it through our Patch utility...so..no good on that one either.
I am guessing I will have the users do a manual install through an icon in the Novell Application Launcher window, so they will expect a reboot when manually installing.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.