What do we want to achive ?

Okay so the topic pretty much says it all but the scenario is that you have Software updates deployed as Available and you would like to trigger them on a remote client without needing to actually go in to software center and manually select the update and then click “install selected”

And i know all of you have been waiting for this and so here is the magic powershell script that will make that happen!

function trigger-AvailableSupInstall { Param ( [String][Parameter(Mandatory=$True, Position=1)] $Computername, [String][Parameter(Mandatory=$True, Position=2)] $SupName ) Begin { $AppEvalState0 = "0" $AppEvalState1 = "1" $ApplicationClass = [WmiClass]"root\ccm\clientSDK:CCM_SoftwareUpdatesManager" } Process { If ($SupName -Like "All" -or $SupName -like "all") { Foreach ($Computer in $Computername) { $Application = (Get-WmiObject -Namespace "root\ccm\clientSDK" -Class CCM_SoftwareUpdate -ComputerName $Computer | Where-Object { $_.EvaluationState -like "*$($AppEvalState0)*" -or $_.EvaluationState -like "*$($AppEvalState1)*"}) Invoke-WmiMethod -Class CCM_SoftwareUpdatesManager -Name InstallUpdates -ArgumentList (,$Application) -Namespace root\ccm\clientsdk -ComputerName $Computer } } Else { Foreach ($Computer in $Computername) { $Application = (Get-WmiObject -Namespace "root\ccm\clientSDK" -Class CCM_SoftwareUpdate -ComputerName $Computer | Where-Object { $_.EvaluationState -like "*$($AppEvalState)*" -and $_.Name -like "*$($SupName)*"}) Invoke-WmiMethod -Class CCM_SoftwareUpdatesManager -Name InstallUpdates -ArgumentList (,$Application) -Namespace root\ccm\clientsdk -ComputerName $Computer } } } End {} } About the script So we are starting out with 2 Parameters function trigger-AvailableSupInstall { Param ( [String][Parameter(Mandatory=$True, Position=1)] $Computername, [String][Parameter(Mandatory=$True, Position=2)] $SupName ) These 2 are mandatory which means that the function wont run unless you give it 2 parameters so first up is $Computername just input the computername you want to trigger the install on and for $SupName you need to Input the KB-name, for example KB2134454 or if you want to install all of the available updates just input All. Next up is where the variables are set to which EvaluationState the update have and what WMI class we are gonna call later. { $AppEvalState0 = "0" $AppEvalState1 = "1" $ApplicationClass = [WmiClass]"root\ccm\clientSDK:CCM_SoftwareUpdatesManager" } There’s total of 24 different states and here’s just a sample of them

Value State 0 ciJobStateNone 1 ciJobStateAvailable 2 ciJobStateSubmitted 3 ciJobStateDetecting 4 ciJobStatePreDownload 5 ciJobStateDownloading 6 ciJobStateWaitInstall 7 ciJobStateInstalling

To get the full list of States and more info about the WMI class follow the link to Microsofts MSDN

What I’ve noticed is that when the updates first gets available they don’t get value 1 but 0, then after while some gets 1 and i haven’t really looked in to why that is yet but i might come back to that later on.

The rest of the script just handles the actual process of calling the WMI classes and get things done,

If the parameter $SupName is All or all it will trigger all available updates or if it just has a specific KB1234567 it will only trigger that one.