Kevin, Sorry to hijack this thread, and I’m not trying to sound combative or critical, but it seems to come out that way no matter how I say it, so, just here.
How are SCCM admins and SCOM admins supposed to handle SCCM maintenance windows? Our DNS servers and DC’s trigger hundreds of emails each from the DNS management pack when they patch, about DNS zones not running and nslookup failing to find the name server for each zone. Last night one DC and one NS patched and rebooted and patching these two servers generated 1342 emails. 671 New, and 671 Closed. I don’t particularly want to override these alerts because I want to get them any other time besides the servers’ maintenance window in SCCM. What are the best practices here? How can SCCM tell SCOM, “hey, the server isn’t dead, nothing’s amiss, it’s just rebooted for patching”? are there best practices around setting maintenance mode in SCOM? I’ve seen a tool that purports to do this, but it cratered our 2007 SCOM when too many windows were configured in it. do we really have to do it one at a time manually? What’s the going message from you guys these days about this? Todd From: [email protected] [mailto:[email protected]] On Behalf Of Kevin Holman Sent: Monday, September 15, 2014 7:23 PM To: [email protected] Subject: RE: [msmom] URL monitoring Alert SCCM is setting to enable maintenance mode for that agent. This doesn’t work and never has since MOM 2005. Pausing the healthservice is bad, it is not actual maintenance mode, and this causes all workflows to fail. The SCCM team should stop enabling SCOM maintenance mode or alert suppression on their advertisements, and software updates. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Philip George Sent: Monday, September 15, 2014 4:28 PM To: [email protected]<mailto:[email protected]> Subject: [msmom] URL monitoring Alert Hi All, We have URL monitoring setup which monitor a bunch or web URL from a gateway server. For the past few days we are getting alerts "One or more Web Applications Unavailable" for all the URL from that server. I checked the SCOM server the time we got the alert i could see the below message in the event viewer. The health service {B8D8F4B1-817D-98FF-A615-6E99C66EA369} running on host MOMGW1 and serving management group SCOM2012 with id {3D041EB1-17CA-1233-9193-5C6E645B8FC2} is not available because service has been paused. to check why its doing this i checked the GW server event viewer I could see The Microsoft Monitoring Agent running on computer " MOMGW1 " is suspended for the following reason: "ConfigMgr 5.00.7958.1000 - SMS_MaintenanceTaskRequests - {DCF45B33-86CE-4131-A3C8-CF2FCB61B4A2}" and from the MaintenanceCoordinator.log I could see the below message. Failed to get task state for '{DCF45B33-86CE-4131-A3C8-CF2FCB61B4A2}'. Error 0x87d00317 MaintenanceCoordinator 9/15/2014 9:03:35 PM 5888 (0x1700) Adding task for client "updatesmgr": id - "{DCF45B33-86CE-4131-A3C8-CF2FCB61B4A2}", pri - 20, service window - 0, max time for sw - 600. MaintenanceCoordinator 9/15/2014 9:03:35 PM 5888 (0x1700) Start scheduling tasks. Total 1 tasks in the queue. MaintenanceCoordinator 9/15/2014 9:03:35 PM 5888 (0x1700) Task '{DCF45B33-86CE-4131-A3C8-CF2FCB61B4A2}' (agent 'updatesmgr') pass service window check. MaintenanceCoordinator 9/15/2014 9:03:35 PM 5888 (0x1700) Signaled task '{DCF45B33-86CE-4131-A3C8-CF2FCB61B4A2}' (agent 'updatesmgr'). MaintenanceCoordinator 9/15/2014 9:03:35 PM 5888 (0x1700) Done scheduling task. Winning task '{DCF45B33-86CE-4131-A3C8-CF2FCB61B4A2}' (agent 'updatesmgr') MaintenanceCoordinator 9/15/2014 9:03:35 PM 5888 (0x1700) Task "{DCF45B33-86CE-4131-A3C8-CF2FCB61B4A2}" (agent 'updatesmgr') is reporting back on starting. MaintenanceCoordinator 9/15/2014 9:03:35 PM 3348 (0x0D14) Stopping timer 13013 MaintenanceCoordinator 9/15/2014 9:03:35 PM 3348 (0x0D14) EnterMomMaintenanceMode - beginning; parameters reason = 'ConfigMgr 5.00.7958.1000 - SMS_MaintenanceTaskRequests - {DCF45B33-86CE-4131-A3C8-CF2FCB61B4A2}', timeout = 660 MaintenanceCoordinator 9/15/2014 9:03:35 PM 3348 (0x0D14) Attempting to call SCOM Maintenance Mode interface. MaintenanceCoordinator 9/15/2014 9:03:35 PM 3348 (0x0D14) EnterMomMaintenanceMode - ended; parameters reason = 'ConfigMgr 5.00.7958.1000 - SMS_MaintenanceTaskRequests - {DCF45B33-86CE-4131-A3C8-CF2FCB61B4A2}', timeout = 660 MaintenanceCoordinator 9/15/2014 9:03:36 PM 3348 (0x0D14) Disabled Mom alerts for task '{DCF45B33-86CE-4131-A3C8-CF2FCB61B4A2}' (agent 'updatesmgr') MaintenanceCoordinator 9/15/2014 9:03:36 PM 3348 (0x0D14) Timer 13016 setup for execution. MaintenanceCoordinator 9/15/2014 9:03:36 PM 3348 (0x0D14) Successfully started task '{DCF45B33-86CE-4131-A3C8-CF2FCB61B4A2}' (agent 'updatesmgr'). MaintenanceCoordinator 9/15/2014 9:03:36 PM 3348 (0x0D14) Removing task '{DCF45B33-86CE-4131-A3C8-CF2FCB61B4A2}' (agent 'updatesmgr') from the queue. MaintenanceCoordinator 9/15/2014 9:06:02 PM 5732 (0x1664) Stopping timer 13016 MaintenanceCoordinator 9/15/2014 9:06:02 PM 5732 (0x1664) ExitMomMaintenanceMode - beginning MaintenanceCoordinator 9/15/2014 9:06:02 PM 5732 (0x1664) Attempting to call SCOM Maintenance Mode interface. MaintenanceCoordinator 9/15/2014 9:06:02 PM 5732 (0x1664) ExitMomMaintenanceMode - ended MaintenanceCoordinator 9/15/2014 9:06:02 PM 5732 (0x1664) Removed task {DCF45B33-86CE-4131-A3C8-CF2FCB61B4A2} for client updatesmgr MaintenanceCoordinator 9/15/2014 9:06:02 PM 5732 (0x1664) Anyhow the question is :- What make the URL monitoring fail during this time? SCCM agent putting the SCOM should not make URL monitor fail. Any pointers? Philip
