Using Automox

Hi Team,While updating the third-party application on our client device, the client needs to be informed that, before the application update, an installation notification will be triggered on the device. From this installation notification, the end user should be able to identify which applications are going to be updated on the device.We can customize the installation notification using 125 characters, but how can we use the notification to inform the user that these specific applications are going to be updated?Could you please assist us in configuring this setup?

Hi,Is it possible to automatically run a worklet directly after the Automox agent has been installed on a new device. I want to deploy software using Automox during user enrollment.Thanks,Rob

Automox Console - How do I disable the notification/message blue circle bottom right, that keep doing popup?I couldn’t find anything, I assume there is no setting for it ? Let me know if it’s possible, else I will use an ad blocker.Thanks !

I cant be the only one experiencing this. S1 seems to be causing issues with Windows Servers being consistently patched. We have exclusions in place, but this doesn't seem to help. When we want patches to be fully applied across all servers, we have to disable the S1 agent completely during patching window. This is of course unacceptable. Anytime I contact support all they say is they see the device that had issues when trying to scan and receive this error: {"args":"","response":"[\"255\", They then point me to their documented S1 exclusions. I’ve attached our S1 exclusions that we have in place but they don't seem to help. I even tried changing the amagent execution directory to C:\ProgramData\amagent and that didn't help either.  

Is there an automated way to group devices in Automox? I have over a thousand devices discovered and need to group them but I don’t want to have to search for each device and assign to groups. Is there a way to maybe import a csv file into groups in Automox?

Hi, our network threat detection system is alerting about hundreds of PCs downloading TightVNC.  The URLs used to conduct these downloads look like this (defanged version): hxxps://d1ovafk2iqpmhd[dot]cloudfront[dot]net/automox.com/tightvnc/@v/v2.8.84.windows-amd64.zip Can you please confirm if it is by design for the amagent.exe to download TightVNC even if no admin ever intentionally installed TightVNC on any PCs?  If so, why would this happen if we don’t use TIghtVNC or Automox for remote desktop control?

Hi Ottomaters! I am currently working on a script to obtain the “Needs Attention” devices from the API. The idea is to deliver this to our agents by email / Teams so that we can proactively remediate any update problems before they turn into major problems.  I have two devices in my test group which require attention (This is from the dashboard in console): However, when I try to run the API call:/reports/needs-attention?limit=250&offset=250&o={orgID} It seems that the API returns no results? : { "nonCompliant": { "total": 0, "no_known_cves": 0, "unknown": 0, "none": 0, "low": 0, "medium": 0, "high": 0, "critical": 0, "devices": [] }} I suspect that I am missing something really silly and simple here, but I’ll be honest it’s got me scratching my head a bit! Grateful for any pointers as to where I might be going wrong. Thanks in advance.

Hi all,  Does anyone know if Automox has any recommended Microsoft Defender exclusions please? We use Microsoft Defender for Endpoint and want to ensure we’re not impeding on Automox performance / usability at all please. Further, if anyone knows of any local client firewall rules (other than the 7844 for Cloudflare Tunnels) that might be needed please.  I tried to search but I can’t seem to see anything, so thought I’d best double check. Thanks in advance!  

I am looking for a PS script to get a list of all software installed in our environment and determine which ones Automox can patch and which ones cannot be patched by Automox. Thanks 

Is it possible to assign a role that enable the user to execute policies, but not allow them to add/delete/edit policies? It would also be helpful to assign permissions based on Group membership or some other construct where devices belong to an organisational unit. - For example, delegating controls to a regional IT team, or to a team that supports end-user devices, but should not be able to manage servers.

Our client attempted to uninstall the Automox agent from a Linux machine but encountered multiple issues.Details of Actions Taken: Stopping the Agent Service: ~$ sudo service amagent stop Deregistering the Agent: ~$ sudo /opt/amagent/amagent --deregister Output: no certificate to deregister Attempting to Purge the Agent Package: ~$ sudo apt-get purge amagentOutput: Reading package lists... Done Building dependency tree Reading state information... Done E: The package amagent needs to be reinstalled, but I can't find an archive for it. Reinstallation Attempt: The client tried reinstalling the agent using the following command: curl -sS "https://console.automox.com/downloadInstaller?accesskey=ORGANIZATION-KEY" | sudo bash However, the result indicated that the agent was already installed: Output: /opt/amagent/amagent already installed Dashboard Attempt: The client also attempted to delete the agent directly via the Automox dashboard. Unfortunately, this action failed, as the

