Deploy .MSP packages without WSUS

Yes, you can deploy .MSP patch files using SCCM as either an Application or a Package, depending on your requirements. Here’s how you can do it:

If the .MSP file is an update for an existing application installed via MSI, follow these steps:

1. Create the Application
   • In SCCM, go to Software Library > Application Management > Applications.
   • Click Create Application > Select Manually specify the application information.
   • Provide a name, publisher, and other details.
2. Add a Deployment Type
   • Click Add Deployment Type > Select Script Installer.
   • Under Content Location, specify the folder containing the .MSP file.
   • Set the Installation Program to:

          msiexec /p PatchFile.msp /qn /norestart
     

   • Set the Detection Method to check the updated version of the application in the registry or WMI.
3. Deploy the Application
   • Deploy it to a Device Collection.

If you don’t need extensive tracking or the .MSP isn’t MSI-based:

1. Create a Package
   • In SCCM, go to Software Library > Application Management > Packages.
   • Click Create Package and specify the content location where the .MSP file is stored.
2. Create a Program
   • Set the Command Line to:

          msiexec /p PatchFile.msp /qn /norestart
     

   • Choose whether it requires user interaction (usually hidden/silent mode is best).
3. Deploy the Package
   • Distribute it to your DP, then deploy it to the target collection.

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin

Hi, @Nesma

Thank you for posting in Microsoft Q&A forum.

Here is a guidance to deploy .MSP packages using SCCM:

https://www.prajwaldesai.com/deploying-adobe-reader-updates-using-sccm/

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".

After the way you tag questions on Q&A is updated, for any "Microsoft Configuration Manager" related problem, you can tag it with "Microsoft Intune", and then "Microsoft Configuration Manager" as the child tag.