/Update vs /p and Source MSI Question
These are probably really easy questions, but finding explicit answers seems to be harder.
Is there any difference between /update vs /p?
Is it possible to specifically specify the original source MSI that the MSP will be patching against?
This question is based on an MSP that we recieved from a vendor to patch thier original (already installed) MSI which it can't seem to find unless you specifically click on it. The higher ups don't want to do an administrative patch and reinstall all because of a fear that it might break other versions of the install. Convincing them that this is probably the correct approach because OF the multiple versions (ie: standardization) has proven impossible.
Is there any difference between /update vs /p?
Is it possible to specifically specify the original source MSI that the MSP will be patching against?
This question is based on an MSP that we recieved from a vendor to patch thier original (already installed) MSI which it can't seem to find unless you specifically click on it. The higher ups don't want to do an administrative patch and reinstall all because of a fear that it might break other versions of the install. Convincing them that this is probably the correct approach because OF the multiple versions (ie: standardization) has proven impossible.
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
Is there any difference between /update vs /p?None whatsoever :-)
Is it possible to specifically specify the original source MSI that the MSP will be patching against?Er...the command line requires you to point at an MSI. Surely your deployment system contains a copy?
Posted by:
jmaclaurin
13 years ago
Thanks for the quick reply.
For question 2:
Instead of:
From http://msdn.microsoft.com/en-us/library/aa367988(v=vs.85).aspx
msiexec /p msipatch.msp;msipatch2.msp /n {00000001-0002-0000-0000-624474736554} /qb
What I was thinking is something more like this:
msiexec /p msipatch.msp;msipatch2.msp /n "\\server\share\original.msi" /qb
Same type of idea as:
msiexec /i A:\Example.msi PATCH=msipatch.msp;msipatch2.msp /qb
Even though in the HKLM.....\Uninstall\{guid} the InstallSource path is correct, the MSP can't seem to locate it in a silent install, but in a manual install, when prompted, just click the MSI it brings you to in the path (click browse and then click the MSI) and installs no problem.
For question 2:
Instead of:
From http://msdn.microsoft.com/en-us/library/aa367988(v=vs.85).aspx
msiexec /p msipatch.msp;msipatch2.msp /n {00000001-0002-0000-0000-624474736554} /qb
What I was thinking is something more like this:
msiexec /p msipatch.msp;msipatch2.msp /n "\\server\share\original.msi" /qb
Same type of idea as:
msiexec /i A:\Example.msi PATCH=msipatch.msp;msipatch2.msp /qb
Even though in the HKLM.....\Uninstall\{guid} the InstallSource path is correct, the MSP can't seem to locate it in a silent install, but in a manual install, when prompted, just click the MSI it brings you to in the path (click browse and then click the MSI) and installs no problem.
Posted by:
anonymous_9363
13 years ago
MSDN should contain a fuller example.
msiexec /p msipatch.msp;msipatch2.msp /n "\\server\share\original.msi" /qb is the correct way.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.