Video Screencast Help

Inventory Runs Twice on SMP Server

Created: 09 May 2012 | 6 comments

On my SMP 7.1 SP2 server, I enabled both Full and Delta inventory policies in the SMC.  They run as scheduled and complete successfully on the few systems I have with the SMP agent although I noticed that on my SMP server itself, full and delta inventories each run twice (one at the scheduled start time and the second about 20 minutes later).  Got this info from viewing the task runs of each policy where the workstations run full/delta only once as expected.

Note that I'm licensed for CMS 1 where the SMP server is the only system with the SMP agent loaded in my environment.  Does anyone have ideas on this behavior?  Can't confirm whether this double inventory only occurs on servers (not just the SMP server) since we don't want Altiris on these systems.

Comments 6 CommentsJump to latest comment

HighTower's picture

Oh yeah, I have this with all sorts of policies, not just inventory.  Support claims to have never seen this before.

Beyond that I don't have any suggestions for you.

EathenR's picture

I've been experiencing the same problem.  I have a weekly inventory policy and it ran twice in one day.  Did you find an answer?

Clint's picture SMP server still runs both full and delta inventories twice on their respectively scheduled days.  Since this wasn't happening on any of my client workstations, I deemed it minor and never opened up a case with Symantec Tech Support to pursue the matter.


Tom Fisk's picture

We are having the same problem with Inventory Policies. I have opened a Case with Support but no resolution yet. The Policies run on schedule, and then run again randomly off schedule. So far it looks like the second run is triggered by a reboot, or a restart of the Agent service. This is happening on both server and workstation clients.

HighTower's picture

Our second execution happens anywhere from 20 minutes to 3 hours after the first execution.

My coworker states that Support told him that this is a "known issue" and that it's going to be fixed in the next release.  However, we're in the 7.5 beta and we're testing it.

HighTower's picture

So far it appears that this issue has been fixed in 7.5.