Through our OpsMgr R2 Console, we have an SCCM server that we are seeing a "grey" agent on. Looking closer at the "Agent State from Health Service Watcher" view, the Health Service Heartbeat failure monitor is showing in the State Change Events tab: Health Service is not available although following server is reachable: xxx.xxxx.com. Reasons: 17 Health Service has been paused. Further research, it appears the SCCM product puts a 1217 event ID in the Operations Manager event log stating "The System Center Operations Manager agent running on computer "XXX.XXXX.com" is suspended for the following reason: "ConfigMgr 4.00.7071.0000 - Starting - Backup". I've seen this happen other nights, but last night it appears the agent paused, became healthy, then paused again and seems to be stuck. I've tried restarting the OpsMgr agent, stopping the agent and renaming the Health Service State folder, and putting the computer into maintenance mode. How do I get it out of this "paused" state and allow the agent to become healthy/monitored again? Thank you, Kate

Hi Kate, According to my search, it is due to SCCM's backup operation. OpsMgr agent would be paused during SCCM's backup operations and the alert will be generated. The following thread discussed this issue: http://social.technet.microsoft.com/Forums/en/configmgrbackup/thread/d6229a52-d65f-4ccd-bb69-fe5df9eaaf6f Hope it helps. 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.

Kate Have you run through the SCOM MP guide. It has a number of recoveries and agent configs that have to be be completed out side of the standard install. They greatly assist with agent health. Now I understand that something is pausing your agent and I didnt know in fact that SCCM did this, but I do have agents on a number of SCCM servers and I dont see what you are seeing. http://technet.microsoft.com/en-us/library/dd350065.aspxPaul Keely

Vivian... Thank you for the reference. I checked this morning and the node is now healthy. On the night of 11/24, at 10:02 PM after the SCCM backup completed on that server, the agent went to a healthy status. The job that paused it in the first place the night of 11/23 corrected it the following evening. I would still be curious to know if there is another way to get the agent to come out of a paused state. Kate

Hi, It seems is a by designed feature in SCCM that paused OpsMgr agent when backup. Given this situation, configuring from SCOM side may be limited. You can also SCCM forum to check if there is any configuration available: http://social.technet.microsoft.com/Forums/en/category/configurationmanagerPlease 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.