About reboot during package development
Hi All,
I think this is the place I can get my answer, finally!
Scenario: Packages we will repackage are for SMS 2003 deployment, preferred format is MSI. Some of them require reboot, so my question is mainly how we build reboot methodology for MSI packages.
- Because we always add /qn to avoid user interface during MSI installation, forcereboot action and schedulereboot action won't work.(this is according to Microsoft msdn, these 2 actions only work with user interface enabled installtion)
- We usually add "REBOOT=ReallySuppressed" in order to avoid automatic reboot, since user may still be working on that client during deployment.
How do you handle reboot in this case? ideal way I think is to prompt user to choose reboot now or later. But how? And assuming we have some way to prompt, then how we ensure there is always one prompt even if we deploy 10 packages which all require reboot?
Thanks a lot!
I think this is the place I can get my answer, finally!
Scenario: Packages we will repackage are for SMS 2003 deployment, preferred format is MSI. Some of them require reboot, so my question is mainly how we build reboot methodology for MSI packages.
- Because we always add /qn to avoid user interface during MSI installation, forcereboot action and schedulereboot action won't work.(this is according to Microsoft msdn, these 2 actions only work with user interface enabled installtion)
- We usually add "REBOOT=ReallySuppressed" in order to avoid automatic reboot, since user may still be working on that client during deployment.
How do you handle reboot in this case? ideal way I think is to prompt user to choose reboot now or later. But how? And assuming we have some way to prompt, then how we ensure there is always one prompt even if we deploy 10 packages which all require reboot?
Thanks a lot!
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
A while ago, at my last client,. I built a 'We need to reboot your workstation' HTA for general usage. We subsequently used it for exactly this scenario, where a sequence of installs would require a reboot at the end. It was simple enough - it used the WMI shutdown method with appropriate parameters, but allowed the user to cancel altogether. There was also (obviously) an override to force a reboot.
Posted by:
dunnpy
13 years ago
I've always managed it by suppressing the reboot, safe in the knowledge that the company policy dictates that machines are shutdown every evening and started up again in the morning - energy use policy and green credentials [:)]
I also favour late afternoon deployments, so they won't notice the sofware until they've started back up again in the morning.
If I'm running a deployment for a project I'll advise the client liaison person tell users to look for the icon (desktop or start menu), leave it 15 minutes and then manually reboot the machine if the users want to use the software as soon as it has deployed.
Hope this helps,
Dunnpy
I also favour late afternoon deployments, so they won't notice the sofware until they've started back up again in the morning.
If I'm running a deployment for a project I'll advise the client liaison person tell users to look for the icon (desktop or start menu), leave it 15 minutes and then manually reboot the machine if the users want to use the software as soon as it has deployed.
Hope this helps,
Dunnpy
Posted by:
systeman
13 years ago
thanks Vbscab and Dunnpy!
You just pointed out some direction for me to consider about. I will check if your solution could be applied to our business or not. thanks again!
You just pointed out some direction for me to consider about. I will check if your solution could be applied to our business or not. thanks again!
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.