Skip to main content

recurring schedule behavior in sms / sccm agents

background

while investigating long boot/logon cycles, i came to the realization that there really is no documented statement on how a sms agent behaves when set against a recurring schedule.  here’s a really brief summary of what i’ve discovered so far.

first of all, it turns out that regardless of the type of recurring situation, it’s always the same.  this means whether it’s inventory or software distribution the behavior is exactly alike.  i know there’s some confusion about this… but this is what i’m seeing.

basically when an agent does not miss its schedule, it runs as it should.  duh.  i don’t know why that took me so long to process, but i finally get it now!  really!  let me explain, if you still don’t follow.

 

inventory behavior

i have a computer named “myLaptop”.  myLaptop goes home in the evenings with me and stays off since i refuse to work outside of normal business hours.  because of this, when i log on the next morning, all kinds of things happen – whether i like it or not.  :|  squaring away our environmental details, here is what the schedule for myLaptop inventory times look like:

inventoryAction lastReportDate schedule
hardware 1/28/2009 11:32:51 AM once/day
software 1/26/2009 4:33:52 PM once/5 days
heartbeat 1/28/2009 4:42:46 PM once/day

 

while myLaptop is turned off, it misses the scheduled execution for hardware inventory and heartbeat discovery.  i fire up the laptop at 1/28/2009 5:01:00 PM --because of this, the agent runs both hardware and discovery in tandem.  now if i reboot or restart the agent at any point until its next scheduled time, the agent will NOT run the inventories again

since software inventory is every 5 days, the laptop hasn’t missed its scheduled execution.  therefore, software inventory does not execute again.  if i had started the laptop at 1/31/2009, it would have run all 3 since every scheduled inventory would have been missed.

when inventory does fire off, all of the lastReportDate time frames will be reset to the current datetime value.  therefore, the machine will not run the inventory cycles again until the new scheduled times.

 

software distribution behavior

software distribution behaves exactly as i’ve detailed above.  it makes more sense though with software distribution since you control the mandatory execution timeframe.  also, it never changes the time frame.  if it misses an execution and has to run it, it doesn’t go reset the next scheduled time.  it runs again when you’ve scheduled it to go.

 

additional information

if you’re not familiar with the inventories i’ve mentioned below, they exist in the wmi class InventoryActionStatus.  This class resides in the namespace “root\ccm\invagt”.

from within wbemtest, you can view the details of the schedules by executing the following query:

select * from inventoryactionstatus
 

keep in mind that running the query in wmi returns all date fields in cim_datetime format.  if you want to see it in a better output, try this powershell command:

get-wmiobject -Namespace 'root\ccm\invagt' -Query 'select * from inventoryactionstatus' | ft -property InventoryActionID, @{label="ReportDate";expression={$_.ConvertToDateTime($_.LastReportDate)}}

 

you’ll get a list of inventory action ids.  you can find their translation here.

 

acknowledgement

thanks goes to mark mears.  :)

Comments

  1. I recently came across your blog and have been reading along. I thought I would leave my first comment. I don't know what to say except that I have enjoyed reading. Nice blog. I will keep visiting this blog very often.

    Ann


    http://largepet.info

    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 …