Hi I accidently changed the system clock to the wrong year. Now in SCOM I have some system states errors that are registered in the wrong year and are flagged. The current state is okay.. It is also creating alot of event id's 5500. How can I cleanup this goof?

ahead 1 year or back 1 year? The first you can't, at least not supported. The 2nd will automatically be pruned out, allthough you could speed that up by altering those settings temporary.Rob Korving http://jama00.wordpress.com/

That's do bad that you can't fix the error with a health reset. If I come find a way.. I'll keep you posted!

If it is very recent (like a day ago) you could revert to a SQL backup of the operationsmanager database perhaps. Health resets will clean up some of the mess, but like Rob said, if you have moved it forward and events happen later it could look messy. Alerts from rules and stuff can simply be kicked out and re-created if they re-occur or you can restart those agents.Bob Cornelissen - BICTT (My Blog about SCOM) - MVP 2012 and Microsoft Community Contributor 2011 Recipient

Yeah it's been a few months.. Just noticed it yesterday. It just weird to see something that is healthy after resetting the health then go back to an error state after a little bit of time. Turnsout to be a false state.

Hi, I also noticed the following thread which is about a similar issue. Please see if it is helpful: Reset /Delete the History of a Monitor? http://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/5ebf5509-7080-4332-a7fe-da8078bef02a Thanks. Nicholas Li TechNet Community Support

Yes, so an option would be to delete the agent and leave it that was for several days and wait until its data gets groomed out of the database. And later add that agent again.Bob Cornelissen - BICTT (My Blog about SCOM) - MVP 2012 and Microsoft Community Contributor 2011 Recipient

It's my management server... I can't remove it.

Youre right, that would complicate things.Bob Cornelissen - BICTT (My Blog about SCOM) - MVP 2012 and Microsoft Community Contributor 2011 Recipient

This may seem like a long shot.. What about putting the entire scom enviorment in maintance mode. Then running the script that was mentioned http://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/5ebf5509-7080-4332-a7fe-da8078bef02a in this forum. Then putting the clocks back. Then remove the maintance mode?

Hi, sorry this thread seems to have been left behind. Did you get out of the situation blossom? Let us know what happened. Thanks.Bob Cornelissen - BICTT (My Blog about SCOM) - MVP 2012 and Microsoft Community Contributor 2011 Recipient