Using Automox

Automox does not patch firmware updates. If we have Automatic updates turned off on a workstation or surface how do we get the firmware patched?

I have a couple of reporting questions: Do we have a method to see if a device has opted to defer an update or reboot? I receive weekly summary updated, but that report doesn’t have the ability to drill down. Is there a way to see this same type of information (outstanding patches by groups and time they have been available)? Is there a way to view the history of patches/updates to include dates when applied? Thank you, Brad Brad

As an admin, you can now enforce email 2FA for your entire organization. Please navigate to Settings > Security to check it out! To manipulate individual users, please go to User Accounts, select the user(s) and click on the Actions drop down button. Drop a line with any questions. Have a great weekend.

Great news for folks deploying the AX agent in bulk or individually. We will be enabling users to identify a target group with a new group parameter in the MSI executable via command line. Groups will still have to be set-up ahead of time in the console, but this should help save time as you bulk add new hosts to your organizations and get them on policy runs as quickly as possible. Please be on the look-out for agent command line guide updates and other helpful tips for using this parameter.  We’re targeting early December for a release and will post in Announcements when it is live.  CC: @ncolyer 

Is there a way to provide notices for patches/updates without a deferral option as well as providing notices and deferral options for reboots. Is there a way to provide notices when applications will stop/restart without deferral options? Thank you, Brad

https://support.automox.com/help/week-in-review-release-notes-for-week-ending-01152021

Hi guys, Did Automox change their signing cert recently? We manage through AppLocker and the new cert blocked the agent notifier exe which auto rebooted a fair amount of devices without notification 😛

Good afternoon from Australia! We’re currently rolling out Automox and are setting up our policies. With regards to patching Office 365 for Enterprise on Windows, does this patch based on the update channel the machine is running on? Or does it only adhere to a specific channel (e.g. everyone gets moved over and patched to the Current Channel). Most of our machines are on the Semi Annual Channel at the moment, with mine and a couple of other testing machines using the Beta channel. Ideally, we’d like to keep this structure set up as it is, or at least move the machines on the Semi Annual Channel to whatever channel is needed but keep the machines that are on the Beta channel. Thanks! (also sorry I submitted half a post, Fat Fingers Douglas strikes again!)

Hi, I have a meeting scheduled with automox sales but I’d just like to ask a quick question here. Does the off premises solution run entirely on the web? We’re looking for a solution that doesn’t require us to open any firewall rules/ports at all. Other products I’ve looked at have an off premisis solution but it’s just hosted in the cloud on a vpn attached to the main network rather than being an independent web based solution. Many thanks.

theregister.com That's it. It's over. It's really over. From today, Adobe Flash Player no... Post-Flashpocalypse, we stumble outside, hoping no one ever creates software as insecure as that ever again Let’s get the party started!

https://support.automox.com/help/week-in-review-release-notes-for-week-ending-01082021 Bug Fixes Fixed a bug with the Activity Log Report that could sometimes limit results shown (1/8) …and we’re back! Welcome to 2021! Our staff enjoyed a nice (if irregular) holiday season and break, they’re working on lots of internal enhancements and updates, and they’re excited about getting some important and meaningful features out to everyone.

I’ve looked at the example worklets. I’ve looked at the Chrome worklet I have for installing Chrome. I’ve looked at other powershell code. Nothing seems to work for me. Every time I try to create a worklet it fails. Is there a simple worklet example for Windows I can look at? Here’s what I’m trying to do check to see if the app is installed If it isn’t installed, Install the app If the app is installed, mark the policy as compliant Thanks!

