Patching problems
Hi guys! Back again with what i think will be another obvious question:
Is there a way to automatically ignore MSI errors on a silent install? There is a problem with a file in a patch i'm trying to apply and if I just ignore it during a normal install the patch works fine and everything is ok, but during a silent install it still brings up the box with retry, cancel and ignore.
Also from what I have read there is no way to directly edit a MSP file, does anyone have any good material, links or tips on making changes to existing patches?
Thanks!
EDIT:: Also, I have been told that doing an admin install and applying the patch to it works, but how do I get that slipstreamed admin install back to an MSI?
EDIT:: OK after a bit of reading if i use msiexec /a original.msi /p patch.msp this creates an admin install point with the patch applied, but does this also apply the patch to the original.msi??
Is there a way to automatically ignore MSI errors on a silent install? There is a problem with a file in a patch i'm trying to apply and if I just ignore it during a normal install the patch works fine and everything is ok, but during a silent install it still brings up the box with retry, cancel and ignore.
Also from what I have read there is no way to directly edit a MSP file, does anyone have any good material, links or tips on making changes to existing patches?
Thanks!
EDIT:: Also, I have been told that doing an admin install and applying the patch to it works, but how do I get that slipstreamed admin install back to an MSI?
EDIT:: OK after a bit of reading if i use msiexec /a original.msi /p patch.msp this creates an admin install point with the patch applied, but does this also apply the patch to the original.msi??
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
JdotQ
17 years ago
I'm not sure about automatically ignoring the error prompts during a silent install...
Once you have the source admin install patched, you should redeploy the package so the clients get the latest patched version of the msi. If you are using Active Directory GPO to deploy the software, simply select "Redeploy Application" from right clicking on the package > all tasks. This will invoke a reinstallation on the next reboot (if installing computer side) and will install the latest patched version.
Once you have the source admin install patched, you should redeploy the package so the clients get the latest patched version of the msi. If you are using Active Directory GPO to deploy the software, simply select "Redeploy Application" from right clicking on the package > all tasks. This will invoke a reinstallation on the next reboot (if installing computer side) and will install the latest patched version.
Posted by:
mazessj
17 years ago
Houston,
When an admin install point is created by executing msiexec.exe /a <Original.msi>, the files from the MSI are extracted into this directory so that they can then be accessed from the network or be patched with an MSP. A modified MSI is also written to the admin install point directory that references the extracted files. Apply the MSP to the admin install point and the files and MSI will be updated accordingly. Deploy to your users by pointing to the MSI in the admin install point. If you're deploying to remote users, be sure to bundle the entire directory structure.
However, I think what you're asking for, in an indirect way, is for a way to apply the patch directly to the original MSI and create a new (self-contained) MSI without expanding the files into an admin install point. I don't think you can do that. As for rebundling an admin install point back into a single self-contained MSI, I'm not sure how to do that, whether you can, or whether you should (bad practice, perhaps?). Maybe someone can chime in on this.
As for suppressing the Retry/Cancel/Ignore dialog, you can try running the installation with no UI (/qn). It only displays this dialog if you run it with a UI (/qb or greater). In general, to ensure completely non-interactive, silent installations for your users, you should always use /qn.
--Josh
When an admin install point is created by executing msiexec.exe /a <Original.msi>, the files from the MSI are extracted into this directory so that they can then be accessed from the network or be patched with an MSP. A modified MSI is also written to the admin install point directory that references the extracted files. Apply the MSP to the admin install point and the files and MSI will be updated accordingly. Deploy to your users by pointing to the MSI in the admin install point. If you're deploying to remote users, be sure to bundle the entire directory structure.
However, I think what you're asking for, in an indirect way, is for a way to apply the patch directly to the original MSI and create a new (self-contained) MSI without expanding the files into an admin install point. I don't think you can do that. As for rebundling an admin install point back into a single self-contained MSI, I'm not sure how to do that, whether you can, or whether you should (bad practice, perhaps?). Maybe someone can chime in on this.
As for suppressing the Retry/Cancel/Ignore dialog, you can try running the installation with no UI (/qn). It only displays this dialog if you run it with a UI (/qb or greater). In general, to ensure completely non-interactive, silent installations for your users, you should always use /qn.
--Josh
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
