Video Screencast Help

Missing CMDB Data classes

Created: 16 Mar 2011 • Updated: 29 Mar 2011 | 3 comments
This issue has been solved. See solution.


I am experiencing an issue where only 4 machines within my environment are reporting back Manufacturer and Model number. The rest of the 3700 machines are not showing this information. The 4 that are showing it are some of the first machines that I converted to Symantec Agent 7. I do not believe that any changes were made to the installation files.

I am wondering how I can get the rest of the machines to report this information to the CMDB. I wasn't sure if there is an inventory ini file that needs to be modified or a setting within SMP. I have attached 2 screen shots so you can see exactly what I am seeing.

Thanks for any tips you can provide!



Comments 3 CommentsJump to latest comment

mclemson's picture

The dataclasses here are populated by hardware inventories:

Serial Number, Manufacturer, and Model are both part of the hardware inventory.  Are you running a full inventory on these systems?  Remember that a full inventory should be run monthly, but you can send it as a one-time task as you troubleshoot to determine if this resolves the issue.  It's possible that it synchronizes to the CMDB dataclasses on a schedule, so if that's the case, you should be able to immediately see this data in the Logical Device data class (Manufacturer and Model) and the Computer System data class (Serial Number).

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner

Nickles's picture

Thanks for the response. We have been running full inventory actually weekly while we implement the system. The link you provided led me to run the 'Inventory to Asset Synchronization' and it populated the information for most of the systems in our environment.

It does seem that we have machines not picking up the weekly full inventory task. When checking the Collect Full Inventory policy, I have 68% Compliant 28% Critical and 4% failed. Have you seen this before where all the machines are not running the policy correctly?

mclemson's picture

Best guess explanation for the 28% is that they have not been on or are not responding to the NS.  Try creating a task to run inventory and using one of these 28% as a test machine.

Best guess for the 4% is that no inventory plug-in is installed.  Be sure your target only includes those with the inventory plug-in.

Without knowing more that's where I'd start.  If you have a client who misbehaves, agent logs would be beneficial.  You can view them yourself by typing running regsvr32 to register the AexAgentDiagnostics.dll.

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner