Using Automox

Good day, Is it possible to have an automox agent send an email immediately upon failed patching of a server?

So what’cha want?Happy 2022, y’all! Even though we’ve barely stumbled into the start of 2020: Part III, I think we’re probably all ready for a cup of tea and a nap. But first, I have a question: What AX features are highest on your wishlist for 2022? Here, I’ll get us started: as an Admin, I’d like to see some remote device management in the AX console. (Sorry, but none of you can use that one now! )_______________________________________________________________________________ While we look to 2022, let’s also look back at 2021 - the features AX released last year came fast and furious at times, so we’ll do a quick recap. Give me just a second..so many new things..Recapping…..Okay, done! Here’s a quick, non-chronological rundown (organized by functionality), with some links to additional resources. If you have any questions about any of them, let us know in the comments. Automation Flexible Device & Package Targeting ​​​​​​Gives admins the ability to target specific devices and/o

I think I have found an error in the PowerShell request sample from the documentation for Automox’s "List All Devices" API call.  The request sample has:$url = "https://console.automox.com/api/servers?o=:orgID&page=0&limit=500"This did not run until I changed :orgID to $orgID in order to reference my Organization ID.Actually, I now see that the sample does not include a definition of $orgID either.  So, altogether IMO the sample should read,$apiKey = 'your_automox_api_key'$orgID = ‘your organization ID’$headers = @{ "Authorization" = "Bearer $apiKey" }$url = "https://console.automox.com/api/servers?o=$orgID&page=0&limit=500"$response = (Invoke-WebRequest -Method Get -Uri $url -Headers $headers).ContentI raise this issue because the PowerShell error resulting from the sample isn’t very specific.  Due to that, and because I am only beginning to use this API, it took me quite awhile to discover that the sample was incorrect as opposed to my having made a mistake.  Therefor

This link from the documentation redirects me to the home page. Is the playbook still available for download? https://go.automox.com/hubfs/Technical%20Docs/get-automox.yml

Hey Automox people, I got an email on 11/12 talking about RBAC rollout, with zones and finer grain controls over user access. Any idea when this functionality is actually being deployed? This was one of our bigger asks from AX and we’re excited to use it!

How often Automox scans devices and can the scanning time be scheduled? 

In addition to patching the device operating system, Automox also natively patches an additional catalog of third-party software. You can find a list of our supported third-party software here: https://support.automox.com/help/third-party-patching-softwareWe’re now excited to introduce to you a new category in the community, our Software Patching Catalog Updates! With this category, we’ll notify you of new supported third-party software as it is available. Plus, you can subscribe to email notifications in this category using the Subscribe button on the top right of the category page.Please let us know if you have any questions!

Hello, Automox Community!Vania here 👋 , Product Manager at Automox.I’m excited to announce that our new user role, Patch Operator, is now available!We’ve been hearing from users that they’d like a user role that does not have the ability to create or modify Worklets. For this reason, we’ve created a new role that still has full permissions for patch policies, but does not have “create” or “modify” permissions for Worklet and Required Software Policies. The Patch Operator role, however, can still run Worklet or Required Software Policies.With the addition of this role, we also changed the name of the “Patch Administrator” role to “Zone Operator” in order to better align with this role’s permissions. Here are some screenshots of the new role:Assign a user to multiple zones as a Patch OperatorAdd a user to a zone as a Patch OperatorFor additional information, check out our user documentation.Let us know what you think of the new role in the comments below!Vania

Hello,So the requirements on what to allow outbound through our firewall for Windows agents (for WindowsUpdate) are very clear.  But what do we need to allow for Linux agents?  Or does all of that come via Automox’s cloud CDN?Cheers,Mark.

I’ve found some informative threads on blocking the Windows 11 upgrade with Automox policy but I have devices I’d like to push Windows 11 to and I’ve been unable to use a policy or worklet for this.  I have not found a patch or required software method to push out the Win 11 upgrade and have had no success running the upgrade via a worklet. Is there any type of best practice for the Windows 11 upgrade?  It would greatly benefit our efficiency if I can use Automox for this.

