You say these servers are also in a build phase (at some point). Are these by any chance servers that have been agents before? (for instance a re-install of operating system on a machine and using the same name and computer account to install the new one). In that case you might have to wait until they have a scom agent and have replaced the old entry (if you forgot to clean those out first) and then put the servers into maintenance mode. See if that helps. Just in case you are re-deploying previously existing agents of course (I have seen the issues before when this was the case). Sometimes something goes wrong and you can use the remove from MM and re-enter into MM method Dan describes.Bob Cornelissen - BICTT (My BICTT Blog) - Microsoft Community Contributor 2011 Recipient

Hi, I'm getting alerts (Failed to Connect to Computer) from servers which are in Maintenance Mode. Is this the expected behaviour ? As these servers are still in build, application install, etc, they have been put in Maintenance mode and are brought down repeatedly so we get Failed to Connect to Computer alerts and hence email notifications get triggered, upsetting the server admins.Thanks, Harry :-)

Sounds like some of them may have been missed for MM. Try taking them out of MM and putting them back in. If there are MP's that are doing ping - such as the ping management pack, and if these packs are not designed to respect server MM (very common with custom MPs) then you may have to root out the rule that is causing the issue and put the monitor in MM.Microsoft Corporation

Are you sure you've set maintenance on the computer object? Sounds to me the "agent" isn't in maintenance, just a part of the workflows running on the agent (failed to connect is health watcher so check the "operations manager > agent > agent state view)Rob Korving http://jama00.wordpress.com/

Please also check the folloiwng thread: ScheduleMaintenanceMode won't stop alerts with SCOM R2 http://social.technet.microsoft.com/Forums/en-US/operationsmanagerextensibility/thread/c6201685-4053-43e8-9e74-f6b1f5351865/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.

Bingo Rob !!! I found my server in Operations Manager -> Agent -> Agent Health State as Healthy instead of Not Monitored(with the MM icon), I selected and put it in MM. Looks good, I'll observe it for few more days and will update if I still see Failed to Connect to Computer alerts. I used to put servers in MM by selecting under Discoevered Inventory. Seems this was not the best way.Thanks, Harry :-)

@Dan, No Ping MP, only Windows OS MP's are imported.Thanks, Harry :-)

@Vivian, We are not using any scripts as mentioned in the link. We use SCOM console to start & end maintenance mode.Thanks, Harry :-)