[PowerOfTheShell Plugin 1.5]

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? 

[PowerOfTheShell Plugin 1.5]

Hi KreAch3R

Glad you find the plugin useful.

I am not familiar with 12 noon and the parameters but I will try it out for size and let you know my findings. One thing maybe. The script runs fine when you execute it from your own user in powershell right ? Have you looked if you have set the right impersonation settings in POTS maybe.

/cptrico

 

Yes, it does when running it in powershell! I thought that it had something to do with user permissions, but I don't know what I should fill in the user and password fields. I am using an outlook online account as my Windows User account. This account also has 2-step verification enabled. I tried some setups (using/emitting @outlook.com, trying my main password) but it doesn't seem to work. Should I create an app-specific password?

[PowerOfTheShell Plugin 1.5]

Hello Cptrico,

 

I am using your plugin for a while now, and it is very useful! I am trying to compare it with display changer . I have successfully created the .ps1's that are required, but when I try to run the command from my Pulseway Android app, the app reports "there is no monitor with that name.". I think that is happening because of the variables "\\.\DISPLAY1". Can you help me solve this? What should I do?

 

This is an example .ps1:

& "I:\12noon Display Changer\dc64cmd.exe" -monitor="\\.\DISPLAY1" -width=1366 -height=768
& "I:\12noon Display Changer\dc64cmd.exe" -monitor="\\.\DISPLAY2" -detach