We aleady have 1 RMS and MS working fine, I installed a new MS (2007 R2) , It installed fine , Showed up in the console ,however i noticed a strange behaviour : Thousands of Events on the new MS Log Name: Operations Manager Source: OpsMgr Connector Date: 2/21/2011 1:54:28 PM Event ID: 20022 Task Category: None Level: Error Keywords: Classic User: N/A Computer: New_MS.domain.com Description: The health service {XXXXXX} running on host machine.domain.com and serving management group SCOMG1 with id {XXXX} is not heartbeating. This Event came for almost all my agents that are currently being monitored by the other MS that we have. I know all the agents were heartbeating fine. Q: So, Why did i get this event on the new Ms ? As i know it is fake 2nd Event i received on the New MS (Event Viewer) Log Name: Operations Manager Source: HealthService Date: 2/21/2011 1:48:48 PM Event ID: 1102 Task Category: Health Service Level: Error Keywords: Classic User: N/A Computer: New_MS.domain.com Rule/Monitor "Microsoft.SystemCenter.DiscoverHealthServiceProperties" running for instance "New_MS.domain.com" with id:"{XXXXXXXX}" cannot be initialized and will not be loaded. Management group "SCOMG1" Got thousands of these on the New MS; >Two alerts showed up in the SCOM console as well: (Looked Fake) The Health service $Data/Context/DataItem/HealthServiceId$ running on host $Data/Context/DataItem/HostName$ and serving management group with id $Data/Context/DataItem/ManagementGroupId$ is not healthy. Some system rules failed to load. (Why) The health service XXXXX running on host New_MS.domain.com and serving management group with id {XXXX} is not healthy. Action account is invalid. ( I know it is valid) >how to know if an alert is fake , any brute force method , like something that may help to stop fake alerts to the maximum.

Hello, For your information, here is a thread disscussed a similar heartbeating issue: Strange behaviour between Agent & RMS communications http://social.technet.microsoft.com/Forums/en/operationsmanagergeneral/thread/7114c967-0efe-42c6-91e9-861c196ac760 Hope it helps,Yog Li -- 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.

i don't think the alerts are fakes, but they could be temporary (i never seen a fake alert, the alert always comes because it matches some criteria, however that criteria might be incorrect or might occur on initialization for a brief moment as well :)). The new ms is just discovered fine (not in a grey status or some role hasn't been discovered?) it has downloaded its config ok? When you restart the healthservice of the new ms it shows no errors in the opsmgr log? Rob Korving http://jama00.wordpress.com/