Automox Platform Info

I have installed all available patches in Automox, but the vulnerabilities I scanned on Lansweeper have not decreased. Why is this? 

Anyone using the beta agent and running into issues? I am seeing a number of failures and the log shows they failed due to execution policy issues. Unable to run the script because running scripts is disabled. This is new.

Is ARM64/Snapdragon supported by Automox on Windows 11 yet? For both install and for updating other ARM applications?

Hello!I’m trying to make it so that a user in a single Organization can use a Custom Role I have created.  So far this is proving difficult, as the distinction between whatever “Account” level and “Global” level is is about as clear as mud.  The descriptions of them are the same.  The best I could muster was a user who had the role assigned shown via Organizations, but if you looked under Roles & Permissions the role had 0 users assigned.I had a conversation with someone who used 3 terms (Account/Zone/Organization) to refer to Organization.  And also “Account” referring to… something else.I guess my 2nd question is… what is an Account in terms of Roles & Permissions Account/Global?3rd… what else is “Account?”More confusing is, as a Global Administrator, I can see users defined in 2 places.  With my custom role assigned to nothing, I can see the user in question at a Global level “unassigned” but not present within the Organization I want them to be in with the custom role.This

Apple released macOS Tahoe 26 with a redesigned interface, Apple Intelligence integration, and dozens of security fixes.Automox now provides same-day patching and full support so you can:• Deploy updates across Macs immediately — in office or remote• Close vulnerabilities in core subsystems, drivers, and frameworks• Maintain compatibility with Apple’s versioning shift (v26)Automox zero-day support keeps your fleet protected from day one while enabling fast, automated deployment.✅ Day-one security for macOS Tahoe 26 starts here!

Hello,For some reason our Axonius integration with Automox (via API) has stopped working and I can’t seem to find the API key for it anywhere (but have noticed a Global level “New” Keys section just appeared).  How can I create an API key specific to a read only user that we have?Thanks,Mark

The overall structure of zones vs. groups is creating a lot of redundant issues. As a service provider, we have many clients, which means a lot of consistent policies and users being made. Having clients in zones, we can assign their users the ability to view their console. But then we have to duplicate the same policies, worklets, and users from one zone to another. This is really redundant and the overall structure of zones vs. groups just makes API calls for all clients a nightmare. I see that you can customize the Automox agent installer to specify a group. Managing by the zone (top-level) and groups (clients) makes everything easier to manage. Only thing missing is limiting a user to view only specified group(s). Is there a possibility of this being added in the future? It is just very odd that there is limited to no features when administrating on a global level.

 Attention IT pros: Office 2016 and Office 2019 are officially reaching end-of-support on October 14th.That means no more updates, no more security patches, and definitely no more excuses. 😬Join us next Wednesday, September 24th at 10:00 AM CST for our Automox Expert Insights Webinar: Migrating from Office 2016 and 2019 to Microsoft 365.We’ll cover: Why upgrading matters (hint: it’s not just about shiny new features) How to migrate smoothly without disrupting your users—or your sanity Key security risks to avoid when moving off legacy Office versions How to remediate at scale with Automox Worklets, so you can automate the heavy lifting and spend less time babysitting updates Think of this as a friendly intervention for your older Office installs. 💼➡️☁️Let’s make this transition painless and keep your org secure.🗓️ Date: Wednesday, September 24th⏰ Time: 10:00 AM Central🔗 Register now: https://university.automox.com/best-practices-webinar-registration

Hi all,  We are currently making use of the Windows 11 Feature Upgrade worklet (Windows - Configuration - Windows 11 Feature Upgrade) and this had been working quite nicely for us, however we are recently experiencing and issue whereby this does not seem to be working. Upon checking the logs of devices, we are seeing that they have:  {"args":"","response":"[\"124\",\"Device is on a Windows 10 build. Running the Windows 11 Readiness Check to determine eligibility for the Feature Upgrade.\\r\\nEligibility check passed.\\r\\nDevice is Windows 11 Ready.\\r\\nFlagging Device for remediation.\",\"COMMAND TIMED OUT.\"]"} Please can somebody advise of how I can review why these are timing out and perhaps up the timeout limit to ensure that this is back working?  Thanks! 

