Hi.
I'm looking for a way to reset the frequency / test Time Interval, for all my tests.
I have had som problems with my HM, which are solved now.
Looking in the Audit, it says that the frequency is much smaller than the test originally was set up to.
Any ideas?
Resetteing all test to its originally value
How exactly have you changed test interval?
- using "Change test interval" action?
In this case you may use the same action with "restore original value" option
- using import file or manually editing test properties?
In this case do the same opearation again - manually change test interval back to previous value
Regards
Alex
- using "Change test interval" action?
In this case you may use the same action with "restore original value" option
- using import file or manually editing test properties?
In this case do the same opearation again - manually change test interval back to previous value
Regards
Alex
Hi Alex.
I was experimenting with RMA on a 64bit w2k8.
It was very unstabel, so I found that RMA on a 32bit w2k8 seems to bee stabile.
All the test done with the 64 w2k8, which has been fired, while the agent was unreacheble, got into bad standing.
In my action profile, I has a 33% decrease of the scheduled test intervall, which is working -
so the test intervall became very small.
Getting things done and up running on 32bit w2k8, didn't reset the scheduled time as expected.
I have been through some 200 test now, changing the time forth and back saving in between.
So now I'll post a sugestion in the other forum, which can help people to control if the schedules is not brought back to it originally value.
I was experimenting with RMA on a 64bit w2k8.
It was very unstabel, so I found that RMA on a 32bit w2k8 seems to bee stabile.
All the test done with the 64 w2k8, which has been fired, while the agent was unreacheble, got into bad standing.
In my action profile, I has a 33% decrease of the scheduled test intervall, which is working -
![:)](./images/smilies/icon_smile.gif)
Getting things done and up running on 32bit w2k8, didn't reset the scheduled time as expected.
I have been through some 200 test now, changing the time forth and back saving in between.
![:evil:](./images/smilies/icon_evil.gif)
So now I'll post a sugestion in the other forum, which can help people to control if the schedules is not brought back to it originally value.
What exactly means "unstable"? Agent crashed?? Some tests failed?I was experimenting with RMA on a 64bit w2k8.
It was very unstabel, so I found that RMA on a 32bit w2k8 seems to bee stabile.
What exactly tests do you perform? What exactly test status? Reply value?
RMA version?
Passive RMA? Active RMA?
Windows Service pack?
Do you use ODBC logging or ODBC test method? If yes, what ODBC driver do you use?
Do you have installed some antivirus monitors, personal firewall, content monitoring software? Non stanard winsock components?
If HostMonitor cannot connect to agent, it should set Unknown test status.All the test done with the 64 w2k8, which has been fired, while the agent was unreacheble, got into bad standing.
What message do you see in Reply field?
Any errors in log file specified for agent?
Do you have action that should restore test interval?In my action profile, I has a 33% decrease of the scheduled test intervall, which is working - so the test intervall became very small.
Getting things done and up running on 32bit w2k8, didn't reset the scheduled time as expected.
What settings do you use for this action?
What settings do you use for action that reduces test interval?
Regards
Alex