Automox Platform Info

Hi Automox Community, I was wondering if anyone is running Automox with Oracle Linux boxes. We have tried some and the agent never gets past initialization stage. -c in console indicates that it runs through sever get commands and seemingly just starts over. Has anyone else encountered this issue and possibly can give me advice on resolution and troubleshooting? Running on Oracle Linux 8 VM, Thanks, Dan

I’m looking to search for a device name by using like or contains. I’ve found that using name=PartialName* I can put a * a the end of the term and it works. Using a * at the front of the term results in an error 400. $FullURI = "https://console.automox.com/api/servers?name=partialname*&o=$orgID" This page talks about advanced filters for HostName and “like_any” or “not_like_any” but there is no info on where to include that or how the spacing work on the URI if that’s where it goes. It also mentions “display-name” and “contains” or “does-not-contain” with the same issue. Where do these filters go? The body?

Happy Friday, everybody. We’re all extremely excited to announce our new integration partnership with Splunk! In short, the add-on(s) will allow data from Automox to be ingested & displayed on a dashboard in Splunk (Enterprise or Cloud). By using a combination of the Technology Add-On and the Dashboard for Splunk, users will be able to visualize and search across the data imported from Automox. Personally, I think it’s awesome to partner with a SIEM solution like Splunk! Some key benefits include:  Faster Data-Driven Decisions: Triage events faster with access to merged contextual data with Splunk data sources. Cross-Team Visibility: View a single source of truth for quick operational and security decisions. Customizable Alerts, Reports, and Visualizations: Uncover device patterns and trends with enriched data insights and viewing capabilities.    Documentation fr

Curious to see how many different policies and groups everyone has setup in their console - also include how many endpoints those cover!

Hi All, I have a question about setting up a run book with possible mutiple stages. Is it possible to chain dependent policies? For example I want to do the following as a single workflow: 1 - Run Worklet, if it unsuccessfull - STOP send notification 1, if it successful, CONTINUE 2 - Run Policy, if it unsuccessfull - STOP send notification 2, if it successful, CONTINUE 3 - Run Another Worklet

Would be great if Windows, macOS, and Linux could all serve dialog prompts / pop-ups to users when Automox patch policies are running. Even something baked into Linux that we could tap into such as “notify-send” would suffice here. I’m sure we could create a script to do this but I feel like having to script something and create a patch policy is sort of counterintuitive.

So say you schedule something for the 5th Saturday of a month and there is no 5th Saturday of the month. Does the policy just kick off on the 4th Saturday then?

Right now, we can edit device tags, but in order to keep from overwriting current valuable device tags, we need run a GET command, save all device tag content into an array, and then execute a PUT command to write an entirely new batch of tags. It would be way easier if we could just run a PATCH command as an additive operation add more new tags. This is a particular pain point when we have scripts creating from-scratch tags for devices that end up overwriting valuable manually-created tags that some of our technicians have added for their own records.

I’m having a problem in one of my saved Policy’s. I enabled Device Targeting and added an Attribute, Condition and Option and saved successfully. But now I can’t clear all those values and turn off the Device Targeting. When I clear those values, turn off the Device Targeting and attempt to Save I get this error message: Error: Device filters must have a “field” key. Device filters must have a “op” key. Device filters must have a “value” key Additionally, I didn’t like the idea of giving end users too much time to defer reboots so I changed the hours of the Deferral Settings from 1, 4 and 8 to 1, 2 and 4. After speaking with my manager we agreed that some of our positions will need to defer 8 hours. So I set them back to 1,4 and 8 and Save but when I open the policy again they are back to 1, 2 and 4. Any suggestions?

I assume this has been asked before but the only reference I could find was about the planned dynamic groups feature. I’m new to this product so maybe I’m missing something. Are there plans to allow a device to be a member of more than one group? From an outsider standpoint it seems relatively easy but I assume there is more to it. Thanks for your insights Ron

Hi All, want to see what I’m doing wrong here… trying to follow the example here https://developer.automox.com/openapi/axconsole/operation/issueDeviceCommand/, to issue a command to a server so it can remediate itself, I want to do it one server at a time so it doesn’t take everyone down at once… I’m trying to use the command type “policy_{policy_id}_remediate”  so here is how I’m calling it through curl  curl -X POST‘https://console.automox.com/api/servers/{server_id}/queues?o={org_id}’-H ‘Authorization: Bearer {api_key}’-H ‘Content-Type: application/json’-d '{“command_type_name”: “policy_{po

