Using Automox

I can see the option to install all updates greater than Low Severity.Is there a way to scan for “Optional Updates” like you see in the PC’s Windows Updates section?

We’re a Dell shop and have all Dell Workstation and Laptops.I know there’s a way through the Dell utility to update the bios when updates become available.Is there a way through Automox to scan for available Bios updates and remotely install them for everyone?

Good morning!I just wanted to ask if anyone has had experience using Automox in an environment that has Deep Freeze enabled on some computers. I noticed Deep Freeze will keep the Windows Update service and BITS in a “Disabled” state throughout the day while the computer is frozen, but is supposed to turn it back on during the thaw periods overnight. I’m wondering if the Windows Update and BITS services being shut down all day could be what is preventing these systems from updating correctly, even though the services get turned back on overnight. This seems to happen even if Deep Freeze is told to completely avoid doing anything with Windows Updates. Thanks!

Hi Automox community, I’m investigating ways in which we might improve our patching and remediation. We currently have Tenable VM, which is ok but doesn’t easily integrate with Automox in my experience as I have to import/export csv files. My cloud team are trying out Datadog, which they are really keen on, but does anyone here use it and have you been able to integrate it with Automox?I know Lansweeper and Rapid 7 integrate with Automox, but they aren’t on my cloud teams radar at the moment. Does anyone use either of these solutions? How do you find them?If we can’t find a product that easily integrates with Automox, then maybe we can build something. We’d like some way to extract the vulnerabilities from whatever scanning solution we have, stick that data in a database so we can exclude things, then use the Automox API to target devices that require that particular patch. Has anyone here build anything like this?Thanks

I have noticed that if a Windows endpoint unexpectedly reboots or there is a network disruption while processing a worklet or worklets, the Console will lose the ability to communicate to the endpoint for around 24 hours. That's how long it takes for the back end console maintenance to run and reset things. Even removing the device from the console and reinstalling the agent has no effect. The device is still stuck on stupid in the console. We would love to have a feature to reset the communication immediately so we can continue to work on systems without having to tell users they now have to wait until tomorrow for what they need. Even if its an api feature, that would be fine. Is this causing anyone else headaches? We use worklets to push software to endpoints and are in there daily doing that. I don't know that this would bother customers that are just using Automox for Windows updates. If others are having problems though, maybe Automox can help us out. I am tired of opening ticket

Hi Team,I am having issue while trying to remote connect to user's computer. When I click on Remote Control from Device Page, it starts initializing and ask prompt to user. User accepted the prompt, and it connected but within a second, it just disconnected.Then I click on Reconnect button on top and it establish connection and get sudden message says - “Unauthorized to start a Remote-Control Session”I did try to scan computer and also restart computer manually but still having a same issue while attempting to remote control.I read few Automox article and found below information. Authorization failed Org does not have an Account ID (That means the organization was not migrated to Global Zone Management) Your role does not have permission to use Remote Control JWT minting service might be down However, I am still not able to understand the cause. I have also checkFirewall link: https://help.automox.com/hc/en-us/articles/5352219184020-Agent-Firewall-Allowlisting-RulesRemote control w

Hi all,Last night we had a system reboot unexpectedly.  The policy used on this system is set to never reboot.  The end user told me that they manually went into Settings → Updates → Check for updates before they left for the day, which triggered a CU to download/install.  My question is, if a user manually checks for updates, clearly this overrides the Automox update policy.  But, does this also override the Automox reboot setting which is configured in the policy?   Thanks in advance for any help!

This I feel is especially important for those who manage consoles of multiple offices/entities. As each organization has their different nomenclatures and tagging practices, the only ways you can effectively track down all existing tags in the environment is by going to the Devices section and double clicking the Tags column, this will present all devices tagged in descending order, or by using the Actions option and clicking on Apply Tags (Read-only users can’t assign the tags but can see them). Lastly one can fetch a CSV report from the Devices tag and find from there. Point is, natively from the cloud console, there is no “dedicated” way. It would ideal if Zone Operators, Admins could create tags arbitrarily (like as it is right now) but one can also check existing tags and which devices have been tagged with them, kind of like the Groups subsection in the Manage section. 

Working in a script able to delete files in privileged folder like system 32. But getting “File '\Windows\System32\Tryme\new 2.txt' does not exist.” on the script bellow. According to the reponce on  this: Automox runs as SYSTEM so this issue is unlikely related to elevated privileges.Any suggestions? What am I missing here?  Evaluation Code:Exit 1 Remediation code: $filePath = "C:\Windows\System32\Tryme\new 2.txt"# Check if the file existsif (Test-Path $filePath) {    try {        # Attempt to delete the file        Remove-Item -Path $filePath -Force -Recurse        Write-Output "File '$filePath' has been successfully deleted."    } catch {        # If an error occurs, display the error message        Write-Output "An error occurred while trying to delete the file: $_"    }} else {    # If the file does not exist, inform the user    Write-Output "File '$filePath' does not exist."}

In yet another security-related initiative from the CISA Secure by Design Pledge, we’re thrilled to announce the release of our Audit Trail API. This new feature lets security teams and IT admins easily pull audit logs from the Automox console straight into their SIEM. Now, you can effortlessly track who's doing what and where.Our SecOps team put together a Python script to help you get started! Find it here. 

With the recent events in CrowdStrike world, we have all Dell enpoints and found that they could not get into the winRE without the SupportAssist OS Recovery to fix issue. Is there a way to deploy this tool via Automox? 

