Get the latest product updates, ask technical questions, and learn best practices
Recently active
Hey all, Just wanted to check to see if Automox has the ability to patch drivers on Windows devices? I.e. how WSUS has this ability? Would like to retire WSUS completely for end user devices, and would be beneficial to tap into the MS Windows driver update channel.
We’re excited to announce that Automox now supports patching for the following third-party applications: Amazon WorkSpaces Windows/macOS QZ Tray Windows Don’t forget that our third-party support catalog is always available to find the most up-to-date coverage of our third-party supported titles.
We’re excited to announce that Automox has the following third-party titles in progress and coming soon*: Amazon WorkSpaces Windows/macOS QZ Tray Windows Don’t forget that our third-party support catalog is always available to find the most up-to-date coverage of our third-party supported titles. *Disclaimer: As these titles are still in-process, Automox cannot guarantee the eta for third-party support as working with every vendor is different.
I have created a deployment configuration via the Microsoft Intune dashboard. Before I deployed the app I had to convert it to an intunemac using IntuneAppUtil. In my Intune dashboard, it says the app has been installed on the macOS (Big Sur) device. Using the terminal I can indeed see the agent installed in /usr/local/bin/amagent. But when I checked my Automox devices dashboard I don’t see the device registered. Has anyone done this before successfully what additional steps have you done? Screen Shot 2021-09-02 at 3.55.18 PM1118×623 47.8 KB Thanks.
I would like to deploy SQL patches (not the latest version) but a N-1 version leveraging ‘Patch Only’ policy or We need to leverage our script to install a specific package.
We’ve been making good use of the Automox Agent Deployer and it really has helped us get started quickly. As we enter the next phase of our rollout, we want to target deployments with a given Automox Key to a subset of machines that share a Crowdstrike Host Group with machines we don’t want to target - so we’d really like to be able to deploy using FalconGroupingTag and SensorGroupingTag.I think our workarounds would be move machines into different Crowdstrike Host Groups, which would be challenging due to our other integrations, or manually run the script against each host via Crowdstrike RTR, which would require other development work and doesn’t make use of the excellent Automox Agent Deployer that is already built.
Is it possible to create a policy to scan a group of devices for missing critical patches then create a report the breaks out which critical patches are missing. We do not want to patch those devices with this policy, only scan.
We’re excited to announce that Automox now supports patching for the following third-party application: YubiKey Manager Windows/macOS We’ll share third-party titles that are in progress and coming soon as well as they become available!Don’t forget that our third-party support catalog is always available to find the most up-to-date coverage of our third-party supported titles. Have a great weekend!
We’re excited to announce that Automox now supports patching for the following third-party applications: 3Dconnexion 3DxWare Windows ePlayer Pro macOS We’ll share third-party title that are in progress and coming soon as well as they become available!Don’t forget that our third-party support catalog is always available to find the most up-to-date coverage of our third-party supported titles.
This doesn’t happen too frequently, thankfully, but when it does it can be very frustrating for end users.A patch that requires a reboot fails to install so Automox tries again on the next scheduled run. As I find I have to run schedules often to keep up with the number of patches, this can mean that a user has to reboot every day.What I’d like is the ability to disable a patch after a number of failed attempts so that this doesn’t happen. I’d also like to be notified about this so that we can investigate the cause.As we get too many failure notifications we’ve actually turned these off for now anyway.Does anyone have any thoughts or suggestions on this?Thanks
Hello, I would like to notify end users once their patching is completed so that they know if it is okay to shut down their device.If a device is shut down, logged out, or put in sleep mode, the patching will fail. I’ve noticed this multiple times with testing on different devices. There is no real way for an end user to know when their patches have been updated. Furthermore, on Automox I am able to see each “Device Status” as “Refreshing” when updates are being conducted, and “Ready” once they are complete.I would like confirmation that Refreshing = Patching. With that wording it is a little confusing.I have ran manual patches on certain devices that will begin “refreshing” and after completion, they will turn to the “ready” state. Although I will still see the same patches needing an update in the “Software” section of the device. Does anyone know why this is happening? It is as if the patch runs and after completion nothing actually happened with those items that needed to be patche
Good Afternoon,I’m planning on deploying via GPO using MSI. I’ve gotten the ACCESSKEY entry added to the MSI using Orca. I was hoping to assign device group membership as well. Could someone please provide the syntax for this? I haven’t had any luck, and am not finding any documentation. I tried the following with no success:Property: GROUPValue: “Default/Parent Group/Device Group”Thanks!
The team is busy at work this week and we’ll have updates to share soon. In the meantime, don’t forget that our third-party support catalog is always available to find the most up-to-date coverage of our third-party supported titles.
Actually, we completely reset the PC and wiped it clean, and built the PC from scratch. However, the automox console is showing the pc with the old hostname. How can I clear this up?
Hi there,I’ve been experiencing an issue on certain clients where the Automox device section states “Reboot Required” even when a reboot has been administered, in some cases multiple times. I’ve tried manually restarting, restarting from the Automox client, CLI restarts, etc. The message is persistent. This seems to only apply to macOS devices. Any ideas?Best,Dane
We’re excited to announce that Automox now supports patching for the following third-party applications: Asana macOS Dependency Agent by Microsoft Windows When we have titles in progress or coming soon, we’ll list those here as well!Don’t forget that our third-party support catalog is always available to find the most up-to-date coverage of our third-party supported titles.
Hi Automox Community! Here’s the latest content in AXU to keep you ahead of the game: Level II Practitioner Exam - Level up your game and score a certificate to boast about!Automation Maturity Playbook - Unlock the power of automation with our playbook featuring 10 essential plug-and-play patch policies.Automating Patch Tuesday - Say goodbye to patching headaches! Learn to navigate Microsoft's Patch Tuesday with confidence and efficiency. AXU is always adding new content to help you make the most of Automox. Let us know what you’d like to see in the university!
We’re excited to announce that Automox now supports patching for the following third-party applications: exacqVision VMS Client Windows/macOS HeidiSQL Windows ideaMaker by Raise3D macOS Snagit 2024 Windows/macOS And, the following titles are in progress and coming soon*: Asana macOS CutePDF Writer Windows Dependency Agent by Microsoft Window UltraVNC Windows Don’t forget that our third-party support catalog is always available to find the most up-to-date coverage of our third-party supported titles. *Disclaimer: As these titles are still in-process, Automox cannot guarantee the eta for third-party support as working with every vendor is different.
Hi I would need some adviceI use policy “Patch recently released macOS updates”. It shows a pop-up window and if user click on “patch”, e.g. MacOS 14.3.1 is upgraded to 14.4. But I see it has two IFIf user does not click on “patch” button, MacOS is not updated If he does it, MacOS is not restarted. There is just notification in Settings icon, but my users ignore it. Is not there any way to enforce patching even if user does not click “Patch” button? Is not there any way how to significantly show to user he should reboot? And if he does not reboot, reboot is forced e.g in 48 hours? Thank you for you helpAldomoro
greetings with everyone,Is there automox compatibility with Qradar SIEM?I am investigating, if anyone has a similar case, could you give me some guidelines to follow the best path?
We’re excited to announce that Automox now supports patching for the following third-party applications: Adobe Acrobat Reader 2020 Classic (MUI) Windows/macOS Nudge macOS And, the following titles are in progress and coming soon*: exacqVision VMS Client by Johnson Controls Windows/macOS HeidiSQL Windows ideaMaker by Raise3D macOS Don’t forget that our third-party support catalog is always available to find the most up-to-date coverage of our third-party supported titles. *Disclaimer: As these titles are still in-process, Automox cannot guarantee the eta for third-party support as working with every vendor is different
We’re excited to announce that Automox is working on the following third-party applications that are in progress and coming soon*: Asana macOS Adobe Acrobat Reader 2020 Classic (MUI) Windows/macOS CutePDF Writer Windows exacqVision VMS Client Windows/macOS HeidiSQL Windows ideaMaker by Raise3D macOS UltraVNC Windows Don’t forget that our third-party support catalog is always available to find the most up-to-date coverage of our third-party supported titles. *Disclaimer: As these titles are still in-process, Automox cannot guarantee the eta for third-party support as working with every vendor is different.
Discuss the Hands-On IT Automation 101 podcast here!
Any solutions to the output below? We have such low compliance because everyone uses Teams. Failed to apply patches ("Teams Machine-Wide Installer..."): Error: Microsoft Teams is unable to patch because it is currently running.
We'd like to switch some of our AWS instances over to Graviton, for the cost/performance improvements, but there isn't currently an Automox agent for ARM.Is this something in the roadmap, or should we be considering an alternative patch management platform which does support it?
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.