Hi all,We would like to have a download time different than the patch time.At this moment, we have a policy schedule at 00:00 and a automatic restart enabled with a deferral of 12h in order to reboot all critical systems during working hours if something happening. But if any patch installation succeed but generates any problem in the machine, it will stop working. Is there any workound or idea of how to achieve what we want? To dowload around 00:00, patch around 11:00 and then reboot at 12:00? Thank you,David.  

Hello all,I’ve run into a couple of issues I’m looking for solutions for with Automox’s implementation of SAML, one of which is a security concern. Scenario 1: You have an Entra joined Windows device that you log into with an Entra ID account (joel@contoso.com). Once logged in, you open up a fresh copy of Microsoft Edge with no stored credentials, cookies, or cache. Finally, attempt to log into Automox.  Expectation: Edge will use your device credential by default to SSO authenticate you into Automox, if that is rejected, you will be prompted to create a browser token via Microsoft to authenticate to Automox. Reality: The device credential created by Edge is rejected by Automox, no attempt is made by Automox to request your computer create a browser token, and there is no way to prevent Edge from using your device credential in the browser.Result: You simply cannot use Edge to log into Automox in this circumstance unless you use an incognito window.Scenario 2: You have a regular accoun

Hi, I just started creating different groups based on OS and core business functions, and came to realise that you can not really automate based on those filters, automation is based on policies. I can run a policy for all devices affected to it, but can not run all policies affected to a group. Am i missing on something, or is Automox just not built this way, and that is possible room for improvement ?

Hi Team,Is there any way to enable below through script/policy on mac rather than going and executing command individually on each systemhttps://docs.automox.com/product/Product_Documentation/Agents/Agent_Installation/Install_and_Configure_Automox_Agent_for_Apple_Silicon_Devices.htm

Our Monthly Expert Insights Webinar is right around the corner—don’t miss your chance to level up your device visibility game. 🔒 You can’t secure what you can’t see. If your device inventory still feels like a guessing game, we’ll show you how to fix that (no spreadsheets required 🙌). 📅 Wednesday, August 27 | 🕙 10:00 AM CT🎟️ Register now to save your spotWhat You’ll Learn:✅ How Device Inventory actually works (and why it’s your new BFF)✅ A full view of OS, hardware, software, and IP details✅ How to spot device health issues before they become disasters✅ Ways to harness APIs for automation and insights Who Should Join?IT admins, security pros, and automation fans who want more control, less work.🎙️ Featuring: Kyle, Senior Solutions Consultant👉 Unlock total visibility of your device fleet. 

Not sure if this is available or not, but I’m hoping we can get a feature put in.Issue:When I go to a device, and check the software to see what needs updates, I see which ones need updates, but I don’t truly know quickly which policy is going to update it. Solution:Ideally, we have two columns.Policy Column: This will show you the name of the policy that will update the software (or one that will be doing it next if multiple) Update Scheduled for: This will show you when the software is actually going to get updatedThis way, when you are looking at a device and it’s software section, you can quickly see when the update is happening and by what policy. Just an example the current software section, and what the column would look like 

Hi  What is best possible way in automox to update zoom workspace to latest version on 25 devices.  

We are aware of the issue with initiating reboots from windows and that these are not completing the required Automox reboot work. For instance if a user @10AM defers a policy reboot for 4 hours and then decides to reboot their device @1PM during lunch the reboot work is not completed. I understand this is tricky to fix. But how are people dealing with those devices as they can remain in ‘Needs reboot’ for quite sometime if no manual intervention.  Is there not a worklet that can trigger the automox notifications to say ‘click here to reboot’ or similar. Be good if the popup could remain when reboot is deferred so that reboot could be initiated from the popup. Thanks Chris

