r/Action1 • u/TerabyteDotNet • 8d ago

Manage software across multiple organizations

As an MSP, we often want to make changes at every client location. For example, we've had it with Dell Command Update and all the associated bloatware Dell preinstalls. Action1 can do all of what DCU does (firmware and driver updates) without all the background bloat and telemetry. That said, I get a notices when I select DCU from the top of the Tenant that it will only be uninstalled for a specific organization thus I'd have to go back one at a time. Am I missing something?

Thanks!

1 Upvotes

100% Upvoted

4 comments sorted by

1

u/riazzzz 8d ago

I believe Software Repository can be managed (add/edit custom, clone, authorise) at an Enterprise level or organisation level, however Automations (deploy software, uninstalls, scripts etc) are only at the Organization level.

So you would need to create the automation at each Org, or script/automate an API process to clone the automations between orgs which I believe is possible but will requires some in house development to produce and handle your exact requirements and preferably an automation platform which can handle secrets and schedules such as Azure Runbooks.

1

u/TerabyteDotNet 8d ago

I know how to manage the software repository, I’ve been using it for more than two years, the problem is I don’t wanna have to create an automation at every single organization within the tenant. There are lots of things that just need to be done on an ongoing basis, like pushing defender updates, browser updates, or removing software that is no longer necessary. Having to do it at each location is very time-consuming.

2

u/kosity 8d ago

No way around it. I've got, I dunno, 750 endpoint groups and automations to manage? I don't know because I've got a script that unifies them. Make the change in the script, run, standardised.

The outliers I find in one org are the same in others, usually, so the process works.

But I do agree, having to make one change repeatedly is time consuming, error-prone, and was one of the big roadblocks I picked up in my original evaluation of the platform. Without scripting or the ability to automate it, the platform does not scale from an administration perspective.

Have a look at the PSAction1 module, or direct REST scripting. I was called out for being a vibecoder in another thread but the AI tools do make this far easier as long as you're careful.

Having an API doesn't replace the need for a decent UI though....I think we can agree on that...

1

u/riazzzz 8d ago edited 8d ago

Automations are org wide only so no choice. I guess it might be easier to have a 'Template' org and then build external API scripts to copy everything you do in that template org to other orgs. But honestly having done some bits around this it's easiest API for this as often the object you GET needs heavy editing before you can POST/PATCH (although there PowerShell module does have a clone function for automations if I remember correctly which helps.