Updating Administrative MSI with MSP fail
Hello, according to Microsoft documentation, updating source of software distribution share should be very easy. All you have to do is to update the administrative installation source with the MSP with the command "MSIEXEC /p "patch.msp" /a "source.msi" /qb".
But I have tried several time with a lot of software (Office, Adobe Acrobat, .Net Framework, Visio, etc...) and none so far have worked.
When patching I got no problem but when installing new version I ALWAYS have error in the Event Log.
Error is Event 108 "Failed to apply changes to software installation settings. <failure consequence>. The error was <error message>. The installation source for this product is not available. Verify that the source exists and that you can access it"
Am I the only one to get these error. Am I missing something?
Thanks for your help!
But I have tried several time with a lot of software (Office, Adobe Acrobat, .Net Framework, Visio, etc...) and none so far have worked.
When patching I got no problem but when installing new version I ALWAYS have error in the Event Log.
Error is Event 108 "Failed to apply changes to software installation settings. <failure consequence>. The error was <error message>. The installation source for this product is not available. Verify that the source exists and that you can access it"
Am I the only one to get these error. Am I missing something?
Thanks for your help!
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
AngelD
18 years ago
remove the /qb parameter so you can specify in which directory the admin installation should be placed.
Posted by:
wd40
18 years ago
Still not working... tried with Acrobat Pro and I got the same error....
Posted by:
AngelD
18 years ago
After you've installed the administrative installation (/a), try
"MSIEXEC /p "<full path to>\patch.msp" /a "<full path to>\source.msi"
"MSIEXEC /p "<full path to>\patch.msp" /a "<full path to>\source.msi"
Posted by:
wd40
18 years ago
Doesn't work..... I have discovered that I had to publish an update to my policy for this to work.... never tried because I will not use this unless I really need to apply a critical update.
Thanks
Thanks
Posted by:
nheim
18 years ago
Hi wd40,
that can't work at all! You're missing the most important point here:
Never, ever change an install point, when a GPO points to it!
You break the connection with the peer, where the app is already installed.
If for some reason, a repair kicks in on one of those, you get the error with the 'path not found' because the MSI-file is not the same anymore.
As you figured out yourself, the only exeption from this, is to do a 'redeploy' in the GPO right after you did the update, to keep all the installations in sync.
Hope this clarifies the situation.
Regards, Nick
that can't work at all! You're missing the most important point here:
Never, ever change an install point, when a GPO points to it!
You break the connection with the peer, where the app is already installed.
If for some reason, a repair kicks in on one of those, you get the error with the 'path not found' because the MSI-file is not the same anymore.
As you figured out yourself, the only exeption from this, is to do a 'redeploy' in the GPO right after you did the update, to keep all the installations in sync.
Hope this clarifies the situation.
Regards, Nick
Posted by:
wd40
18 years ago
So am I correct with what I said? Do I need to publish a new package that updates the first one in the same GPO to get my updates applied?
Thanks!
Thanks!
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.