.msi + .mst + .msp via GPO
How is that for some alphabet soup... So i have a vendor provided .msi (ESRI ArcReader 9.0) that we have created a transform for. I've been able to deploy this in my testlab without any problem. Now ESRI has released the SP1 patch for ArcReader as a .msp. Does anyone have a good way to deploy this combination of files via GPO?
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
WiseMonkey3
20 years ago
Hi, This is what I like to do with this situation;
Turn the supplied MSI into an admin installation - Run MSIEXEC.exe /A "Path to .MSI file". This will generally ask for a destination location and explode out the MSI with all its files outside. Once this is done you can generally apply the patch to the admin installation by running MSIEXEC /a "Path to Admin .MSI" /p "Path to .MSP" this should merge the MSP into your admin install. Then create your transform file and do the GPO thing.
One of the benifits with this method is once you have your admin install with the MSP applied and in AD, if you then release the app to users and another MSP comes after you can apply the new MSP to your admin install again and this time just redeploy in AD, it will be reinstalled to all users that have the previous version installed.
Turn the supplied MSI into an admin installation - Run MSIEXEC.exe /A "Path to .MSI file". This will generally ask for a destination location and explode out the MSI with all its files outside. Once this is done you can generally apply the patch to the admin installation by running MSIEXEC /a "Path to Admin .MSI" /p "Path to .MSP" this should merge the MSP into your admin install. Then create your transform file and do the GPO thing.
One of the benifits with this method is once you have your admin install with the MSP applied and in AD, if you then release the app to users and another MSP comes after you can apply the new MSP to your admin install again and this time just redeploy in AD, it will be reinstalled to all users that have the previous version installed.
Posted by:
dinozilla
17 years ago
ORIGINAL: WiseMonkey3
Hi, This is what I like to do with this situation;
Turn the supplied MSI into an admin installation - Run MSIEXEC.exe /A "Path to .MSI file". This will generally ask for a destination location and explode out the MSI with all its files outside. Once this is done you can generally apply the patch to the admin installation by running MSIEXEC /a "Path to Admin .MSI" /p "Path to .MSP" this should merge the MSP into your admin install. Then create your transform file and do the GPO thing.
One of the benifits with this method is once you have your admin install with the MSP applied and in AD, if you then release the app to users and another MSP comes after you can apply the new MSP to your admin install again and this time just redeploy in AD, it will be reinstalled to all users that have the previous version installed.
Hi,
I tested the same with Microsoft Office Communicator 2005
But not extract it first, but rather straight to merge them with the commandline
msiexec /p xxx.msp /a xxx.msi
i do notice a source folder created immediately after that...which contains source from the msi.
Sadly after that, when deploy through AD, the installation fails with fatal error, which I had no idea what is going wrong.
Could the method I applied(not extract first, but let the command extract and merge) cause this problem?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.