Hi, I have a MP which inventorys and monitors some clients. In the MP, I define some classes and relationships. Class A hosts Class B, and B hosts C, C host D. And some discovery rules, if Instance of Class A is discovered, it will start script B to discover Class B, if B is discoved, it will start script C to discover Class C and so on. These rules will invoke for a given interval. It works well for almost all the clients for a long time. while recently, one of the clients has problem. It shows the instance of A and B, but instance C do not show. I debug the script and look for the log it shows the script C was run successfully with the given interval and it also return the Discovery Data without any error. While on the SCOM server side, the instance of Class C do not show. Other clients are still show good. Is any of you have ever saw this problem? Is it a known issue?

Hi, Have you tried to clear health service cache on this agent?http://OpsMgr.ru/

Alexey, Thanks your reply and sorry for my late response for my bad health. Could you please tell me why we need to clear the health service cache and how to clear for this special client? Or just restart the Opsmgrs Console with /clearcatche? Since one of our customer also have this problem, we need to tell them the reason.

Hi, I'd seen something like this before. When agent runs discovery for a second(third... etc) time it compares discovery results with previous results. And if nothing was changed discovery data will not be send to MS. In some cases instances is deleted from DB(for example, when MP was deleted and imported back) but discovery data isn't deleted from agent cache. You can stop System Center Management service on agent, delete all from <agent install folder>\Health Service State (do not delete this folder itself) and start service again. Wait for discovery interval if it uses SyncTime parameter and tell us if you see instances again.http://OpsMgr.ru/

Thanks you answer so quickly, I would try and tell you the result. By the way, I have another problem maybe the same issue. please help confirm. I have discover some devices(called Class A) based on MS Network Device in my MP. It works fine for a long time. After I upgrade my MP(delete the old version, after an hours later, import the new one), the Network device is there, but my Class A do not show and the class A discovery script was not running on the SCOM server. The data flow could not be started on the server.

Yes, it maybe the same issue. You can delete cache on RMS as well. Is your MP unsealed? Unsealed MPs can be tricky...http://OpsMgr.ru/

They all sealed. But if I delete the Network Device and rediscovery them again, everything will be OK. Could I say it's SCOM limitation?

The first question is gone due to some other errors. While for the Network device problem, it still there. I have discover some devices(called Class A) based on MS Network Device in my MP. It works fine for a long time. After I upgrade my MP(delete the old version, after an hours later, import the new one), the Network device is there, but my Class A do not show and the class A discovery script was not running on the SCOM server. The data flow could not be started on the server. If I remove the one of three Network Devices and rediscover it again, it will works fine, my class A will be discovered. While the other two still do not show. Is anyone know why?

if you deleted the MP and did not update(increment) the version # of the updated MP, this could cause this kind of symptom. Deleting an MP marks instances as to be deleted. You really need to wait three days to have an MP really clean out if you are going to change the MP. Better to just increment the version # and re-import without deleting.Microsoft Corporation

We indeed update the new MP version. My discovery is target on Network Device, the DataSource is based on SNMP. The Network Device is there, but my discovery dataflow do not start. How could I debug/manual trigger the discovery dataflow? Keep in mind that if I remove the one of the Network devices and rediscover it again, it will work fine. But others do not were remove/rediscover will still do not work.

Get the root cause. It's due to the different Community string. Sorry for confused.