Using Automox

Many Automox customers have asked us for a flexible method to manage and execute policies on a subset of endpoints based on criteria that match their IT operational workflows. The result? Flexible device targeting, which gives you the ability to perform actions on endpoints based on device and user-defined attributes – without being locked in to rigid dependencies. What is Flexible Device Targeting? Flexible Device Targeting allows Automox users to add filters to policies so that the chosen policies will only run on devices that match those device filters. Plus, you can add up to 10 filters per policy to give you an amazing degree of precision to manage your endpoints. Current device filters include: Hostname Device Tag Operating System OS Version IP Address Active Directory Organizational Unit Here is how to access Flexible Device Targeting. Access “Manage” from the

i am new to automox. took it over from someone who left. trying to figure out how to see if a certain patch has been applied to all window machines. i can see how to check each machine to see what has been apllied but i need to see if a particular patch has been applied across ALL machines

I see there is Package Targeting by severity. Is there a way to target packages that do not require restart? I’d like to create a policy that patches without notification, if a restart is not required. For patches that do require a restart, I’d like a policy with notifications and deferrals.

This script will set the tag(s) for all computers in a group. It will override any tags that are currently assigned to any of those systems. There are some areas in the code you’ll need to update to get the script to function: $orgID = 'YOUR_ORG_ID' - put your Org ID, which can be found by looking at the URL of your console and selecting the value after the “?o=”: https://console.automox.com/dashboard?o=999999 . In this example URL the Org ID is the 999999 portion. $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. $grpID = 'GROUP_ID_OF_SYSTEMS_TO_TAG' - put your Group ID of the systems you want to set the tags on. It can be found by viewing the group page that lists devi

Other RMM software supports a ton of titles, Automox supports only a few, will you support more in the near future and have ability to filter ‘third party titles’ when selecting this in a policy as it seems currently you either need to create individual policies to patch certain third party titles or create a worklet

It would be great if Automox displayed whether Bitlocker/Filevault was enabled on the device page

It would be great to remotely manage machines in terms of processes and services, I know, it can be done via a Worklet but ability to kill and restart services from within a device page is quicker and more flexible than a Worklet

I was just looking at Ninja RMM and it offers ability to view machines not rebooted after X days. It would be great to have such ability in Automox so I know patches have been applied and catch any machines that haven’t been restarted.

Hi Guys, i would like to know if there are any script that can give a software report by PC, with an specific software, Microsoft Office for example, to know which version is installed in every PC in the console. Aprecciate any help Regards

Hey All, We’re really excited to launch our brand new Developer Portal available here: https://developer.automox.com/ The Developer Portal contains our most up-to-date public API documentation, resources for programmatic use of the Automox platform and the ability to execute authenticated requests against the APIs directly in this user interface. Use this resource to see what’s new with our APIs and to review any upcoming major changes, as well. We look forward to continuing our investment in Automox APIs to further enable customers to bake Automox directly into their custom business logic. Next up are things like client libraries and SDKs to help folks get moving even faster! We’d love to hear your feedback on the Developer Portal and what other things you look forward to seeing from the Automox team when it comes to our APIs.

It would be great if it was possible to add the ability to clone a Policy so that we don’t need to create one from scratch where we would like to use a similar criteria

It would be great to add the filter to report by OS in the Activity Log, it would save me from having to check our naming convention/opening the device to check OS/scrolling

It seems like a basic thing to have but being able to add multiple software titles to an Advanced Policy where I can add more than 1 title e.g Zoom 64-bit and Zoom 32-bit.

I noticed the naming convention for Windows 10 versions are their version numbers, instead of 1909, 21H1, etc which would be easier to understand. I always end up needing to google what version 10.0.19041 refers to

Apple no longer refers to their latest OS (11) as OS X, would be nice to see this amended for those versions

I noticed it is not possible to remove the Recently added tag which is added by default, which is not a major issue.

It would be nice to be able to remove a client through the Device page. It is only possible through the Devices page where you need to tick the device and remove it, but a button on the Device page would be nice too.

Does anyone know of a method to Delete or Manage (Edit, Modify) tags (aside from creating new)? I can’t find one in the console.

August 5th at 2pm ET: Join us for our monthly Q&A and ask our industry experts anything and everything about IT operations and the Automox platform. Register here to submit your questions! Some topics we can cover: How to proactively reduce the risk of cyberattacks Best practices for endpoint management and increasing the velocity of endpoint hardening The best way to gain visibility and control across your remote or hybrid workforce Technical questions around patch deployment Tips and tricks to get the most out of the Automox platform Submit your questions in advance or listen in as we answer questions from your peers about today’s most pressing topics. Register Now! See you there!

On the primary device screen All tags are sorted “as added” meaning each device receives the tags visually in the order they were applied. This leads to devices with the same tag sets appearing visually disorganized in the device page. It would be helpful if all tags in the device page received an alpha sort prior to display. This would allow someone visually looking at it to determine devices that are “like tagged”. The order in which a tag is applied is low value data compared to what tags are applied when doing quick visual checks.

https://support.automox.com/help/release-notes-for-week-ending-07302021

Just wondering with the new function with targeting based on asset info, would it be possible to assign tags in bulk? For instance, making a location tag would be more logical now together with a policy that is targeting a specific set of machines. I would like to tag machines for instance based on a preset in the hostname, but currently we must edit every device manually. Anyone found a workable solution to do this more efficiently because tagging cannot be done on initial installation of an agent.

When creating reports it would be really nice to have our custom computer names included instead of only the actual computer names, it would make it easier for the customer to recognize their devices. Thanks

I’m carrying out our monthly patching rounds today. As part of our process, we don’t auto-reboot after patching, we trigger it manually. However, it looks like devices aren’t restarting when I trigger a restart from the Automox console. Has anyone else seen this before? I’m purely looking at Windows server just now.

How to get a silent install package to execute in automox. I’ve tried the following with no success so far. Looking to install a executable silently. .\TigerConnect-Setup.exe /S also, Start-Process -Wait -FilePath “TigerConnect-Setup.exe” -ArgumentList ‘/S’ -passthru