Does anyone has an idea how to distinguish between a "non-completed Hostcheck" and a "Hostcheck which does not match given criteria"
The Idea is to create a regular expression for this issue ("Hostcheck did not deliver any info") an then start a role mapping to an empty role with the name HostCheck_failed_to_Complete or something similar. ( an expression which describes something like "Hostcheck did not deliver information within a given Timerange")
I already use regular Expressions to map a certain role if not all criteria are matched by an existing HostCheck but the in the case HC does not start or crashes I cannot distinguish.
For what will this be good or useable? Troubleshooting! If a user has problems to get all roles or function it's often dedicated to a restriction or a non-passed Hostcheck. I can determine if he has not passed all or some criteria of a given check. But the IVE-Admin never knows early if it is due to a not finished HC or an not started HC.
Any Ideas are appreciated.....
Solved! Go to Solution.
The way I've done this is to have a trivial check - one I know will always be true. This is my "host checker completed" test. It could be a process check for something which will always be running, or a registry check for something which you know will always be there. Then, I do role mapping based on the failure of that check to a role which says "Host Checker did not complete". So, any other failure is a true failure, because we know the check completed.
Hope this is helpful -
Ken
The way I've done this is to have a trivial check - one I know will always be true. This is my "host checker completed" test. It could be a process check for something which will always be running, or a registry check for something which you know will always be there. Then, I do role mapping based on the failure of that check to a role which says "Host Checker did not complete". So, any other failure is a true failure, because we know the check completed.
Hope this is helpful -
Ken
Hi kenlars,
thank you - that's it !
As in most situations the simple solutions are the best solutions. Thank you very much (shame on me not to see the wood for the trees .....)
I found a solution I like even better - I think it is guaranteed to work, at least on Windows systems - a check to see if process dsHostChecker.exe is running. If that is not true, you know Host Checker did not complete - or run at all.
Ken