Skip to main content

forcing a task sequence to rerun … from powershell

well, kind of.  steve rachui wrote this genius little gem about how to manage the instances of the configmgr agent scheduler to manipulate a task sequence to rerun.  as you’ll note in the post, he didn’t indicate a method to automate it.  this is actually rather easy to accomplish from powershell.

first of all, our example … we’ll use steve’s screenshots as reference.  here’s the id that we want to get rid of: CEN20018-CEN00027-DBBBC9D6.

to be quite veracious and unerring, we should use the exact task sequence id in question.  we can set that to a variable just for kicks.

$tsid = “CEN20018”
 
alright, now that we have that, let’s examine the command we’re going to use.  to get information out of wmi, we have to use the get-wmiobject cmdlet.  ordinarily, you could just provide the class name you want to look at, but as steve noted in his post, you need to connect to a different namespace: root\ccm\scheduler.  let’s retrieve all the classes of this namespace using –list.
 
get-wmiobject –namespace “root\ccm\scheduler” –list
 
 
here’s a snippet of the expected output:
...
__Win32Provider {} __SystemSecurity {GetSD, GetSecuri.. CCM_Scheduler_History {} __NotifyStatus {} __ExtendedStatus {} __SecurityRelatedClass {}
...
 

ah, there we go.  the class we’re looking for is ccm_scheduler_history.  next thing we’ll do is pull the instances of this class.  if we just pull the class, it’ll be quite a nasty output, so let’s concentrate on what’s important for now: the schedule id.

Get-WmiObject -Namespace "root\ccm\scheduler" -Class ccm_scheduler_history | ft scheduleid


now we get a succinct output of just the schedule ids.  there’s the schedule id we’re looking for!

{00000000-0000-0000-0000-000000000027}
{00000000-0000-0000-0000-000000000061}
{00000000-0000-0000-0000-000000000011}
{00000000-0000-0000-0000-000000000022}
CEN20018-CEN00027-DBBBC9D6
{00000000-0000-0000-0000-000000000023}
{00000000-0000-0000-0000-000000000031}
{00000000-0000-0000-0000-000000000021}


let’s pull it all together and see how it looks.

Get-WmiObject -Namespace "root\ccm\scheduler" -Class ccm_scheduler_history | where { $_.scheduleid -like "$tsid*" }


perfect.  now we got back the right instance of the class.  i’m going to set this to a new variable called $tsinstance because i’m just that creative.

$tsinstance = Get-WmiObject -Namespace "root\ccm\scheduler" -Class ccm_scheduler_history | where { $_.scheduleid -like "*$tsid*" }
 

now, finally, we’re to the point where we can get rid of the thing.  so … how?  well… as it turns out, there’s a cmdlet for that.  all we need to do is pass the object to remove-wmiobject.  that just rocks.  here’s the finished command.

$instance | Remove-WmiObject


and if you just want one long command, here’s that as well:

Get-WmiObject -Namespace "root\ccm\scheduler" -Class ccm_scheduler_history | where { $_.scheduleid -like '*CEN20018*' } | Remove-WmiObject

Comments

  1. Perfect! I found Steve's post and was trying to make it work through VBS but Powershell is even better. Thanks!

    ReplyDelete

Post a Comment

Popular posts from this blog

how to retrieve your ip address with powershell...

update: this is how it’s performed in powershell v3 as demonstrated here.(get-netadapter | get-netipaddress | ? addressfamily -eq'IPv4').ipaddress update: this is by far the easiest.PS C:\temp> (gwmi Win32_NetworkAdapterConfiguration | ? { $_.IPAddress -ne $null }).ipaddress
192.168.1.101
are you laughing yet?  i know you probably find this topic amusing.  it's really interesting though.  whenever you get over it, i'll do this in the standard cmd.exe interpreter and then in powershell to show you what kind of coolness powershell does.done?  okay, good.  this is an interpretation of a demo that bob wells did at our smug meeting.  hope you like it.i should tell you, it's not as simple as the title would lead you to believe.  i like doing that little slight-of-hand thing since it gives the impression that i'm painting a very easy target on my back for your criticism (though it's probably true in other ways)!  the idea is that we want to retrieve just the ip ad…

understanding the “ad op master is inconsistent” alert

i use the term “understanding” loosely.  this is by far no definitive guide on this particular alert, just a few things i have picked up in my attempt to understand it.let’s look at the context of the alert:The Domain Controller's Op Master is inconsitent. See additional alerts for details.
first of all, it gives very little information.  the only particularly useful detail is that it indicates which server is having the issue.  other than that, just a spelling error as there are no additional critical alerts to look at for details.this rule, as you know, comes from a sealed mp.  therefore, we can’t modify anything in it except the overrides.  the couple i’ve tinkered with are:interval (sec) log success event to begin with, interval (sec) is just set way too high.  the default is 60 seconds.  why on earth would anyone want to know that your op master consistency may be off, every minute?  actually, i could think of a few reasons, but really, it’s overkill.  the way the script works…

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point. even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch.I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.DETECTIONstatus messagestake a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough material to …