Uninstall MSI Applications with Run Scripts and CMPivot

As Config Manager admins, we're frequently approached by managers that want us to do something NOW. Enter the Run Scripts feature in Config Manager. If you're not familiar with CMPivot, Run Scripts, and Client Notification then it would be super helpful for you to read a few of my past blogs.

Intro to CMPivot and Run Scripts A Deeper Dive into CMPivot, Run Scripts, and Client Notification Adding Parameters to Run Scripts
Today's ramble is on how to use Run Scripts with a parameter to instantly uninstall an MSI application from your device(s). We're going to use a quick 12 year old PowerShell script (it's an oldie, but a goodie) I found on Stack Overflow.
#Uninstall an MSI application
Param( [Parameter(Mandatory=$True)] [string]$ApplicationName )
Get-WmiObject-ClassWin32_Product|Where-Object {$_.Name -eq$ApplicationName} |foreach-object-process {$_.Uninstall()}
In you SCCM or MEMCM or MECM or whatever you call it now console, go to Software Library > Scripts and click on

Run Scripts with Parameters in MEMCM (R.I.P. SCCM)

How do you use Parameters in MEMCM's (R.I.P. SCCM) Run Scripts?
How do you use Parameters on the Run Scripts feature? You get three guesses, but the first two don't count. That's right, you create a script with standard PowerShell Parameters and you build it out in MEMCM. In your MEMCM console, navigate to Software Library > Overview > Scripts. If you're not familiar with Run Scripts in MEMCM, check out my previous Blog articles on it.

Click on Create Script. In the Create Script Wizard that pops up input a Script Name, pick between PowerShell or PowerShell in your Script Language, import or paste in your script with Parameters, and click on Next.

My demo script for this article (scroll alllll the way down, it's at the bottom) is about an 8 out of 10 on the cool factor, and about a 3 out of 10 on the usefulness factor. Long story short, the script will make a computer talk. There are two Parameters that you can input, one for "what do you want to say?&qu…

CMPivot, Run Script, & Client Notification (Again!)

What is Client Notification?
Client Notification in SCCM is one of the most powerful features of SCCM that most people never know they use on a regular basis. In SCCM 2012 SP1, Client Notification was introduced to help get rid of the Slow Moving Software name and help get SCCM into the business of real-time actions. Client Notification consists of a Notification Manager, a Notification Server, and a Notification Agent which is part of CCMEXEC on the client.
The Notification Agent on the client attempts to initiate communication with the Notification Server (your Management Point aka MP) via TCP on port 10123 and it keeps this “conversation” alive checking in every 15 minutes. If TCP on port 10123 isn’t available, the client fails over to using HTTP/HTTPS on port 80/443 and this communication occurs every 5 minutes.
DNS Resolution from the MP to the Client is NOT required, because the client is initiating the communication with the MP. As long as the client can resolve the MP, the co…