Using Automox

We’re excited to announce that Automox now supports patching for the following third-party applications:  X-Mouse Button Control  Windows And, the following titles are in progress and coming soon*:  DataGrip by JetBrains Windows/macOS DinoCapture 2.0 Windows  We’ll be back in the new year with our next round of updates. 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.

Hey all, Ran into a very strange situation where I have a windows endpoint that is attempting to patch an older version of Google Chrome and all my activity logs say that chrome is patching successfully, however when i look at the device record, Automox still tells me the older version of Chrome is installed (version 66 strangely enough) and that the app hasn’t patched successfully. when I RDP’d over to the PC, i can see that the latest version of Chrome is installed and there are no older versions of chrome that i can see. As you can imagine it is a buzz conversation amongst our IT SecOps team because Chrome 66 is of course absurdly old. I’m not exactly sure where else i can look to find where automox is detecting this older version of chrome that doesnt seem to be installed. Any suggestions or ideas would be appreciated.

I am onboarding my devices having come from another product. I am having issues correctly onboarding my 4 DNS servers (ubuntu) and my webserver (ubuntu)  I onboarded my webserver first, it registered and initially displayed the correct info in the System Details. I proceeded to onboard DNS01 and I received the Slack message it hit my account. When I went to device details DNS01 is not in the list and my webserver is now displaying the DNS01 fqdm in system details. Any ideas to either correct this within the GUI or manually edit the details on the endpoint?

The momentum of additional third-parties being added to Automox’s support list is nothing short of outstanding! We wanted to extend of big thanks to our engineers for their hard work as well as provide the latest third-party applications that they have recently added to our list, including:  DbVisualizer Windows/macOS Diagrams.net by JGraph Ltd macOS Evernote Windows/macOS Git Extensions Windows RingCentral Windows/macOS  And, the following titles are in progress and coming soon*: DataGrip by JetBrains Windows/macOS DinoCapture 2.0 Windows Go Windows Go Connect Windows/macOS X-Mouse Button Control (XMBC) 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

Hi,While creating Patch All Except Policy for Linux. Which Patches do we need to include to be installed?What is best recommendation for patching Linux?

Hi team,In our environment, SSO is Enabled for the Zone and during failover of SSO. Can we use Email-ID and Password as an alternate method to login to the Automox Console.Thanks,Shoaib

We’re excited to announce that Automox now supports patching for the following third-party applications:  Autodesk Desktop Connector Windows Artweaver Plus 7 Windows Bluebeam Optical Character Recognition 20 (OCR) Windows Bluebeam Revu 20 Windows Bytello Share Windows/macOS DYMO Label macOS Plantronics Poly Lens App Windows/macOS  And, the following titles are in progress and coming soon*:  DbVisualizer Windows/macOS Diagrams.net by JGraph Ltd Windows/macOS Evernote Windows/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. 

Hi Team,As per the below article, Automox supports six role-based access controls (RBAC). But in the same doc we have one more role named as Helpdesk operator, and it has privilege to take Remote session as well. By default, does this role only used by Automox Support Team? or it can be assigned this role to Zone users?Ref: Roles and Permissions – Automox Thanks,Shoaib

Hi Team,While creating Groups we have a session called OS Patch Management. Where under that we have settings only for Windows and macOS nodes, so we need to know for Linux which is the recommended settings to be used?Can you please confirm if these settings applicable for Linux OS? if yes, what are the recommended settings to be used?If this Session is not applicable, then what settings do we need to be set?Ref: OS Patch Management Settings for Groups – AutomoxThanks,Shoaib

Happy Almost Thanksgiving! We wanted to share the latest third-party updates before the short week wraps-up. We are excited to share that the following titles are in progress and coming soon*: Autodesk Desktop Connector Windows Artweaver Plus 7 Windows Bytello Share Windows/macOS ClaroRead SE by Texthelp Windows/macOS DbVisualizer Windows/macOS Diagrams.net by JGraph Ltd Windows/macOS DYMO Label Windows/macOS Evernote Windows/macOS Plantronics Poly Lens App Windows/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 