Hello,I am currently trying to integrate Automox with FreshService but when i search for a device that is compliant within Automox and also is a Asset within FreshService the Automox app within FreshService keeps saying: “The Device does not exist in Automox”. I configured the API and set the schedule to run daily at 12:00 AM but it has been a couple of days now and still no information is displayed.Has anyone here have any experience in setting up this integration?  

Hi Team,The Automox Console seems to have a very quick timeout on a session.Is there a way we can choose the timeout?It would also be useful if there was a way of enabling conditional access rules to say, that login request coming from a specific IP is trusted and therefore doesn’t require MFA?Cheers. 

What’s the most effective way to submit feature requests to Automox? All the links in this post:  are broken, so that feature board doesn’t appear to still work. Do I need to open a support ticket? Start a new topic? Do something else entirely? Thanks.

In our case, we don’t do Microsoft Updates, it would be great if we could only see 3rd-Party updates..  10-15 vs. 250 updates…So please filter out MS Updates (and ability to make it default view)ty

The Level III Pro Exam is live in Automox University! By passing this exam, you'll earn a certificate that recognizes you as an Automox Pro with in-depth knowledge of our powerful Worklets. Celebrate your achievement by sharing your badge on LinkedIn and in the Automox Community's YAY category. As an added bonus, you can score an exclusive Automox University Alumni t-shirt! To get this limited edition shirt, simply: pass all three exams and post your certificates on LinkedIn AND in the community.  Here’s how to add your certificate to your LinkedIn profile so your connections can see it! Make sure to tag Automox so we can celebrate with you. Begin the exam now and show everyone your Automox expertise!

I’ve tried multiple ways to change groups a device is in from the commandline on the device, all unsuccessfully.I’ve tried the suggestions from https://help.automox.com/hc/en-us/articles/5384338960020-Deploying-the-Automox-Agent-in-Bulk, and installing with the MSI options to add to a group are ignored - it always ends up in the Default Group only.This command will only install it to the Default Group, ignoring the child group:Start-Process 'msiexec.exe' -ArgumentList '/i "Automox_Installer-latest.msi" /qn /norestart ACCESSKEY=<key> GROUP="Default Group/Dev Group 1"'The PowerShell script just fails silently to even install at all when I run it, using the command as an administrator, although the same is true when run from Windows PowerShell ISE interactively..\Install-AXAgentMSI.ps1 -AccessKey <key> -GroupName "Dev Group 1"https://github.com/AutomoxCommunity/se-utilities-public/blob/main/Scripts/Install-AXAgentMSI.ps1 On Linux it’s even worse - the options to move to differ

We have PCs dotted around the world, although most are in the UK. All of them at some time or another can be a struggle to connect to with automox.I found with a couple recently, I had to use team viewer to connect and remove VNC - because the port was engaged by VNC, it was seen as ‘busy’ when attempting to connect. So you could never connect.After removal, Automox would then re-connect, re-install VNC and all would be well.I could write a worklet to remove VNC I guess, but was wondering how easy it would be just to use a worklet to free up the port? 

AXU has rolled out new content to help you level up!  Courses for you to dig into: Tagging Automox Devices with Lansweeper DataLearn how to integrate Lansweeper data to tag devices using Automox Worklets Automox Azure AD SAML WalkthroughThis video guides you through the complete setup of single sign-on for Azure Active Directory. We’re always working to develop the best learning content to help you upskill. Drop your feedback below and let us know what you’d like to see in AXU! 

I’ve recently noticed that when our 2012 R2 servers restart the Automox Agent service does not automatically start. The service on each server is set to “Automatic” but this fails to happen. Checking the event log I see the Error below. Is this a known issue for Automox on Server 2012 R2, or could this be something specific to our environment? During the boot process this event is logged:“A timeout was reached (300000 milliseconds) while waiting for the Automox Agent service to connect.” After logging in I can manually start the Automox Agent service without issue, it’s just not ideal to need to do that each time the servers restart.

would be nice to mitigate dashboard items faster by triggering multiple patch now actions.clicking on a dashboard hotlink will take me to the softwares that need to be patched or mitigated but then i have to go to over to actions and then patch now.  would be nice if I can select ALL the products I wanted to patch and then do a “patch now” to save myself lots of clicks.  

Demonstrate patching and configuration outcomes with a 400-day lookback with the all-new Policy Results Report. See historical results and trends for patching, endpoint automation, and software distribution in seconds. Now you can quickly demonstrate what you’ve done to your leadership and auditors. Plus, use the report to identify and resolve issues that caused failed patching or configuration with in-line activity log access for devices in the report.Here’s a quick breakdown of all the new goodies included in the new and improved Policy Results reportAn expansive list of filter options from policy types, groups, and status Additional Status Types, including Remediation Not Applicable and Not Included The ability to select data ranges with more historical data to reference (data collection started March 1st and that will continue to be compiled up to 400 days). Speaking of policies, this report will now include all Automox policies, including Worklets! A Group by Policy is also now an

I don’t think this is a bug per say, but when “removing” a deployment tag from new pc’s the console deleted the tag as a whole! Is there a way to not have this happen?  Also, this isn’t a worklet question, but I can’t post in the platform forum lol!! The category drop down doesn’t list it! =(  

Hi All,We had a strange pop-up on devices during/after a recent deployment using Automox. The message came from a application of executable called CopyCat (followed by a image of a white cat holding silver keys). For our piece of mind, can anyone confirm if this is a standard component of Automox, or do I need to be worried?