You may not have upgraded properly.  I don't have immediate access to an environment that is on SP1 vs SP2 to verify.  Nonetheless, ensure you upgraded to SP2 using 'Install new products' and not 'View/install updates':

http://www.symantec.com/docs/TECH177513

Does this provide proper agent versions?

Edit: Ignore this.  I can't read.

When did yours change from 8280 to 8292?

You have the V2 rollup installed for SP2.

SP0 = 7.1.13797.6797*

SP1 = 7.1.13851.6851
SP1V1 = 7.1.13851.6865
SP2 = 7.1.15280.8280
SP2V2 = 7.1.15292.8292

*Added the core non-service pack version of the agent from a fresh 7.1 install.

**The SP2 or SP2V2 version actually resolves an issue with high CPU utilization when trying to process a 0 byte .NSE file in the local event queue for the agent. On a typical physical workstation CPU usage for the aexnsagent.exe process will hold at 30% when this occurs. On a single core VM it will hold at >90%. With the new agent it will ignore/delete the 0 byte .NSE file correctly thereby eliminating any high CPU usage.

You can watch this occur by creating a simple empty TESTME.TXT file, rename it to TESTME.NSE and watch the agent attempt to process the file through the queue. If you add ANY kind of text to it, it will process the file and reject it as an invalid/improper format .NSE.

I do not know of any other changes that affect the agent directly.

Thank you for your updates.

The sp1 version has been installed on 26/01 and the "SP2V2 rollout" appeared on 7/02.

Do you know the issues that have been fixed by this rollup?

When Altiris is upgraded at various versions, service packs, etc, does the CMDB table "DBSchema" usually always reflect the same versions listed above in its "Version" column?

thanks,
Scott

Looking at the agents/plug-ins versions on my clients they range from 7.1.7580, 7.1.15280, 7.1.1301, 7.1.2316, 7.1.15280.8280. Does anyone know of a list of what you should have after the Sp2 upgrade?

thanks

I got the rollup from support and they gave me permission to post the change log.  You'll still have to open a ticket with support to get the actual binaries (sorry about the formatting) :

2620808 - We need to evaluate the time that takes to load the Right-Click menu for Computers resources
2634514 - slow performance when clicking update membership with a large membership - spGetComputerResources
2627875 - Getting deadlocks in sp_Inv_AeX_SWD_Status_Summary_clean
2627692 - Scheduling options for roles and accounts, allowing to scope subset to be replicated by specific rule
   For how to create new rule see CreateRule/ReadMe.txt
2627677 - Performance optimizations on replication of roles and accounts required
2424439 - Replication in hierarchy doesn't propagate resource deletion from parent to child
2527236 - 'Role' resources are constantly replicated during differential replication
2611595 - Slow performance when updating policy with a large target

2625970 - RCa - Hierarchy - Client Task will be replicated each differential replication even if it wasn't changed in case it was executed on child's computers.
2637403 - Task run instances scheduled at the parent can not be "stopped". The message indicates it will, but it does not.
2575924 - Task run-instances are replicated erroneously to all child nodes in a hiearchy instead of only the one(s) to which it belongs.
2124511 - Schedules added to client tasks after first replication are not replicated unless the client task itself changes
1647634 - TS 7.0 Replicating a scheduled task using a Target causes blank computers to appear in list.
2143240 - Task Server: Tasks set to run to a schedule and assigned to agents at both levels of a hierarchy will eventually be marked as ‘Failed’ on the Parent NS.
2655827 - Importing security groups from AD does not contain all the members.
2658306 - Resource updates are taking large amount of time and memory resources due to multiple MonitorChangesAsync threads when there should only be one
2652467 -Unable to delete Computer resource. Error: Violation of PRIMARY KEY constraint 'PK_ResourceTargetContainerChanges'. Defect in trigger trgScopeUpdateTargetInvalidate
2631036 - IRM is not importing the syncronization policy during the upgrade.
2636128 - Task within a MSD set to run only at maintenance window, executes immediately if override is set and if the Task is first in the list
2627388 - Replication in hierarchy doesn't propagate resource deletion from parent to child
2627390 - 'Role' resources are constantly replicated during differential replication
2641966 - Cloning of default OV throws an error when logged in as Symantec Level2 Worker
2653019 - Condition cannot be added in Normal mode under Filter expressions in Query builder
2643544 - Unable to import computers from all security groups in Active Directory or from within a specific organizational unit
2620222 - SoftwareCache.xml is overwritten during execution of dozen detection checks from MD policies which are scheduled in one time
2629544 - Client task agent started running old tasks multiple times daily. Tasks had been configured to run just once and had already ran previously weeks before.
2636958 - Image creation failed if teaming is created using two physical NIC

Thanks BP, Looks diferent than mine, so I need to do some checking...

Thanks for all. A new rollup will be created every month to fix the problems encountered and will be available from the support or the integrators partners of Symantec

For example, as I have opened a ticket for the thousands same errors found on the NS log viewer : "BaseXmlHttpCallback Exception: System.Exception: An exception occurred while executing the request ---> System.Exception: System.Xml.XmlException: Unable to find node named "statusEvt".  Found node "" instead"

the correspondant fix will be included in the 7.1 SP2 rollup V4  (tentatively in April).

New agent version:

SP2V3 = 7.1.15310.8310

V3 specific fixes:

Are these rollups avalible from the SIM, or do we have to contact support to get them?

A new rollup v4 is available

http://www.symantec.com/connect/forums/smp-71-sp2-...