Running powershell script on remote PC

[UrbanFreestyle]

Good morning all. So i have been teaching myself about powershell and am amazed at how powerful it is. One thing i am missing is knowing how to run the PS1 script on a remote PC on our network. Basically i would like to be able to enter a server name and have the script run on that machine. A bit like using shutdown -i 

 

Can anyone offer some advise? The ps1 will be saved to their local machine / to one of our network drives.

 

The powershell script does not need to be invoked as admin.

[keskparane]

Setup IIS with ASP. Then...

[UrbanFreestyle]

i dont need to call it from a webpage though?

[fringie]

6 hours ago, UrbanFreestyle said:

i dont need to call it from a webpage though?

You need a server to run server side code on. PowerShell is a server side language which is also .NET, IIS allows you to use .NET code although idk about powershell scripts but what he sent seems legit although not exactly recommended.

 

That being said you should do it the proper way with the correct networking settings etc. A random guide online - https://www.howtogeek.com/117192/how-to-run-powershell-commands-on-remote-computers/ (I know the guide says how to run commands but you can run a script as a command so it's the same thing basically).

 

 

[UrbanFreestyle]

i wouldnt say it is a 'server side' language though. i use it all the time on client end too.

i'm thinking i might just try the invoke command and see how i get on.

[Acedia]

Easy.

Invoke-Command -ComputerName FQDNOfTarget -FilePath \\YourNetworkDrive\Script.ps1

 

[UrbanFreestyle]

On 4/19/2019 at 12:11 AM, Acedia said:

Easy.

Invoke-Command -ComputerName FQDNOfTarget -FilePath \\YourNetworkDrive\Script.ps1

 

Thanks. so for example this would be:

Invoke-Command -ComputerName work1.domain.local -FilePath \\server1\script.ps1

 

 

[Acedia]

4 hours ago, UrbanFreestyle said:

Thanks. so for example this would be:

Invoke-Command -ComputerName work1.domain.local -FilePath \\server1\script.ps1

 

 

That would be the most basic example. There are many different ways of improving it tho. If you need different credentials you can feed them via -Credentials $Credentials if you store them in $credentials=Get-Credentials or from the secure store from your machine, you could set multiple computer names in an object and use that, importing them from an array or a text file or by getting them from AD itself, you could skip the FilePath alltogether and feed the Script directly by using -ScriptBlock {$Script} or -ScriptBlock {Restart-Computer} and so on.

[UrbanFreestyle]

10 hours ago, Acedia said:

That would be the most basic example. There are many different ways of improving it tho. If you need different credentials you can feed them via -Credentials $Credentials if you store them in $credentials=Get-Credentials or from the secure store from your machine, you could set multiple computer names in an object and use that, importing them from an array or a text file or by getting them from AD itself, you could skip the FilePath alltogether and feed the Script directly by using -ScriptBlock {$Script} or -ScriptBlock {Restart-Computer} and so on.

Thanks, thankfully no creds needed. I hope that the invoke command isnt blocked.

[UrbanFreestyle]

sadly invoke is blocked also cant run it through a PS Session

 

[Acedia]

4 hours ago, UrbanFreestyle said:

sadly invoke is blocked also cant run it through a PS Session

 

Run this on the target

Enable-PSRemoting -Force

Enable-PSRemoting -Force

 

[Guest]

there are some nice tutorials around as running scripts remote seems to be a part of powershell. depending on what you want to do you may also have a look at ansible. supports windows too and can run powershell scripts too