What bug fixes and features are addressed in the upcoming Inventory Solution 6.1 SP3 Release?
|Article:HOWTO9984|||||Created: 2009-04-03|||||Updated: 2009-06-02|||||Article URL http://www.symantec.com/docs/HOWTO9984|
What bug fixes and features are address in Inventory Solution 6.1 SP3?
SP3 has been released (5/29/2009).
The following issues or features are addressed in Inventory Solution 6.1 SP3 (Note, this list may contain items that were subsequently determined as not applicable for this release, and some fixes in SP3 may not be represented here):
39284 - Incomplete Add or Remove Programs data on x64 systems
23612 - Vista and x64 Support for Inventory Solution
25420 - Custom Inventory query WMI on x64 system does not return any results
27148 - AeX OS Add Remove Programs sending incomplete data on x64 systems
43427 - KNOWN ISSUE: On Windows Vista SP1 the Serial Number and other hardware level values are not captured
43424 - KNOWN ISSUE: Retired computers do not update Inventory if the system sends in new Inventory
36631 - KNOWN ISSUE: Error "AeXCustInv encountered a problem and needed to close" on Windows 2003 Servers
NOTE: This issue will not be addressed: 34797 - KNOWN ISSUE: When installing or upgrading to the Inventory 6.1 SP2 Report Pack, the Reports are missing
34220 - KNOWN ISSUE: New install causes both Re-create Inventories to fail to insert into the database
40713 - KNOWN ISSUE: AexAuditPls is crashing and popping up a debug error
30536 - Why is custom inventory reporting a buffer overrun?
33348 - KNOWN ISSUE: Custom Inventory causes a Data Protection error
43960 - KNOWN ISSUE: Inventory for Windows is not returning a build number
43226 - KNOWN ISSUE: AeXSNPlus.exe - SNPlus in Inventory 6.1 is not reporting inventory due to a hang/crash condition
43970 - KNOWN ISSUE: AeXMachInv.exe still causing WMI race conditions even with the /wmisync switch (Inv 6.1 SP2)
43426 - KNOWN ISSUE: Windows NT Virtual Machines'' Inventory results in an error and data is not posted to the database
41330 - Common data gets orphaned when all associated split rows are removed
Article URL http://www.symantec.com/docs/HOWTO9984