/bundles/itninjaweb/img/Breadcrumb_cap_w.png
Hi

I have to install MS .NET 2.0 on a number of machines that require it, and before the next software install begins the machine needs a reboot for it to install properly

How can I modify the .net msi to reboot after install?

I am using Windows 2000 GPO to deploy the packages.
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity

Answers

0
In my experience, the .Net MSI will set a reboot just fine if it needs it. If you're not seeing one, it doesn't need one.

I'm curious to know why the next app requires a reboot before it will install properly. Are you seeing a message from Windows Installer to that effect? What does ProcMon tell you, in terms of file/registry activity that triggers that message?
Answered 09/28/2007 by: VBScab
Red Belt

Please log in to comment
0
Set a property in the PROPERTY table REBOOT=Force or use the following command
msiexec /i Path\.NET.msi REBOOT=Force

Giz
Answered 09/28/2007 by: gizmolala
Third Degree Blue Belt

Please log in to comment
0
ORIGINAL: VBScab

In my experience, the .Net MSI will set a reboot just fine if it needs it. If you're not seeing one, it doesn't need one.

I'm curious to know why the next app requires a reboot before it will install properly. Are you seeing a message from Windows Installer to that effect? What does ProcMon tell you, in terms of file/registry activity that triggers that message?



Well if I log into the box and execute the msi manually it will work fine, but if deploying via Windows 2000 GPO it requires a reboot for it to process properly. Very strange! It's only this particular application though Analyst Notebook 7.
Answered 09/30/2007 by: myst
Senior Yellow Belt

Please log in to comment
0
Hi Myst .. Why dont you try logging the Analyst Notebook 7 , If its a vendor msi i am pretty much sure some custom action is changing the reboot property from suppress to forcereboot . If you are able to find such custom action you can write you own Set Property custom action to change the property again to Suppress..hope this helps you...
Answered 09/30/2007 by: blacklisted_packager
Orange Belt

Please log in to comment
0
Thanks for all the replies, for now I have created a dodgey little msi package that copies a text file to the machine then reboots it [:D]

I imagine this will all become easier when we move to sms 2007 and server 2003.
Answered 09/30/2007 by: myst
Senior Yellow Belt

Please log in to comment
0
ok even easier way, use wise to create a transform file that just forces a reboot

no messy programs left lying around that way, I just didn't know you could apply the transform via the GPO when the msi installs

lets all laugh at the newbie [X(]
Answered 10/01/2007 by: myst
Senior Yellow Belt

Please log in to comment