I am using System Center Essentials 2010, and have a number of servers reporting 0-OK for hard disks. I have followed the blog published (http://blogs.technet.com/b/systemcenteressentials/archive/2010/03/29/troubleshooting-unknown-software-and-update-status-not-yet-contacted-and-lack-of-hardware-and-software-inventory.aspx) and this does not seem to be the answer. The registry keys are present and the Windows Update log is correct. I do not use imaging for deployment of servers so duplicate SUSClientID is not the issue. I have 27 servers reporting in SCE. 14 of them are responding with 0-OK and the other 13 are reporting correctly. The servers not reporting are a mixture of physical and virtual servers, server 2003 R2 as well as server 2008 R2 so there is no consistency as far as I can tell. The servers reporting 0-OK for hard disks are reporting back with the correct operation system, but are not reporting the hard disks, the memory, the IP Address, the model number, or the CPU specs. Any ideas on where to go from here? Thanks, Jesse

Hi Jesse, Based on my research, I would like to suggest the following: 1. Ensure WMI queries work on the problmeatic computers. You can try starting a query on the SCE server to the target server. 2. Check firewall settings referring to the following document: Firewall Exceptions for System Center Essentials 2010 http://technet.microsoft.com/en-us/library/bb437377.aspx If the issue persists, please check the Event Log on the problematic computers; if there are any related errors, please let us know the details. Hope this helps. Thanks. Nicholas Li - MSFT Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi Jesse, Based on my research, I would like to suggest the following: 1. Ensure WMI queries work on the problmeatic computers. You can try starting a query on the SCE server to the target server. 2. Check firewall settings referring to the following document: Firewall Exceptions for System Center Essentials 2010 http://technet.microsoft.com/en-us/library/bb437377.aspx If the issue persists, please check the Event Log on the problematic computers; if there are any related errors, please let us know the details. Hope this helps. Thanks. Nicholas Li - MSFT Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Internal firewalls are all shut off so firewall exceptions isn't an issue. By WMI queries do you mean collect inventory in the SCE console? Sorry I am still kinda new to this. Thanks, Jesse

Thanks Nicholas, I was able to run the WMI queries successfully both locally and from the SCE server. Never had any errors pop up. I tried a repair on the agent as well as uninstalling and re-installing the agent and still no luck. It is just very odd that SCE knows the operating system, whether the machine is virtual or physical, and what the model is if it is a physical machin, but just doesn't report the ip address or memory or hard disks, things like that. Any other ideas? On a side note, to make things a bit more of a mystery, I at times have received alerts for low disk space on servers that are reporting 0-OK for hard disks. So in some cases the servers really are reporting back, SCE just isn't displaying it. In other cases though, I've had servers reporting 0-OK for hard disks that have filled up and never generated an alert. Thanks, Jesse

Hi Jesse, Regarding the WMI queries, please try running a WMI query locally as well as remotely: For example, you can try the hardware related queries to check if it works: WMI Tasks: Computer Hardware http://msdn.microsoft.com/en-us/library/aa394587(v=VS.85).aspx To obtain data from remote computers via WMI query, please refer to: Connecting to WMI on a Remote Computer http://msdn.microsoft.com/en-us/library/aa389290(v=vs.85).aspx In addition, just for a test, in the console, please try uninstalling and reinstalling the agent on one of the problematic servers and see if it works. Hope this helps. Thanks. Nicholas Li - MSFT Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.