"Bootstrapping" powershell scripts
Posted on 2016-10-04
I'm trying to set up all the necessary WMI settings for monitoring a workstation by running a local powershell script.
It's going pretty well. I'm at the stage where it's about ready for production.
Remaining to solve:
I have all the files on a file share and can copy and import modules from there.
But the workstations aren't set to run scripts. So I need to first set them up for "unrestricted" as none of my scripts are signed.
(Then I can set them back to "undefined" when I'm finished).
Ideally, I think I'd want to do everything from a single command or desktop shortcut.
(This must be a fairly typical objective).
So how might you suggest I do that?
Right now I have to run some powershell commands to get things started.
While *I* can do that, it's more tedious and not so "exportable" to others.
(and respond "A")
Copy "\\server\c\\Scripts\MyScript.ps1" "$($Env:Temp)"
How to fire off all 3 commands without having to type them all and give a response as well?
A simple one-liner would be great!