I am seeing behavior when executing scripts using invoke-vmscript from a shared powershell session that I get null from the output from time to time, but not always. Strange that the powershell executes without errors, but the result that is supposed to return does not. If I run it from the powershell host, it returns output. I am thinking it could be memory related. I got around of some of it by opening new powershell sessions for those workflows. Has anyone seen this?
Thank you