KNOWN ISSUE: After changing the custom schedules for Collect Inventory Policies, clients are executing the Policies twice. Once on schedule and then again the next mornings when no policy is scheduled.


Article ID: 157681


Updated On:


Management Platform (Formerly known as Notification Server)


After changing the custom schedules for his Inventory policies each policy runs twice.
They run at the scheduled time in the evening. And then they run sometime the next morning.

The agent logs show each run, both the scheduled and unscheduled, is being invoked by the same schedule Guid, but it lists different times. When it runs on schedule the logs show that scheduled time. When it run off schedule the logs show the unscheduled time.

The following is for the unscheduled time:
Date: 7/17/2012 5:55:12 AM
Process: AeXNSAgent.exe (3704)
Module: AgentScheduler.dll
Source: ScheduleEngine
Description: Schedule {bec7883c-b8d1-4469-bd5d-4c8a87c25eb4} ({BEC7883C-B8D1-
4469-BD5D-4C8A87C25EB4}) triggered at 2012-07-17 05:55:12 -7:00

The above came from running only the Collect Delta Hardware policy. Per the Inventory policy, and confirmed in the client policy XML file, the schedule is set to run at 2230 hours repeating weekly on Mon, Tue, Wed, Thu, Fri, and Sat using agent time.

The logs show the same entry before the scheduled run but with the correct date/time at the end.
The policies clearly show only the one scheduled time, in the evening.
The client policy XML file shows the same scheduled time as is shown on the policy.
If all the Inventory policies are enabled then they all run at the same non-scheduled time.


Known Issue.


This issue has been reported to the Symantec Developement team. A fix has been provided with ITMS 7.1 SP2 MP1 Rollup v3. See HOWTO81832

Applies To

Symantec Management Platform 7.1 SP2, 7.1 SP2 MP1