PowerOfTheShell Plugin 1.5 in Windows Client API Posted October 19, 2014 Hi Again, that is actually not something I have come across before using this kind of user. I would just expect if the user were capable of executing the PowerShell script it would be fine to impersonate as this user in POTS. You could try just to test the script and create a local user, try it out first in PowerShell and then add it to POTS if it works after we know it is user related and there is a need for a workaround or requirement for a dedicated user for impersonation. Cheers /Cptrico I created a local "Test" user, run the powershell script while logged in from that user, and it run fine. I tried to run it from POTS while impersonating "Test" and it didn't run. I didn't have to use the impersonation option before though, and I don't know if I am doing everything correctly. How exactly is POTS calling the powershell script? Given that the script responds with "no monitor found with that name", what exactly is missing and the script can't complete completely?