The conditionals should only be looking for a pass\fail response. 0 = pass, and 1=fail. Theoretically 0 should indicate pass, and anything else would be seen as a fail. Give that a try and let me know if that helps.
Hi bcstring just testing that now.. but i have seen others using vbscript and using custom exit codes like 64 and 32 and it work in their examples.
is it just a powershell limitation? will let you know how i get on
Ok so no matter what i did - use 0 an 1 or specify a custom exit code this would not work.
My work round is using a completely different method. I am finding that replace text action works great with conditionals. Its not how i want it to work and will continue to look into the powershell issue but as we need to get moving on this migration.