hi, I was wondering if any of you have trouble with the “remember me” checkbox on https://console.automox.com/? no matter what I do, it will not remember my user name nor password, that check box seems to be doing nothing…I have 4-5 different devices (Mac, pc, iOS) and none of them works…even created a new account and tried, still the same…  thanks! 

Hi, everybody - Chad here. We’ve seen/heard a few issues from users concerning certificates, and it turns out that our LetsEncrypt cert recently expired. From our Engineering team: "As of September 30, 2021, the previous root certificate leveraged by Let’s Encrypt - Automox’s certificate issuer - has expired. For most of our customers and their devices, this will not result in any expected impact to service due to the previously issued ISRG Root X1 root cert that is supported on modern browsers and devices as documented in more detail here: DST Root CA X3 Expiration (September 2021) - Let's Encrypt. In addition to this expiring root certificate, Automox rotates our Console and API certificates every 90 days, and in some cases more frequently, requiring any whitelisting of certificates to be handled accordingly. In order to ensure devices are able to c

Bring radical efficiency to your custom integrations with the all new Automox Software Development Kit (SDK) for Python. Our SDK is built on top of the REST API, so you can accomplish more with fewer lines of code and no library maintenance. Write applications to create device groups in Automox based on your Active Directory Organizational Units or ServiceNow CMDBs. Or, accomplish a more specific use case and update devices in Automox with a CSV file. Whatever your use case, our SDK will empower your teams to create bespoke solutions to your organization’s unique IT challenges.To access and download the SDK, visit our Github pag

I noticed when I am on the software tab and click on the number in the “Updated” column, it pulls up a nifty query on the devices tab. Is there a syntax guide that you could point me to for some of the advanced searches I would like to run? It looks like I could run some of the device searches from the console without having to run API scripts for this information. I couldn’t find anything on this in the KB. Example below.

Months ago i deploy a Policy to install the 20H2 Windows version which was working fine, updated like 95% of the registered devices, then like 1 month ago i changed the Policy to install the 21H1 version, but after the change the policy isn´t doing nothing, none machine has been updated to 21H1 version, the policy is running at the same time, same settings, install optional updates, reboot if is required, only install “Feature update to Windows 10, version 21H1”, i try forcing the policy to run in 1 machine, but nothing happend. I connect with a machine and in the Windows Update panel appear the Feature 21H1 to be installed, but need to be done manually, anybody else with this issue? why the policy isn´t installing the 21H1 automatically as the 20H2? Anybody with similar issue?

I have many users who have not restarted their MacOS device. The BigSur 11.6 patch is held up, waiting for the user to restart. How can I create a Patch Only policy that warns, defers, and then eventually restarts the MacOS devices needing the latest OS update.

I was re-installing the Automox agent on a device where it had been removed, and now I get the error below in the log: Error from performRequest(“install”, body): Post https://api.automox.com/install: dial tcp 44.236.226.107:443: connectex: No connection could be made because the target machine actively refused it. 2021/09/28 10:25:46 main.go:370: ERROR: client.DoInstall(): Post https://api.automox.com/install: dial tcp 44.236.226.107:443: connectex: No connection could be made because the target machine actively refused it. Has anyone else experienced this before?

Greetings, I’m new to a company and this product. We use Automox for our patching. Can we use the product to install MSI packages on servers? Thinking things like Infosec agents etc. I’m currently using cobbled together POSH scripts which work OK but it would be nice to use Automox against an established list of devices. Thanks for any insight. Ron

I have a server 2012 R2 that refuses to show in the Automox console under Devices. I have uninstalled the agent and reinstalled and received an email alert that a new device was added to Automox but I can’t find it anywhere in the console.

Does Automox have actual support personnel that replies to anything?? So far on several open cases the only response is the BOT response that my ticket has been created. This is not an acceptable response.

Update: Thanks to @Douglas_C post, there is a way to obtain the latest version of Acrobat here: https://get.adobe.com/reader/enterprise/ Use it to do a more desirable single required software policy (the first policy listed below) which will update existing Acrobat installs and install it on systems that don’t have it. If you’re only looking to update systems that currently have it installed and not install on systems that don’t have it, use just my second policy with the .msp files. Due to a current issue with Adobe restricting how their software is distributed, Automox is currently only able to support patching Acrobat Reader DC up to version 20.013.20064. I’ve setup the following to be able to keep it updated to the latest version. First, I created a required software policy with th