Hi, I realise that it's too late now but This is not something that I would do with a production OpsMgr management group. I would use a separate implementation for this sort of thing. I think you will need to call PSS as it sounds like database changes are required to solve this. I take it you have tried the 'reset health' option in health explorer? EDIT - have you tried removing the agent from the management group, waiting a couple of days, then re-adding? Matt Matt White ( http://systemcenterblog.hardac.co.uk/ )

thats what i did: - removed the agent from the Management Group and re-add it (after 10min) - reset the Monitor - deleted the HealthServiceStore - restart the agent I can try to remove the agent again and wait a few hours, or is there a better way to delete all the data from a server(performance and other stuff too)?

I think there is a grooming event that happens overnight - hence the reason for removing the agent for a couple of days. In the database there is a table called StateChangeEvent, in there you should see your rogue entries. However, it is not supported to make direct changes to the SQL database. You have to also consider whether the data will be in your data warehouse. Hence the suggestion of a PSS call. MattMatt White ( http://systemcenterblog.hardac.co.uk/ )

Hi In our environment we have to test the behavior of some servers in the future 31.12 to 1.1.2011 All the Server are in separate Domain with a separate TimeServer. I made a gatewayserver to monitor these servers. After the testing, we changed the servers back in the normal domain. Now some of the monitors will not reflect the actual state. It looks like: 19.02.2011 12:13 Service is not running 16.02.2011 09:06 Service is running 14.12.2010 10:26 Service is running I guess , now Opsmgr have troubles with the future and present date, how can i delete the history of the monitoring? Thanks

Hi, To get some related records, you may try SQL queries. Please refer to the following post and see if it will give you some hints: Useful Operations Manager 2007 SQL queries http://blogs.technet.com/b/kevinholman/archive/2007/10/18/useful-operations-manager-2007-sql-queries.aspx 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.

I have a script posted which is a simple modification to the built in grooming script - which will groom out ALL the data in your statechanges... by default we wont groom out any monitor where we currently think you are in anything but healthy state. However - since your statechangeevent occurs in the future - even my simple script wont groom it. I am afriad the only solution I know would be to edit/delete those records in the database, which isnt supported. You really should not change times on servers - having proper and robust time synch is very important to the health of a domain, and will potentially affect applications which are dependent on time. I'd probably recommend opening a case with PSS in this situation.... or wait until the time passes. :-) You can also delete the objects (server agents) from the console, and make sure the agent is not running (no pending actions). Then wait 2-3 days so that we will groom out the deleted items from the database. When you delete an agent - we dont delete the data about that agent, we simply mark the managed entities "is deleted" value to true... so they dont show up. This is by design to allow for people to troubleshoot issues, removing and reinstalling agents, without forcing a bulk removal of database discovery data. It takes 2-3 days to groom these old managed entities out.Kevin Holman http://blogs.technet.com/b/kevinholman