Symantec Management Platform (Notification Server)

 View Only
  • 1.  SMP 7.0 Agent slow to receive Configuration from Console

    Posted Mar 13, 2012 09:47 AM

    I've noticed that the Symantec agent is very slow receiving a configuration response from the console. When I look at some agents, it may go days without an update even though I have set the interval to 1 hour.

    What's Symantec service that responds to new configuration requests? Can I change the scheduled task?

    Incidentally, I've changed my inventory requests to 3 days to help out the server. We are also within our node count for the main NS.

    thanks



  • 2.  RE: SMP 7.0 Agent slow to receive Configuration from Console

    Posted Mar 13, 2012 10:34 AM

    Three days for inventory is much too frequent.  How many nodes are in your environment?

    I recommend weekly for your delta inventory (different days/times for hardware/software), monthly for full inventory (not to overlap with your delta schedules), daily for basic inventory, and 1 hour for an update interval until I hear how many nodes you have.

    Are there any errors in the Altiris Log Viewer on the NS?



  • 3.  RE: SMP 7.0 Agent slow to receive Configuration from Console

    Posted Mar 13, 2012 11:20 AM

    Is it possible you are talking about the "Changed" timestamp in the agent?

    If no policy is changed in the console, this time will never update, since it is the time of the last "change", not the last "got it".



  • 4.  RE: SMP 7.0 Agent slow to receive Configuration from Console

    Posted Mar 13, 2012 12:35 PM

    Thanks guys,

    Good info about the "Changed" timestamp. It bugs me because some of my agents are lagging behind a few days on my report  based off of MAX(vR.StartTime) as 'Last Configuration Requested'. My assumption was that the Configuration Requested was the agent saying hello and the Changed was the Console saying hi back. LOL. Makes since that the Changed will never update if the server isnt added to any new policy or filter. I thought that if the Last Configuration Requested went past a day (even though the interval is 1 hour), then the agent must be malfunctioning.

    That led me to the server being possibily busy and/or a service scheduled task running long.

     

    thx