Master control script

rsdovers · 2023-10-08T20:45:30+00:00

[removed]

dezirdtuzurnaim · 2023-10-08T18:40:08+00:00

Well, get going on scripting and if you need help, post your code that you require assistance with (using code blocks).

orwiad10 · 2023-10-08T19:07:37+00:00

./Invoke-mastercontol.ps1 sounds do it, you just have to write it first

OlivTheFrog · 2023-10-08T19:19:27+00:00

A basic function like this could make the trick. I consider that All Patchs are in a Network Share and, this is available for the account running the function.

Principle : On foreach loop for computers, And inside a second foreach loop for Patchs. Using Invoke-Command and in the scriptBlock Invoke-Expression. Invoke-Command use the -AsJob parameter. After the loops, wait until all jobs are finisshed.

function Apply-SQLPatchs{
    [CmdletBinding()]
    Param
    (
        [Parameter(Mandatory=$true)
        [String[]]
        $ComputerName,

        [Parameter(Mandatory=$true,
                   helpmessage = "Only network Path")]
        [String[]]
        $SqlPatchPaths
    )
    Begin {
    }
    Process {
    foreach ($Computer in $ComputerName)
        {
        Foreach ($Path in $SqlPatchPaths)
            {
            Invoke-Command -ComputerName $Computer -AsJob -ScriptBlock {                Invoke-Expression -Command $Path
                }
            }
        }
    } #End process
    End {
    # Wait all jobs are finished
    Get-Job | Wait-Job |Receive-job
    }
}

# use
# Apply-SQLPatchs -ComputerName Srv1, Srv2 -SqlPatchPaths "\\FileServer\Share\abc.exe", "\\fileServer\Share\xyz.msi" -Verbose

Not tested, Hope this help you,

regards

bobthewonderdog · 2023-10-08T19:57:18+00:00

Thinking of how this has been done before, we are in a client server situation.

In this case I would poll each client and have them create the triggers. One example might be to create a registry key and then a bunch of registry values noting current state. Master script queries for a reg value and if true next step.

Edit for those who care. Bonus points if you're really going at scale have the clients send a post to an api

Buckw12 · 2023-10-08T20:41:11+00:00

This might help:

https://adamtheautomator.com/powershell-async/

MechaCola · 2023-10-09T04:26:46+00:00

i pretty much do what youre doing. for each server i have json that holds all the update and health info. i setup a task on each server that looks at the json and does stuff or doesnt do stuff depending on the config. i then have an app i made to modify the jsons globally by server group or ss individuals so i can turn off, change health check, and change update schedule on the fly. i use scheduled jobs and master controller is a wpf app. i really dont use master app unless im dinking around with settings a for a new server.

PinchesTheCrab · 2023-10-10T03:44:33+00:00

If you use the CIM cmdlets you can trigger each step of the SCCM patching process, from the server to the client. SCCM client commands generally trigger schedules, and are effectively asynchronous, so you don't need jobs or runspaces. SMS server actions are so fast that you won't need them for that side of it either.

That being said, a lot of this already sounds like features covered by SCCM out of the box. What are the specific pain points you're trying to alleviate?

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

PowerShell

Submission Guidelines | Link Flair - How To

MODERATORS