In these cases, the administrator can extract the *.msp file from the EXTRA! Or Reflection patch executable and use the MSIEXEC command to apply the patch as described in the following sections. Extracting the Service Pack/Hotfix (*.msp) File. May 30, 2018 - Command-line options for msiexec.exe for Windows Installer 3.0 and. Msiexec /i A: Example.msi PATCH=msipatch.msp;msipatch2.msp /qb.

Hi, We have an update for CadMeasure that we need to deploy to around 400 pc's. The patch is currently in MSP file format. Ideally we would like to be able to deploy this via GPO or script or a combination of the 2. The problems we have are that the patch requires local admin rights to install and it needs to be installed silently / hidden. Does anyone have a reccomended method for doing this? I have tried referencing the following 2 links but the package does not seem to deploy. I know seungri mp3 download. Note: Package is being deployed to Windows 7 computers.

Thanks both for the advice. From what you've said and everything else I've read, it looks like the only way to deploy this via GPO would be to repackage the MSP with the original MSI and then redeploy to all the computers that need it. I'd rather avoid doing this as the original install is from a standard desktop image, not an MSI deployed by GPO. Also the original is a fairly hefty install taking anything from 30mins to an hour to install per pc where as the patch only takes a couple of mins to run. Would there be anyway to script the install so that it runs after logon? It would need to be hidden and run with local admin credentials, something the users do not have by default.

Yes, as I stated in option c), you always have the ability to script the install as a startup script. To go further with what AbqBill stated, I'd recommend checking for the CLSID in the registry as a valid identifier that it is installed.

All MSIs create them and it's how Microsoft prodcuts internally verify this (or at least SCCM, SCUP, etc.). Install it manually on a machine, find out what the CLSID is, and then in your custom startup script, check the registry for that specific CLSID to determine whether or not it's been applied. If necessary, you can also build in pre-requisite rules as well, OS bit-ness if you have 32 and 64-bit workstations, operation system version, etc.

Hello, I'm attempting to install software (.msi) and patch file (.msp) with same command-line as follows: msiexec /i package.msi /update update.msi /quiet /norestart /l*v c: temp log.log Even I'm located in same directory with these files, I get error that one of these packages can't be found. If I put full path ahead of.msi and.msp files, then it works. This causes problems, because I'm going to deploy this with SMS and Package folder name on system32 ccm cache might change if settings are updated for program. I know that I could create two separate programs for msi and msp but I want to make installation happen with one command line. How should I modify my command-line to make it work? I can't see why it won't work if both files are located in same directory where command is executed.

Using the update switch or Patch property you should eventually find won't work at all with SCCM. That's what I found with SCCM 2007. Firstly your command line syntax is not complete. You must include the full path to the MSP with either the switch or the property and you will find reference to this in the Windows Installer SDK.

When you do get the syntax right you should still be returned a error code '1651 - Windows Installer does not permit the patching of managed advertised products. At least one feature of the product must be installed before applying the patch.' Withstanding this is the use of Administrative installations, as suggested previously above. Otherwise, dare I suggest patches are not the way forward and updates should be minor or major upgrades, incrementing the versions numbers and reinstalling the products in the process?