Fix database after time shift

Fix database after time shift

In our testing environment, we have shifted the time for the domain backward for some simulation testing. Unfortunately, OpManager has become confused and has stopped monitoring our servers. I tried to rediscover and test each monitor, and that worked for a little while yesterday - but today it's back to not monitoring.

For example, today is May 16 2012. The last time OpManager thinks it monitored the servers was in August 2012. So, it's waiting until then (I think) before it monitors again. I would like to know if there's a way to clean out the data in the database so that it will start monitoring again.

Thanks.






                  New to ADSelfService Plus?