Zum Inhalt

Powershell – SCCM – Readvertise a previously installed softwarepackage remotly (not from console)

Ever came to the situation, that you have to rerun an advertisement on a computer after a failed installation with SCCM? This could happen if you want to install flashplayer or adobe acrobat or some kind of software that is frequently used by the user. We had problems on installing software while wsus was installing its updates and the msi installer said „Hmm… perhaps, another installation is running already, so I cant do anything for you (BLAME!), sorry“. I hate this message, because its a pain in the ass to readvertise these failed softwarepackages on a single computer.

As some posts earlier mentioned, I am writing an administration webapplication to administrate our environment. This includes softwaredeployment too. We address our softwarepackages by Active Directory groups. Every time we create a new softwarepackage, we create a seperate computer collection in SCCM and link it to a newly created ad group. Every member of this ad group (computers for instance) gets the linked software by SCCM.

While it’s a bit difficult to get some automation into the readvertisement with all these groups and links, we wrote a script, that is triggered by my webgui and does this job on the client computer side for us.

As you can imagine, the first prerequisite for this script to run is: Yes, admin privilages on the client computer. If you don’t have admin rights, just do the conventional way: walk over there and install the software by hand.

What does your script in detail?

That was the question I was waiting for. It’s a bit complicated, but I try to explain what my script does.

These are the prerequisites:

  1. Admin privilages on the client computer
  2. An administrative powershell
  3. A computername, netbiosname, dns name, or ipaddress of your machine
  4. The advertisementID of your advertisement. But pay attention! The used advertisementID is the one of your computer and not the one from your SCCM server. You can get your advertisementID at your sccm client computer reports. (It’s the AdvertisementID you can see at your sccm console). If you want to get the advertisementID by packageID just scroll down a bit to the topic „Get the client advertisementID by packageID

If you have your (client) advertisementID (should look something like XXX00012, where XXX is your sitecode) we can now start on how the script actually works.
This script does everything by using (the mighty) WMI. First we query the CCM_Softwaredistribution to change a value of a current advertisement.

This key ist called „ADV_RepeatRunBehavior“. As the name says, this key controls, when your advertisement have to rerun. Normally this key has „RerunIfFail“ as value. But the advertisement doesn’t rerun over and over again until the installation is successfull (thats why you are here and reading this post).
We set the value of our advertisement from „RerunIfFail“ to „RerunAlways“.
Afterwards we query the CCM_Scheduler_ScheduledMessage to get the ScheduledMessageID (which looks like a GUID with your advertisementID as first segment).

This id is used for the scheduler to identify your advertisement.
So all we have to do is to trigger the SMS_Client (method: TriggerSchedule), pass through our ScheduledMessageID and fire it up. After submitting our request the SMS_Client on your computer comes up and with „hey, some kind of software needs to be installed (if you configured this in SCCM)“.

All we have to do after your advertisement is rerunning is to reset „ADV_RepeatRunBehavior“ to its previous state which was „RerunIfFail“.
I don’t want to destroy anything, so I read this value before changing it at the beginning of my script and put it back in, after we are done with our readertisement.

Im not finished with this script yet, it’s a little beta script to test the rerun on my local computer. There is no exception handling, no trapping, no checking on the return values.
I like this kind of raw script, because you can take what you want without renaming all functions, and rewrite all the exceptional thing. Let me know (@comments) if you want to get the final script with all the exception handing and the ping checker. I added a beta version of the rerun script at the end of this post.

Very important

You can’t rerun all of your previously commited advertisement. The SMS_Client delete your advertisements after… I don’t know on which conditions these items are deleted. Every rerunable advertisement is stored in the CCM_SoftwareDistribution database. So you have to check first if your advertisement is available.

Get the client advertisementID by packageID

If you don’t want to find the client advertisementID by reading your reports you can get it by quering the „CCM_Softwaredistribution“ for the fields „PKG_Name“ (the SCCM packagename) or „PKG_PackageID“ (the SCCM PackageID you can see at your SCCM console).
To get a list of all readvertisable advertisements, just use this WMI query on your client.

The Script

Here you can download a much more final version of the rerun script: Powershell Readvertisement Script

Published inBusinessSCCMScriptingWMI

Ein Kommentar

  1. Srinivas Srinivas

    Thank you for this wonderful script. It works well. I am looking for a script that can rerun advertisement from client computer and for the same computer as user who do not have admin rights.

    Normally user can trigger rerun advertisement by going to Software Center, selecting advertisement and click on reinstall. Same operations can we trigger using script either Powershell or vbscript.

    Thanks in advance,

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.

I accept that my given data and my IP address is sent to a server in the USA only for the purpose of spam prevention through the Akismet program.More information on Akismet and GDPR.

Diese Website verwendet Akismet, um Spam zu reduzieren. Erfahre mehr darüber, wie deine Kommentardaten verarbeitet werden.