New Post: VBS fails but PDAT says success

Hi David,

I've been able to reproduce this using a buggy VBScript and I don't think it's something specific to the PADT. If you run the VBScript in a command prompt and then type echo %errorlevel% you should also see a 0 return code.

You will probably need to put some error handling in to the VBScript and throw a different error code if you catch an error.

Cheers,

Sean

PS. @André, David's quotes are correct, the back ticks are escape characters in PowerShell.