Hello, From the LONG!!! thread http://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/70ea2c17-dae0-4733-acae-24b6bcde767e The management servers even with all Monitoring Unix/Linux machines in maintenance Mode is grayed out... after an hour... Any specific event in the logs which will tell me exactly when the MS went gray? Nothing in Apllication log? System Log? only in Operations Manager logs... So far I don't see the workflow id RHEL... anymore so the MM seesm working fine for this the warnings remainings seems to be more on the data Warehouse... all of these are on the Event ID 2115 as previously seen... try to redo again ... Apparently the workflow are too agreesive with the environment ... response timeout 60 seconds, 1 minute or 119 seocnds depending on the workflow does not seems to fit the environment!!! http://blogs.technet.com/b/kevinholman/archive/2008/04/21/event-id-2115-a-bind-data-source-in-management-group.aspx Warnings: Workflow Id : Microsoft.SystemCenter.CollectAlerts Workflow Id : Microsoft.SystemCenter.DataWarehouse.CollectEntityHealthStateChange Workflow Id : Microsoft.SystemCenter.DataWarehouse.CollectPerformanceData Workflow Id : Microsoft.SystemCenter.DataWarehouse.CollectEventData Workflow Id : Microsoft.SystemCenter.CollectDiscoveryData Workflow Id : Microsoft.SystemCenter.CollectSignatureData If I go to Monitoring > Operations Manager > Management Server Performance > Avg Batch Size I have several instances: - alertwritemodule: average:1.33 peaks: (2.75, 1.95, 2.45) only 3 - eventwritemodule: average 1 peaks (5, 19, 35!!!) only 3 - discoverywritemodule: average 6.5 peaks (37, 29.5, 22.25) only 3 - performancesignaturewritemodule: average 0 peaks (222, 232, 266.5) only 3 - statechangewritemodule: average: 1 peaks ...(7.80, 9, 8) 10-12 of them... - sqljobwritemodule: average 1 no peaks ... flat - performancewritemodule: average 6 peaks (395, 410, 390) only 3 Range 5/11 4 p.m. 5/12 3:30 p.m. the only one having data are on the RMS nothing from ant MS, is it normal? Any idea? Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hi, Please try clearing the HealthService queue on the MS: 1. Stop System Center Management service. 2. Go to C:\Program Files\System Center Operations Manager 2007\, and rename the “Health Service State” folder. 3. Restart System Center Management service. Regarding the Event ID 2115, please refer to: OpsMgr 2007: Performance and scaling issues with the converted Exchange 2007 management pack http://blogs.technet.com/b/operationsmgr/archive/2009/08/26/opsmgr-2007-performance-and-scaling-issues-with-the-converted-exchange-2007-management-pack.aspx Troubleshooting gray agent states in System Center Operations Manager 2007 and System Center Essentials http://support.microsoft.com/kb/2288515 OpsMgr 2007: Troubleshooting Console Performance in large environments http://blogs.technet.com/b/operationsmgr/archive/2009/09/17/opsmgr-2007-troubleshooting-console-performance-in-large-environments.aspx Performance IOPS for the DB and DW in OpsMgr 2007 http://blogs.technet.com/b/momteam/archive/2008/06/24/performance-iops-for-the-db-and-dw-in-opsmgr-2007.aspx In addition, please check the Event Log on both the MS and RMS and let us know the results. Thanks. Nicholas Li - MSFT 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.

Hello, 1. Stop System Center Management service. 2. Go to C:\Program Files\System Center Operations Manager 2007\, and rename the “Health Service State” folder. 3. Restart System Center Management service. Is it normal to have to do this on a weekly basis? Thanks, DomSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hi Dom, No, it is not normal. I've read the thread you mentioned in the first post and... I think it's time to make a call to MS Support Services... Have you tried?http://OpsMgr.ru/

Hi Dom, I also think that you are ready to make a CSS call. If a reset of the health service state doesn't work (and you should not have to do that too often) and you have tried all those other things already, you would do wise to go the step further and contact MS about it in a call, so they can run through everything with you.Bob Cornelissen - BICTT (My BICTT Blog)

Hi Dom, No, it is not normal. I've read the thread you mentioned in the first post and... I think it's time to make a call to MS Support Services... Have you tried? http://OpsMgr.ru/ Hi Alexey, yes and each time it works for 1-2 weeks then the RMS or the MS are down again.... Thanks, DomSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hi Bob, I placed the request for two new collectors for nworks to split the load. Role: nworks Management Pack Collector Hardware: - Network Speed: 1Gb/s - CPU: Dual 3.00 Ghz E450 - Memory; 4 Gb - OS: Windows Server 2008 R2 Enterprise - OS Architecture: 64-bits - Volumes: 50 Gb I placed the request for the Cross-Platform Role: Management Server Hardware: • 2 disk RAID 1 • 8 GB RAM • Dual Proc For now all Cross-Platform client are in maintenance Mode The PING MP is working only on 6 machines... but still issues.. I am waiting all Architecture in place beafore calling MS again as so far the issue is resolved only for 1-2 weeks maximum... Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hmm, that is very unfortunate. To me if it stays alright for several hours to several days and than turns grey again it sounds like a resource issue. If you fear that the nworks collector is causing it you could also go into the nworks console and remove checkboxes for esx hosts you dont want to monitor (I mean of course to temporarily lower the load!!). Later checking the checboxes will bring them back into monitoring of course.Bob Cornelissen - BICTT (My BICTT Blog)

Hi Bob, I have three Management Servers and one Root Management Server. MS1: 600 Servers MS2: 150 Devices most of them are printers DMS1: 6 15 Desktops The RMS remains healthy but the three MSs are grayed out ... If I reboot them they will come up healthy for an hour or two and then grayed out again. It looks like to me something else is impacting the whole environment. Could it the Datawarehouse? Several facts since all this is happening: - Movement of OperationsManager Database from the RMS itself to a Cluster. - Adding the Multi-Ping Managemnet Pack - Increasing the number of ESX Servers to be listened by nworks. I will remove some ESX servers as well. Still progressing.... I got my second nworks collector ... Thanks, DomSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hi, ... Regarding the Event ID 2115, please refer to: OpsMgr 2007: Performance and scaling issues with the converted Exchange 2007 management pack http://blogs.technet.com/b/operationsmgr/archive/2009/08/26/opsmgr-2007-performance-and-scaling-issues-with-the-converted-exchange-2007-management-pack.aspx ... In addition, please check the Event Log on both the MS and RMS and let us know the results. Thanks. Nicholas Li - MSFT 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. Hello, I have started the Echange tuning but it seems the overrides are old, I think I need to edit the xml file with XML Notepad to chnage the refernces to the current MPs Exchange 6.0.6702.0, System Library 6.1.7221.0 (instaed of 6.0.6270), IIS 6.0.6658 (Instead of 6.0.3539.0) etc... Thanks, DomSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hello, After migration of the DB one MS was still pointed to the old DB Host and causing issue,.... so now back to the regular tuning Thanks, DomSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager