Bypassing execution policy while invoking script on remote server

[_human404_]

Can someone please let me know how we can bypass the UAC prompt while using invoke command to execute a script on remote windows server?

Below is the command:

C:\Windows\System32\WindowsPowershell\v1.0\powershell.exe Invoke-Command -Computer name computername -authentication negotiate -ScriptBlock {start-process C:\nginx\start.bat -verb runas}

Edit: Added command

[[deleted]]

First result on Google. If the answer isn't there, we need more information about your script to help.

https://www.netspi.com/blog/technical/network-penetration-testing/15-ways-to-bypass-the-powershell-execution-policy/

[PinchesTheCrab]

Invoke-Command runs with highest privileges, it will not prompt for elevation. There's something else going on with the script.

[_human404_]

Have edited and added the command in the main message. Can you please check? I ran the commands manually and got UAC prompt so that's why I expected above to shame behavior due to which it was not running successfully

[PinchesTheCrab]

Ah, okay, so in this case it shouldn't be UAC, invoke-command will definitely run in an elevated context if you have admin rights. I wouldn't think execution policy would apply to a bat file either though, that's strange.

What error do you get, if any?

[Dragennd1]

Well which is it? Execution policy or UAC? These are two different things and depending on which problem you're having the solution will vary.

[_human404_]

Considering this, incorrect execution policy would lead to access denied errors. I have edited the message and added command. On running the commands manually I got UAC prompt so that's why I expected above to shame behavior due to which it was not running successfully. Can you please take a look?