I have a set of critical patches to rollout and for this to be done through GPO, my team suggests I create one MSI which can initially install two patches (through custom actions) force a reboot and resume installation by running the other two patches and then force a final reboot.

Is this possible provided I copy the last two patches, a vbscript to run these two patches onto the target machine and execute the script which i would place in the RUNONCE key while the MSI runs before the first reboot?

To me, this seems very difficult. I really need help because this is a critical rollout.
0 Comments   [ + ] Show Comments

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.

Answers

2
ORIGINAL: sirisha.js
I have a set of critical patches to rollout and for this to be done through GPO, my team suggests I create one MSI which can initially install two patches (through custom actions) force a reboot and resume installation by running the other two patches and then force a final reboot.

Is this possible provided I copy the last two patches, a vbscript to run these two patches onto the target machine and execute the script which i would place in the RUNONCE key while the MSI runs before the first reboot?

To me, this seems very difficult. I really need help because this is a critical rollout.

Not sure why one MSI would require multiple reboots unless it's calling multiple MSIs that each require a reboot. What sorts of patches? If you mean OS or office patches, something of that nature, I think there are better methods than running them through the MSI. the MSI assumes by default, one app and (at most) one reboot which can be controlled/handled/suppressed through the REBOOT property -- except for o2k7 which uses
SETUP_REBOOT. I guess MSFT in its infinite wisdom, when it's almost second nature to use REBOOT=R in packages, has to keep us on our toes by changing things a little bit.

Why not just suppress the reboot until after all the patches are applied? Unless you're dealing with a situation where one patch which requires a reboot requires another which requires a separate reboot....is it really necessary?
Answered 12/18/2008 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
2
I agree with Owen, but would doubly suggest aggregating your reboots (if they're *really* required) simply because you're deploying through GP. Your current implementation means making your users log in THREE times! If there's a guaranteed way of pi$$ing users off, that would be a top candidate!
Answered 12/19/2008 by: VBScab
Red Belt

Please log in to comment
0
Thank you so much both of you !! Our patch mngmt guys had told me that each of these patches would require a reboot which is why I was trying to explore this route. Ultimately, I did suppress the reboot for all four patches and forced one reboot through the MSI at the end of install.
Although, I still wonder if there is a way to run an MSI, reboot the machine and resume with its install once it has finished rebooting.
Answered 12/19/2008 by: sirisha.js
Senior Yellow Belt

Please log in to comment
0
Just about the only reboot scenarios I tolerate are the replacement of files which are in use or the installation of system (kernel-level) drivers. Pretty much everything else can be worked around.
Answered 12/19/2008 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity