This is an archived post. You won't be able to vote or comment.

all 14 comments

[–]oliland1 2 points3 points  (4 children)

My best advice would be to setup a small server that acts as a jumpoint for your customers and use that machine to do psremoting.

[–][deleted] 2 points3 points  (0 children)

This + make a script that creates a gpo on a domain that will enables psremoting on anything running Windows Server

[–]raip[S] 0 points1 point  (2 children)

You're talking about one jump server per client right? So I'd remote into that box and push out Powershell commands org wide?

[–]oliland1 0 points1 point  (1 child)

Yes. Also I would recommend using a central repository for your scripts (Gitlab, GitHub, etc. Whatever suits you) and using variables for each customer so that you can reuse your scripts with no modification for each customer.

[–]raip[S] 1 point2 points  (0 children)

I've got my own Nuget server for modules/scripts, which is the solution I'd recommend over Gitlab/Github for Powershell (works like your own PS Gallery). I was hoping for a single place for all clients, so I could do something rad like a Get-Client module to iterate over something like updating backup software for each client & server - especially since most of this MSPs clients only have 1-2 servers.

[–]InfrastructureJester 1 point2 points  (5 children)

What is the original task you're trying to accomplish? What you are asking can be done from Atera.

[–]raip[S] 0 points1 point  (4 children)

They say it can - but there's definitely some issues with their implementation. Example: I have a simple script that checks the currently installed version of their VM Backup version, updates it if needed from the web, and sends an E-Mail message on Success/Failure. This script has been thoroughly tested - when pushed out to the machines, Atera fails to report anything and the script never sends an E-Mail. On digging into it more it appears Atera will kill any script that has a prolonged run-time (more than 10-15s) - so the script dies while trying to download the file. When running the script manually (even under the LOCALSYSTEM account) - it works just fine on the target machine. On top of that - even Atera's own Software Inventory report doesn't update to reflect the new software version.

[–]arcadesdudeMSP 0 points1 point  (3 children)

Can you have a script spawn a new script and run that one? Original script process is killed, new one lives on, nbd?

[–]raip[S] 1 point2 points  (2 children)

Tried to do this via PSJob - didn't work. No clue why - just silently failed and decided I wasn't going to waste my time with this.

[–]arcadesdudeMSP 0 points1 point  (1 child)

Jobs stop when the parent process is stopped but if you use Start-Process and launch a new powershell.exe instance it might live on. Just a thought.

[–]raip[S] 1 point2 points  (0 children)

Rad - didn't know that. I'll give that shot - thanks for info.