I have a question about the policy schedule option, “If a device misses a patch window, patch it the next time the device checks in” We have systems that need to patch at a particular day and time of the week. If this option is selected and for what ever reason, a server misses the installation on the scheduled date and time, can the server patch and reboot, once it checks in and could that be at any time of the day? If it is only during the window, what does Automox consider the “Window” since the schedule only includes, “Months, Weeks, Days” and a scheduled time

HelloHow do you keep linux up to date?I would like to understand what would be the best practice.Do patch policies address Linux OS machines?Or is it necessary to do it via worklet?

We know how important it is to ensure our customers can ask for and receive assistance. This is why we’ve been working behind the scenes to create a new process for submitting a Support ticket. Let’s say you’re in the console, working on something, and run into an issue you can’t solve. All you have to do is click this button in the lower right corner to open the Resource Center.  The Resource Center allows you to search our Help Center, access the Community, join upcoming events, see our latest best practice guides, and (starting today) contact our Support team. Simply click the Contact support button and follow instructions! We hope this improves the process for working with our Support team. 

Overnight we received at least 100 failed update notifications for Google Chrome on our endpoints. The error is pretty vague and we confirmed that on each endpoint that received the error Chrome was not updated to the expected version 131.0.6778.109. What’s even more bizarre, each endpoint that reported this error no longer shows that Chrome is installed, either directly from the Control Panel or within the Automox Console. So now those endpoints won’t get updated at all since Automox isn’t seeing Chrome installed. “Failed to apply patches ("Google Chrome"): Update of google_chrome failed with exit code 1603” I’m looking for any help in figuring out how to remediate this. I’m going to start by trying to redeploy Chrome with other tools, and pausing the original “Keep browsers up-to-date” policy that was enabled during our onboarding into the product.

Situation:We had scheduled a policy, but the client device disconnected two minutes before the scheduled scan.Findings:Upon analyzing the amagent log, we identified intermittent connection failures between the client system and the Automox WebSocket server (wss://api.automox.com/stomp).After a few minutes, the connection was re-established, and the server sent an install update notification to the client device.Question:What could be the potential causes of these connection failures between the client system and the Automox WebSocket server? What steps can we take to resolve this issue?

How can I manually test Automox notifications on a Windows device to ensure they are working properly?

We have set up user notifications in the format shown below, but end users are not receiving reboot notifications after completing Windows updates. Could you please help with this? 

Hi Guys,I have previously mentioned this to support although I am not too sure if there is a procedure for requesting additional features for the Automox agent? thus thought it would be useful to post in the community to try and reach out the toe correct team\department.It would be really useful if the Automox agent was able to integrate with windows from a native OS reboot perspective. One thing I am seeing allot  is that users are postponing the reboot notifications generated by Automox and then restarting there device outside of Automox. Although patches are still being applied the Automox dashboard does not appear to be aware of this reboot and the agent continues to report  back to the dashboard that a reboot is required.If the reboot is initiated from the Automox reboot notification the dashboard updates as expected when the r the host reboots although it would be useful if there was some integration to reboots that are initiated outside of the Automox.

Why Automox is not showing us the latest patches that need to be installed. If the patches are showing up on the MS Defender report we should see them in Automox as well

What will happen if you create the 2 same policies with different schedules?

Hi all, I’m currently trying to create a Worklet for TeamViewer Host to silently install on new builds. I have created an .msi file to attach to the Worklet but currently I don’t know how to bypass the installation so that it actually installs. Ideally, we would be able to silently install and grant easy access to our admin account (which is already associated within the msi install) I was wondering if anyone else has tried creating this Worklet or has any insight.

Why does the Automox agent fail to connect when no one is logged in?

We have scheduled the Apply All Patches policy for one of the Windows devices. During the patching process, an end user reported that Automox attempted to install OneDrive updates, which Microsoft Defender flagged and blocked as an unusual update operation. Could you please assist with this issue