how to push 3rd party software updates to domain clients?
-
We use Ninite pro.
-
I prefer to use Chocolatey.
Salt and Ansible are good options as well, as @DustinB3403 already mentioned.
-
I’d go choco. Ninite requires rebuilding the installer (last time I used it) ever time you add/update/remove an application .
Choco is much easier, @JaredBusch uses it if I recall.
-
@gjacobse said in how to push 3rd party software updates to domain clients?:
I’d go choco. Ninite requires rebuilding the installer (last time I used it) ever time you add/update/remove an application .
Choco is much easier, @JaredBusch uses it if I recall.
It's included in our RMM now (Atera). Really nice when you have someone calling asking for software and can say, "It's now installed, look at your start menu" without missing a beat on the phone.
-
@travisdh1 said in how to push 3rd party software updates to domain clients?:
I prefer to use Chocolatey.
Salt and Ansible are good options as well, as @DustinB3403 already mentioned.
You can actually use use salt and ansible to manage chocolatey, which is cool.
-
You can add third party updates with WSUS, but it's more of a manual process to add them than using chocolatey
-
@registry2021 said in how to push 3rd party software updates to domain clients?:
@gjacobse said in how to push 3rd party software updates to domain clients?:
@registry2021
You can via GPO.I read pushing software via gpo is a pain. is there another way?
Definitely look into Chocolatey as others have suggested and only use GPO's with MSI if required. I recently moved over to Chocolatey (based on suggestions here) and am very happy I did.
-
Chocolately and PDQ are both very easy to utilize.
-
@jclambert said in how to push 3rd party software updates to domain clients?:
Chocolately and PDQ are both very easy to utilize.
I'll be using this on domain environment and hoping I can update the workstations remotely. is it possible and which one suits best?
-
@registry2021 said in how to push 3rd party software updates to domain clients?:
I'll be using this on domain environment and hoping I can update the workstations remotely. is it possible and which one suits best?
Both can be used in a domain, the question is completely dependent on what you're willing to setup.
PDQ Deploy is likely the easiest to "use" if you don't want to setup anything and you just want a GUI to push packages from a Windows desktop environment.
-
Chocolatey is very likely the most flexible solution, but would require some setup on your part to get it going throughout the domain.
-
Chocolately - I use the their package choco-upgrade-all-at-start. This will schedule choco to upgrade at every reboot.
There's another package choco-upgrade-all-at that defaults to 4 AM update daily.
-
@Dashrender said in how to push 3rd party software updates to domain clients?:
Chocolately - I use the their package choco-upgrade-all-at-start. This will schedule choco to upgrade at every reboot.
There's another package choco-upgrade-all-at that defaults to 4 AM update daily.
/Me screws over @Dashrender because I never reboot my computer. "What closing the lid doesn't count as rebooting?"
-
Chocolatey is more flexible, but PDQ is super simple. We implement PDQ here currently, as it was an uphill battle to get anything going. Now that the benefits are seen, many roads have opened.
I am all for automation, and open source is a plus. Salt may be the next venture, as it looks like a fleet of Pis, and an expansion of Linux servers may be in our future.
-
@jclambert said in how to push 3rd party software updates to domain clients?:
Chocolatey is more flexible, but PDQ is super simple. We implement PDQ here currently, as it was an uphill battle to get anything going. Now that the benefits are seen, many roads have opened.
I am all for automation, and open source is a plus. Salt may be the next venture, as it looks like a fleet of Pis, and an expansion of Linux servers may be in our future.
Yeah - I really need to look into salt myself. One frustrating thing is not knowing the status of any anything. not that salt can help with that, at least I don't think it can directly.
-
We can't use Chocolatey, at least the public NuGet repo it uses by default.
But for common apps, I have it 100% automated via Azure DevOps, Intune, and the PSADT.
Another option I'm still looking into for certain apps is using Azure DevOps like above, but then deploying the artifact to a NuGet repo then used by the newer WinGet tool.
-
@Dashrender said in how to push 3rd party software updates to domain clients?:
Chocolately - I use the their package choco-upgrade-all-at-start. This will schedule choco to upgrade at every reboot.
There's another package choco-upgrade-all-at that defaults to 4 AM update daily.
You specify the time when you install it.
choco install -y choco-upgrade-all-at --params "'/DAILY:yes /TIME:17:00 /ABORTTIME:20:00'" -
@Dashrender said in how to push 3rd party software updates to domain clients?:
Chocolately - I use the their package choco-upgrade-all-at-start. This will schedule choco to upgrade at every reboot.
There's another package choco-upgrade-all-at that defaults to 4 AM update daily.
You can just make a Scheduled Task,too.
-
@Obsolesce said in how to push 3rd party software updates to domain clients?:
We can't use Chocolatey, at least the public NuGet repo it uses by default.
Lots of people with that limitation, but just make your own. Still a great tool and, we'd assume, it means any public repo would be an issue for you so the need for your own repo would be a universal need.
-
@jclambert said in how to push 3rd party software updates to domain clients?:
Chocolatey is more flexible, but PDQ is super simple. We implement PDQ here currently, as it was an uphill battle to get anything going. Now that the benefits are seen, many roads have opened.
I am all for automation, and open source is a plus. Salt may be the next venture, as it looks like a fleet of Pis, and an expansion of Linux servers may be in our future.
Sounds like some great ideas!