Hi Team, When I’m in Devices (https://console.automox.com/devices) I want to be able to open a device in a new tab. Currently I have to duplicate the tab I have open, and then select the device I want to view. It would be really helpful if I could right click and open a new tab on the device. Thank you, Chris.

Is there any way to uniquely rename an endpoint without having to build a one-off worklet or use an external api call in a generic worklet? If you were able to execute arbitrary commands this would be easy enough, but the best option I see in this case would be if worklets were able to read their associated display name in the console (or a tag or custom field if these are available) to then set as the hostname. That way you could use the Automox api to change the console display name of a device, and then trigger a generic worklet on specific devices to rename themselves according to the console parameter. Any thoughts on how this sort of functionality could be accomplished with the current feature set?

Automox sent all of us AXers (employees) a very nice holiday gift basket. One of the best surprises in it were some Automox playing cards. This is the very first hand that I got dealt playing poker (totally honest, I swear), so you know the cards are lucky: IMG_49294032×3024 2.77 MB This is a limited run item just for employees, but if enough customer holler for them then we’ll see…

Hi, has anyone had any issues with the API from today? I had a script that pulled down all machines and was working fine for the last few weeks however stopped this morning with an ‘Invoke-WebRequest : The remote server returned an error: (500) Internal Server Error’. Script is (XXXX added for privacy): $apiKey = "XXXXX" $orgID = "XXXXX" $expDir = 'XXXXX' ############################################################################################################# #Pull server detail by group from API and export as csv to defined directory $uri = "https://console.automox.com/api/servers?o=$orgID&api_key=$apiKey&l=1100" (Invoke-WebRequest -Method -Uri $uri).Content | ConvertFrom-Json | Select-Object results -ExpandProperty results| Select-Object name, serial_number | Export-Csv -Path $expDir\AutomoxAPI_Export.csv -NoTypeInformation -Force If I remove the ‘&l=1100’ from the uri variable it works without issue, however only pulls 500 devices. This only started happening from

In the coming weeks, we will be releasing updates to the Automox API and introducing API limits to ensure optimum platform performance for our customers. We will begin to roll out changes to our endpoints to begin to support and eventually enforce limits on the number of results returned per request. These endpoints will have a limit parameter available, and this parameter will have both a default value and a maximum limit. The limit argument will allow values between 1-500, with a default of 500, and a max of 500. Our endpoint responses do not contain pagination information so API users will have to check to see if there are additional pages. For example, if 499 results are returned when 500 results are requested, there is no second page. If 500 results are returned, a second request will be needed to check for and fetch additional results.  These changes to the endpoints will be documented at https://developer.automox.com/  We will be rolling out these limit arguments for our API end

AX engineers have finished up some work to improve the performance of the policy editor. We had some reports of slow response time a few weeks back. Let us know if you are still encountering issues.

Hello Automox Alive Community! I am pleased to announce that Automox has passed the audit requirements of the American Institute of Certified Public Accountants’ (AICPA) achieving SOC 2 Type 2 (System and Organization Control 2 Type 2) status. SOC 2 Type 2 is a cloud service provider benchmark attesting to a provider’s overall cybersecurity hygiene. The process is voluntary, consisting of a capability audit aligned to Trust Service Principle control categories. These categories are of the latest industry standards covering Privacy, Security, Availability, Process Integrity, and Confidentiality as measured and audited over a period of 9 to 12 months on average. Please see the official AICPA SOC for Service Organizations page to learn more about SOC 2 Type 2. Please see our blog post, press release, or review our Security Practices for additional detail on how Automox defines, aligns, and protects your data and privacy.

Zendesk ServiceNow ITSM ServiceDesk Plus Spiceworks Freshdesk HappyFox Zoho Desk Freshservice Agiloft Service Desk Jira Service Desk SolarWinds Service Desk Sysaid TeamSupport Salesforce Service Cloud ConnectWise Manage Kustomer Kayako Track-It Kace BMC Remedy 0 voters

We are actively researching improvements to patch & reboot notification and deferral functionality. Specifically, we are considering the following options to provide administrators greater control over the user reboot deferral experience. Configuration option to automatically consume deferral option when available Allow admin to extend 15 min notification window to 2 hours We would love feedback if this same functionality would be useful for patch notifications and deferrals. Does it make sense to have the same configurability options to maintain parity between the two notification types? Would one set of options set at the policy level work for both patch and reboot notifications in your use case? Please consider and select the option below that best reflects your preference. Any additional comments on why would be appreciated. Reboot only - new configurations only apply to reboot, no new configuration options for patch notifications Set a policy level - same notification wi

https://support.automox.com/help/week-in-review-release-notes-for-week-ending-12112020