Client Management Suite

Hi,

So I have two things coming into play here. I have computers that don't have any hardware inventory data and are "broken". I should stress that basic inventory and a regular software inventory policy is working and the purge policy has not retired them. Those will hopefully get fixed by uninstalling/reinstalling the Altiris Agent. I also have formerly umanaged computers who are just getting the Altiris Agent for the first time. When I check my reports I see all of the computers that don't have hardware inventory data. Over time the ones coming online will get updated either through an inventory policy or an inventory task job. Unfortunately that cannot happen fast enough and when I look at the report it is hard to separate the broken ones from the ones that just have not had a chance to run a hardware inventory policy or task. I was talking with one of the L3 engineers as I have a case open for the ones that will require a uninstall/reinstall of the Altiris Agent. He thought I might be able to adjust one of my queries to check the Computer System data class. I believe he was suggesting (could be wrong) that a new installation would have the Computer System data class, but a broken installation would not. Does that make sense or do I have it backwards? I will post my query in a little bit. I just don't have access to it off the computer I am typing this message on. If someone the modified query can differentiate the broken ones from the ones that just have not updated would be great.

Hope someone can help.

Hi,

Here is the query I would be looking to tweak if possible. Now that I think about it using Computer System is probably not the way to go.

SELECT     vComputer.Name AS 'Computer Name', vComputer.[IP Address], vComputer.[OS Name], vComputer.[OS Revision], vComputer.[System Type], vHWComputerSystem.Manufacturer,
                      vHWComputerSystem.Model, vHWComputerSystem.[Identifying Number] AS 'Serial Number', vHWProcessor.Model AS 'Processor',
                      vHWComputerSystem.[Total Physical Memory (Bytes)] / 1048576 AS 'RAM (MB)', vComputer.[User] AS 'Primary Owner'
FROM         vComputer LEFT OUTER JOIN
                      ResourceAssociation AS loc ON (loc.ChildResourceGuid = vComputer.Guid OR
                      loc.ParentResourceGuid = vComputer.Guid) AND loc.ResourceAssociationTypeGuid = '05DE450F-39EA-4AAE-8C5F-77817889C27C' LEFT OUTER JOIN
                      vItem AS I ON loc.ChildResourceGuid = I.Guid LEFT OUTER JOIN
                      vHWProcessor ON vComputer.Guid = vHWProcessor._ResourceGuid LEFT OUTER JOIN
                      vHWComputerSystem ON vComputer.Guid = vHWComputerSystem._ResourceGuid
WHERE     (vComputer.IsManaged = 1) AND (vComputer.[OS Name] NOT LIKE '%Server%') AND (vHWComputerSystem.Model is Null)
ORDER BY 'Computer Name'

Can you check to make sure that WMI is functioning properly on the computers with missing HW data?

Already done by my colleague who does the scripting. WMI is not broken. The Altiris Agent is on some computers.

Check this thread out:

https://www-secure.symantec.com/connect/forums/machines-missing-hardware-inventory

Does this sound like it applies to you?

I have done this with the L3 engineer from Symantec and that has helped fix alot of the computers so we get there hardware inventory. The issue I am having now is we also discovered there is a bunch of unmanaged computers. As we deployed to them the report I have is showing both the newly unmanaged computers + broken computers. So the question then becomes is what would differentiate a newly managed computer from one that is broken? If that can be done I can focus on the ones that are truly broken. Surely something must differentiate the two that can be tweaked so I get better results from my report. Some type of data class.

Hardware Inventory is not reporting all, indeed most, of the dataclasses.

A point fix for 7.1 SP2 MP1 v4 was created in ETrack 3154889. Please contact Support for this point fix. The fix will be included in the 7.1 SP2 MP2 v6 roll-up.

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