Groupe des Utilisateurs Altiris Suisses et Francophones Group

 View Only
  • 1.  Task cycling, repeat, duplicate on restart, crash software policy

    Posted Jun 13, 2012 07:27 AM

    I do not have all detail yet. But we see an NS agent trouble we were needing to "Aexnsutil.exe /clean" and reinstall to solve (workaround).

    • multiple tasks running in process
    • repeat and more process in list, after restarting the PC, not solving the problem... Worst in fact.
    • Software policy "freezed"...

    so for a sotware deploy on 150 clients, we got 70 success, 80 failures.

    • XP win32 machines.
    • Latest SP2 7.1 Altiris installed.
    • Most were auto-upgraded from a previous 7.0 install agent...

    I suspect a problem with agent upgraded from 7.0 to 7.1 not stable. Any known similar issue your side ?

    current version agent probably: 7.1.7580 plugins (+7.1.8280 agent)

     



  • 2.  RE: Task cycling, repeat, duplicate on restart, crash software policy

    Posted Jun 13, 2012 03:04 PM

    c’est étrange… Vu l’explication que tu donnes dans l’article, je pencherai pour une éventuelle corruption du cache de policy. Il faudrait peut-être essayer de le vider manuellement dans un premier temps, pour voir si c’est bien ça, puis de le scripter (3 ligne de code J). Le cache se trouve ici par défaut « C:\Program Files\Altiris\Altiris Agent\Agents\SoftwareManagement\Software Delivery » et tu peux le cleaner complètement si tu arrêtes le services « Symantec Management Agent » avant.

    Merci Gilles.



  • 3.  RE: Task cycling, repeat, duplicate on restart, crash software policy

    Posted Jun 20, 2012 03:34 PM

    A little late, but check for corrupt policies.  The agent logs should say that the Symantec Management Agent will no longer start because it's failed three times in a row.  If so, back up and delete the local client policy .xml's and attempt to restart the agent.  If it starts, the policy was corrupt.  Review the backed up client policy and compare it to the new, good policy it just received to see what is different and which policy may have caused the problem.

    If the new policy also causes the computer to crash, the problem is still current and you'll want to compare broken client policies to working client policies, assuming at least some clients are functional.