Deployment Solution

HI

after installation of SMP SP2 mp1.1 rollupV3

I have a strange issue where UpdateSbsinfo is running every 10 seconds on my task/package servers a little further investigation and after refreshing the "Windows computers requiring Altiris package server agent upgrade"  which originally showed 0 and after refresh showed all of the task servers I had updated according to the document howto81832

The UpdateSbsinfo now seems to be running totally randomly sometimes 7 minutes then 5 then1 then4.........

How often does this normally run ??

what defines when it should run ?

C

UpdateSBSInfo is how any changes you make in the console that affects PXE is sent to the PXE server.  We have a doc that details this here:

technical-document-about-ds-71-sp1-architecture-and-data-flow

However, here's the short version:

You send a job to a computer to boot to automation via PXE.  We send out 2 tasks - one to the client to reboot, and the other to the Site Server to be ready for the reboot.  The 2nd task is the UpdateSBSInfo task, and it will create an SBS file via the deployment agent on the site server.  The SBS file is read by the NBS Interface service which hands the data to the NBS Server service (PXE) so that when the client actually reboots, the PXE Server Service actually knows what to do with the client.  Same thing happens for any config changes to PXE.  So it can run often depending on how much you're doing with deployment solution. VERY often if you're really busy.

TIP:  In DS 7.5 it never runs.  We no longer use SBS files.  Instead, when a client boots, the PXE server service pings the NS to ask what to do, and then responds.  It's more efficient.  Look for DS 7.5 later this year (fall) as currently scheduled and if nothing happens.

It'll calm down as your jobs calm down.  :)  The hardest part of the updateSBSinfo task is simply connecting the dots to what it is, vs what it looks like.  It IS literally the way to update the SBS information on the site server.  It is NOT some rogue task that simply runs out of control.  It IS a pain in the neck that we're pulling from the product in the next release... never mind - I didn't say that...  :P  Oh, and I should at least close with it DOES work.  There.  It's an upbeat and positive ending.  :D