February 20, 200521 yr I've always done a direct edit on the msi and have never had reboot issues. I know this contrary to best practice which dictates "dont edit the msi file", but hey it's worked for me.
February 20, 200521 yr I directly edit the MSI too, but the Sun one is kind of weird. The majority of registry entries it writes aren't created by the MSI but by stuff run by the MSI.
February 21, 200521 yr Well I change the RebootYesNo to "No" and I manually ad to the msi file the REBOOT property with the corresponding "ReallySuppress" entry. And I've never had the issues described in this thread. For the sake of completeness, I install the package during RunOnceEx.
February 21, 200521 yr Well I change the RebootYesNo to "No" and I manually ad to the msi file the REBOOT property with the corresponding "ReallySuppress" entry. And I've never had the issues described in this thread. For the sake of completeness, I install the package during RunOnceEx.Please correct me if I'm wrong. But the "RebootYesNo" is a private property, that doesn't affect the installation. I know it is "Yes" by default, but all of my msi's have that even if they don't reboot."REBOOT" is a public property, so no need to edit the msi directly because public properties can be manipulated though commandline. Also, I don't know why reboot=reallysuppress didin't work when I tried it. Only reboot=suppress works for me.Tip: All UPPERCASE properties, are public properties. You can modify them though commandline.All lowecase properties (or properties with alternating cases) are private properties. You cannot modify them easily. I believe it is useless to edit a private property.
February 21, 200521 yr Well I commonly change the private properties and they do take. Using AdminStudio.
Create an account or sign in to comment