Device Status Shows Disconnected, but user is active Logged In.Any Idea why this is showing as Disconnected? 

I’ve just started looking at the API documentation, and it looks like if I don’t know the Device ID but only the name, the only way I can query the API is to return all devices and then filter my results.The only filter option I can find in the documentation for the servers ‘is_compatible’.Is getting all servers and then filtering the results the only way?Thanks!  

This script will dump all available critical updates for all of the endpoints in an organization into a .csv file along with the number of days the update has been available and if the update requires a reboot. You’ll need to set the following before running the script: $apiKey = 'YOUR_API_KEY' - in your console, go to Settings->API and select the API key. Note that the API key is per admin user, so you and another admin in your console will have different API keys. $orgID = 'YOUR_ORG_ID' - put in your Org ID which can be found by looking at the URL on the dashboard and selecting the value after the “?o=”: [https://console.automox.com/dashboard?o=1234]. In this example the Org ID is 1234. You can also modify $filepath if you want to change the file name or save it in a different location. Keep in mind the script will overwrite a previously generated file if it exists. $apiKey = 'YOUR_API_KEY' $orgID = 'YOUR_ORG_ID' $filepath = 'C:\Temp\CritUpdates.csv' Set-Content $filepath -Value

You can’t secure what you can’t see. If your device inventory is a guessing game, we’ve got answers (and they don’t involve spreadsheets  📅 Tuesday, August 27 | 🕙 10:00 AM CT🎟️ Register Now What’s In It for You? Get visibility: What Device Inventory actually does (and why it’s your new best friend). See the goods: OS, hardware, software, IP—yep, it collects all the juicy details. Spot the unhealthy: Track device health and know what’s falling apart (before it does). Do cool API stuff: Pull data, automate insights, and skip the manual labor.  Who’s This For?IT admins, security pros, automation fans — if you manage devices and want more control (without more work), this is your jam. 🎙️ Featuring:Kyle, Senior Solutions Consultant  Unlock total visibility of your device fleet.Save your spot »

Hello Everyone!We're inviting you to our Office Hours session today, August 1st at 12 pm MST/ 1pm CT/ 2pm ETThis is a live Q & A dedicated to answering your questions!Click here to register for the session.

Wrangling spreadsheets like it’s your day job?Automox is rolling out new reporting all through 2025 — real-time dashboards, role-based views, and actionable insights built right into the console.Less manual work. More visibility. Smarter decisions.It's reporting built for action.Learn more here: https://www.automox.com/solutions/outcomes/it-visibility-reporting 

Start where all great IT legends begin — At the beginning. Also called: Onboarding Week 1: Readying Your EnvironmentIf diving into a new platform feels like debugging someone else’s code with no comments…We get it. That’s why we made it refreshingly simple. ⚙️ Start with the basics: Preparing your environment Setting up Groups Hitting “deploy” without crossing your fingers Because skipping straight to “advanced” without knowing what a group does?That’s how you find yourself working weekends. 🗓️ Next live Week 1 session: August 6 at 10am CT📍 Join the onboarding fast track Less guesswork, more “oh THAT’S how it works.”

Hey IT Pros,If your patching strategy feels more like “cross your fingers and hope for the best,” we’ve got good news. Jeremy is back tomorrow with an Expert Insights webinar that’ll help you use Automox Analytics to bring order, insight, and serious efficiency to your patching game.  Here’s what you’ll walk away with:💡 Spot blind spots before they spot you⚙️ Track what’s working (and what’s just noise)📈 Get the performance metrics you actually care about🔍 And confirm whether your “best practices” are actually best for your environment It’s time to stop guessing and start knowing. Analytics can be your secret weapon—or at least a really smart assistant.🧠 Join us and patch smarter, not harder.🎟️ Don’t miss it. Your endpoints will breathe a sigh of relief. Topic: Using Analytics to Improve Patch Coverage and Performance🗓️ When: Wednesday, July 23 at 10AM CST🔗 Register here: https://university.automox.com/best-practices-webinar-registration