With Covid we have more and more remote users and I’ve been having to rely on more and more remote tools and automation. Just curious if anyone has used ConnectWise and had any problems and/or did you use Automox to roll it out?

We’re very excited to announce the release of a newly developed Automox application that will enable users to easily interact with CrowdStrike’s Real Time Responder APIs to deploy Automox Agents through their existing CrowdStrike footprint. Additionally, you’ll be able to set up a recurring schedule to ensure that Automox Agents are always up-to-date and present across your CrowdStrike footprint. Please find the downloadable files and step-by-step instructions here: Automox Agent Deployer | Automox Knowledge Base Let us know if you have any questions or concerns. CC: @tyler.schmidtke

I have deleted the software distribution folder content, check the registry, but still not finding anything that points to a solution regarding this error. 

Agent 38 ReleaseWe are very excited to announce the GA of Agent 38! Agent 38 is available in the console as of this publication for download. Phased upgrades will begin Wednesday, April 21st.This release resolves an issue affecting Agent 37 of high CPU utilization during command execution across all devices. Operating System Support:This release is for all supported Windows, Mac and Linux operating systems. Known Issue:High CPU utilization sporadically affecting macOS devices has been identified as a result of an edge case in our multi-threading logic. A fix for this issue has been identified and will be released in Agent 39.Workaround: If encountered, restarting the Automox agent will restore normal CPU usage Status: Agent 39 will be released in the next 4–6 weeks

Hello, we are looking at moving away from SCCM and use Automox for our updates. What is best practice to configure a policy that will update severe and high updates once every 30 days? I have Install Optional and Recommended Windows Updates enabled, package targeting is Critical and High Device Targeting with Attribute = OS, Condition = In and Value = Windows. I do not have a schedule assigned as I need to test this manually first.  User Notifications are set as:Install Notifications are disabledReboot Notifications are enabled Enable deferrals, enable automatic deferrals enabled, with hourly deferrals set as 1 hour, 2 hours, and 3 hours. Max deferrals is set as 3. 

If this doesn’t belong in the “Labs” portion, I apologize in advance. I’m migrating devices from one Zone to new Zones.  I think I’ve got that process mostly down, but am now looking for the best way to use the API to read in a csv file with the new devices and join them to a new group in the new Zone. Do we have something like that, that I can use?

Hi All,  Is there a way to make a policy Worklet (already setup) for Ipconfig /flushdns run constantly on like a 5 minute loop for 1000 PC’s. It currently looks like this below. I am moving a Home drive Host VM server to Azure Cloud which will have an IP change and we will change DNS record, and want to minimize downtime.Evaluation CodeExit 1 Remedial CodeIpconfig /flushdns

Does anyone have a worklet on enabling FileVault and collecting the recovery key?

To wrap up all of our most recent releases, we also now have automated third-party patching support for Breevy on Windows! You can keep up with our ongoing list of third-party support through our knowledge base page here.

We’re excited to bring you yet another addition to our third-party patching support catalog - Parallels Toolbox for Windows! As always, you can find a full list of supported third-party applications on our knowledge base here.

Automox now supports automated patching for Sourcetree on Mac! You can find this and a list of the other supported third-party software here.

Automox third-party patching support has been added for VMware Horizon Client 7 & 8, for Windows and Linux.You can find a list of all our third-party support here.

I’m attempting to script a LAPS installation which requires the creation of a local account. When I test the powershell script on my local machine everything works great. When I tried to run it through Automox I get an error.Get-LocalGroupMember : The term 'Get-LocalGroupMember' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.At C:\ProgramData\amagent\execDir691746467\execcmd943937958.ps1:3 char:15+ $isingorup = (Get-LocalGroupMember $group).Name -Contains $user+ ~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (Get-LocalGroupMember:String) [] , CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundExceptionNew-LocalUser : The term 'New-LocalUser' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verif

Is there an integration coming for Jira?