Here at Automox, we are constantly striving to improve our processes as well as the experience of your users. With that in mind, we’re delighted to share that for your macOS (Intel) users, their patch experience is now more seamless than ever! Once a user defers their patch and reboot notification from Automox, they’ll continue to receive timely alerts to remind them of the necessary patch based on your policy configuration. This update ensures that your patching is conducted across all of your designated endpoints without any of the hiccups that could be created by a user deferral. The end result is a user experience without unexpected reboots and lost productivity while keeping patching a priority and reducing your overall risk exposure. With these continual improvements in the Automox console we’ll help elevate your IT processes to a business enabler vs. a barrier! 

This Thanksgiving, AXU raises a fork to IT pros who devour knowledge like it's the last slice of pumpkin pie. Fresh on the menu: Secrets Management and Worklets for Data Collection and Auditing – because we believe in stuffing brains, not just turkeys! 

Happy Friday everyone!Automox now supports patching the following third-party applications: Software Name Operating System Jabber VDI Client (macOS, Windows) Visual Studio Community 2022 (Windows) Visual Studio Community 2019 (Windows) ProtonVPN (macOS, Windows) VNC Viewer (macOS, Windows)  The following titles are in progress and coming soon*:Software Name Operating System AUTODESK Desktop Connector (Windows) DYMO Label (macOS, Windows) Poly Lens App (macOS, 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.

For the past 2 months, our console fails to be able to report on severs that have high or critical severity. We are seeing an issue again when we try to filter devices by Severity for Critical or High patches, where it fails to load any devices.    We have a major patch window coming up on Saturday, and not having this available will mean that we need to manually verify patching on the majority of our servers, which is not acceptable. Is anyone else seeing this or is this local to our Automox console?

Hello, We are currently using Automox to manage our linux device. Our user have to register frequently from the intune portal so that their device show in intune.I would like to know if it is possible to register automatically from automox to intune without any action from our user? Best regards

Hi Team,We have disable Domain Firewall and we have Private and Public FW enabled on End nodes. In this case, do I need to allow below URLs on my all-End node’s Local firewall? to fetch updates from Microsoft. Windows OS - We might choose to apply a rule to permit HTTP RANGE requests.[RS1]    •             *.download.windowsupdate.com •             *.dl.delivery.mp.microsoft.com •             *.delivery.mp.microsoft.com Devices can reach necessary Windows Update endpoints through the firewall TLS 1.2  *.prod.do.dsp.mp.microsoft.com HTTP      emdl.ws.microsoft.com HTTP      *.dl.delivery.mp.microsoft.com HTTP      *.windowsupdate.com HTTPS   *.delivery.mp.microsoft.com TLS 1.2  *.update.microsoft.com TLS 1.2  tsfe.trafficshaping.dsp.mp.microsoft.com  

As we observe Veterans Day, let’s take a moment to thank those who served for our freedom, and their families among us, for their incredible sacrifices. Thank you!And on to our weekly third-party updates! We’re excited to announce that Automox now supports patching for the following third-party applications:  Bluebeam Optical Character Recognition (OCR) Windows Bluebeam Revu Windows Ekahau AI Pro Windows/macOS Epson Easy Interactive Tools Windows/macOS Logitech SetPoint Windows Wondershare Creative Center Windows  And, the following titles are in progress and coming soon*: Autodesk Desktop Connector Windows Cisco JVDI Client Windows/macOS Cjwdev AD Photo Edit Free Edition, Bulk Edition Trial Windows DYMO Label Windows/macOS Microsoft Visual Studio Community 2022, 2019  Windows Plantronics Poly Lens App Windows/ma

I’m trying to install Microsoft PowerBI but I am running into a wall. I am doing it through the “Required Software” option for installing programs. I am using the following powershell to install it:msiexec.exe /i "\\xxxxx\xxxxxx\Install Files\Power BI Desktop\PBIDesktopRS_x64.msi" /quiet ACCEPT_EULA=1 This exact powershell line works outside of automox and I can’t understand why it’s not working within the console. For added confusion, Automox say that it was successfully installed on the target computer but when I look at the programs installed on it that is not the case. Any direction would be greatly appreciated!

We’re excited to announce that Automox now supports patching for the following third-party applications:  GoTo Connect Windows/macOS Microsoft Azure CLI Windows Tracker PDF-XChange Editor Windows Wondershare UniConverter 13 Windows/macOS  And, the following titles are in progress and coming soon*:  Autodesk Desktop Connector Windows Bluebeam Optical Character Recognition Windows Bluebeam Revu Windows DYMO Label Windows/macOS Ekahau AI Pro Windows/macOS Epson Easy Interactive Tools Windows/macOS Logitech SetPoint Windows Wondershare Creative Center 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 work

Y’all may have seen the teaser published a few weeks ago (don’t forget to check it out). Well, the time has come. We are proud to announce the Worklet Development Kit is now live! Start using today and check out what’s available by visiting our documentation! Customers with a subscription that allows use of Custom Worklet and Required Software policies have access right now! What is the Worklet Development Kit?The Worklet Development Kit (WDK) is a ready-to-use toolset that simplifies worklet creation by offering pre-made functions and commands that make building, scaling, and executing worklets easier, faster, and aligned with Automox worklet development best practice. What do I need to do to get started?All you need is a supporting plan for Required Software and Custom Worklet policies then you are all set. That’s it. What is supported today?Windows (Powershell) is the first to get released, but we will quickly follow up with macOS and Linux (bash) support in the coming weeks! Now fo

For the past 2 months, our console fails to be able to report on severs that have high or critical severity. We are seeing an issue again when we try to filter devices by Severity for Critical or High patches, where it fails to load any devices.    We have a major patch window coming up on Saturday, and not having this available will mean that we need to manually verify patching on the majority of our servers, which is not acceptable. Is anyone else seeing this or is this local to our Automox console?

Hi Ottomators! Do you want to learn how to level up your Worklet game with FixNow? Our new course, FixNow for Worklets, walks you through everything you need to know in under five minutes!  AXU also has a newly updated course, Patch Policy Management. This is a 15-minute course that digs into the features and functionalities of Automox policies. Let us know if you have any other course requests!

“Great thoughts speak only to the thoughtful mind, but great actions speak to all mankind.”- Theodore Roosevelt (whose birthday is today, 10/27) This is a great theme to segue into Automox’s third-party support! With our industry-leading third-party support, you have the ability to take quick, automated action across your endpoints and lower your organization’s overall risk (instead of toiling with other solutions that often require organizing, categorizing, and prioritizing vulnerability data). We’re excited to announce that Automox now supports patching for the following third-party applications:  Altova MapForce Professional 2023, 2021 R2, 2020, 2020 R2 Windows Double Commander macOS Wondershare UniConverter 14 Windows/macOS  And, the following titles are in progress and coming soon*:  Autodesk Desktop Connector Windows Bluebeam OCR Windows Bluebeam Revu Windows DYMO Label Windows/ma

I understand Automox is meant to be streamlined/simplistic; however, the scheduling system, in my opinion, is too simple and should offer more granularity.  An example being, if I want to exclude patching the entire week of Patch Tuesday - this is not feasible with the current calendar because it goes off the date of the week, not the day of the week.  So if I excluded week 2, that could start on a Monday, a Thursday, etc.I understand we can use advanced patch policies to use offsets for patch age, but that makes scheduling ironically overly complicated. A seemingly simple fix would be to add optional CRON expressions.  I see many platforms doing this, allow basic calendaring with a checkbox to utilize CRON if you want to implement a more advanced schedule.

We are using a patch all except policy for all of our desktops this runs daily at 10:30am.  It has been working great the first month we were using Automox but now it seems to be installing the same update daily with no errors.  It wouldn’t be such a problem however it causes a reboot prompt everyday now at 10:30.  I’ve looked through the reports and I am not seeing any errors.  Even for those who have rebooted it still prompts a reboot daily. Any thoughts or ideas?