Using Automox

This API script will move multiple computers - regardless of what group they’re currently in - to a group you specify. You’ll need to set the following before running the script: $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. $orgID = 'YOUR_ORG_ID' - put in your Org ID which can be found by looking at the URL on the dashboard and selecting the value after the “?o=”: [https://console.automox.com/dashboard?o=1234]. In this example the Org ID is 1234. $targetGID = 'GROUP_ID#_TO_MOVE_TO' - put your Group ID you want the devices moved to, which can be found by viewing the group page that lists devices in that particular group and grabbing the value after “gid=” in the URL. $toMove - Put your list of device names you want to be moved in quotes separated by a comma. You can also modify $logpath if you want to change the location where the

Greetings. We are deploying the Automox Agent to Windows endpoints, our plan being to embed our Automox Agent Access Key as part of the distributed .msi file (see https://support.automox.com/help/embedding-your-access-key-into-the-automox-msi). My concern is that this process may leave stray copies of the installer on endpoints post-deployment, each including its copy of our Agent Access Key, by which unintended additions to our account might occur. More generally, my research to date indicates our Agent Access Key has no privileges beside allowing a machine to add itself to our Automox account, but OTOH we seem to have no way of expiring or rotating this key. If so, it seems we may be open to unintended additions to our Automox account should our .msi file be discovered by a “bad actor” at some point. Put plainly, if we were to deploy private information to our endpoints via Automox, perhaps a “bad actor” could use his registered agent to accumulate this information. If the foregoi

Original script written by @AX-Jon in May 2021, this will check compliance against any system the policy is running against. It can check for a policy, worklet, or required software policy. Just set the following: $apiKey = 'YOUR_API_KEY' - in your console, click on the three dots in the upper right, select KEYS, then copy your API key. Note that the API key is per admin user, so you and another admin in your console will have different API keys. $orgID = 'YOUR_ORG_ID' - put your Org ID which can be found by looking at the URL on the device page and selecting the value after the “?o=”: [https://console.automox.com/device-detail?s=99999&o=1234 ]. In this example the Org ID is 1234. $policyID - put your PolicyID for the policy, worklet, or required software policy here. The easiest way to find the policy ID is to go to the page of the policy and grab the value in the URL after the “&pid=” : [https://console.automox.com/policy-custom-editor?frompage=system-management&pid=99

Hi Team, In the Devices page, under the OS filter, Server 2019 Datacenter is missing. I thought I was going mad when half my servers didn’t appear 🙂 Please could you put it back? Cheers.

https://support.automox.com/help/release-notes-for-week-ending-05282021 A new Data Extracts option is available on the Reports page that allows customers to export detailed device information data and historical patching activity. More info: Data Extracts | Automox Knowledge Base

For those of you deploying Automox via your image deployment software, here’s instructions on how to setup Automox for the gold image to avoid duplicates showing up in the console. https://support.automox.com/help/how-to-create-a-gold-image-vm

How can I only update the software that is on Mac machines but bypass MacOS version updates and security updates? I am wanting to manage those updates elsewhere.

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

is there a way to build your own updates for programs. i have certain programs we use that need to be updated.

Trying to install Splashtop streamer with no success, I created a required software policy: exit (Start-Process -FilePath ‘msiexec.exe’ -ArgumentList (’/qn’, ‘/i’,‘USERINFO=“dcode=XXXXXXXXXXXXX,hidewindow=1,confirm_d=0”’ ‘“Splashtop_Streamer_Win_DEPLOY_INSTALLER_v3.4.6.0.msi”’) -Wait -Passthru).ExitCode What do I have wrong? Here is what the vendor requires, this works just fine. msiexec /norestart /qn /i streamer.msi USERINFO=“dcode= your_code ,hidewindow=1,confirm_d=0”

Based on your exemption recommendations, I have most of my patching policies set to PATCH ALL EXCEPT: KB2267602 KB915597 Preview Feature Update KB4481252 MS Silverlight Based on Microsoft releasing its new updates (20H1/20H2) as “feature updates”, should I remove “Feature Update” from list of exemptions? I think this will be the easiest method to get the newer branches / updates, as their branding is changing to half of years…any thoughts or insight?

Why does the IP address column have multiple IP addresses for the devices listed?

When testing Worklets or Required Software policies, I’m unable to rerun the policy multiple times after changing the policy. The status just displays Pending Update, sometimes for hours. Any suggestions? Thanks Mark

We’re very proud to announce our next funding round! Get all the details here: blog.automox.com Automox Secures $110 Million in Series C Funding to Modernize IT Operations Automox, the cloud-native endpoint management provider, today announced it has secured $110 million in Series C funding to accelerate its vision to modernize IT operations with a comprehensive, cloud-native platform.

Hey Everyone, Currently I use a script to encrypt drives with Bitlocker and then saves the keys in the device’s tags in automox: Worklet: Store Bitlocker Keys in Device Tags One thing that is rather annoying is if I ever need to look into the reports for this worklet running it shows every single device from the API call in a blob of text. Is any aware of how to hide the API call information from showing up in the reports?

We have users complaining about automox restarting machine during the working day as this is sometimes happening during client meetings it is frustrating and embarrassing for them (and destroying their goodwill towards having automox installed) I have seen a group policy that may stop automox doing this, but is there a more elegant way to do it?

Is there a typo at the following page https://docs.automox.com/home/agent-installation/deploying-the-automox-agent-in-bulk#deploying-with-jumpcloud ? I’ve followed the instructions, but when I run the command through a Windows System managed by Jumpcloud I get the following error: The term ‘sudo’ is not recognized as the name of a cmdlet, function, script file, or opera ble program. The example of the command from Automox document is curl -sS https://console.automox.com/downloadInstaller?accesskey=Your-Organization-Key-Here | sudo bash service amagent start Is “sudo bash” not required? Thanks,

I use jumpcloud that supports “chocolatey” as its “windows package manager” What this means is for software it has, it’s just a matter of me choosing it and the device and it goes away and installs it with no tweaking of coding from me 🙂 I know there are other deployment tools that use it and even people like me who like using it directly as they prefer the cleanness of commandline installers Are there any plans to support chocolatey? Chocolatey Software Chocolatey - The package manager for Windows Chocolatey is software management automation for Windows that wraps installers, executables, zips, and scripts into compiled packages. Chocolatey integrates w/SCCM, Puppet, Chef, etc. Chocolatey is trusted by businesses to manage software...

We’ve got some momentum going on the 3rd party software support, having just recently reached 20 titles with yesterday’s release: https://support.automox.com/help/third-party-patching-software We do have a section for 3rd party app requests here on our product board: portal.productboard.com Under consideration - Automox Product Portal Product roadmap and feature requests. Welcome to our product portal. Feel free to add your wishes and votes there, or post below with the software titles that you’d love to see us add first!

I am curious if anyone used worklet to make changes to SPI and DCI?

We’re cutting over our sites to Vonage. The system looks good, has Teams integrations, blah blah blah… I don’t really care. The transition from one system to the next is a freaking nightmare. It’s 2021. Why are phone systems this overly complicated? I literally just want a thingy that peeps can pick up and talk to other peeps and maybe see if those peeps are currently busy or not. BUT NOPE, you need 5987598723487 features and janky groups. Nothing can be simple. We can’t just name things with terms or words that make sense but rather lets call basic groups things like HUNT GROUPS. Because yes, when I think of a sequential phone tree style group I would never call it a phone tree or sequential something or another… I call that a HUNT group. Yea, I know HUNT groups aren’t new but jesus. Who names this crap and why haven’t phone systems become less complex with time?

https://support.automox.com/help/release-notes-for-week-ending-04232021 Bug Fixes Resolved an issue in detecting the device reboot status on RHEL 8.3.

Hi there, I can see you have been making strides in improving user and backend experience but the amount of 3rd party titles has been quite stagnant, is there any chance in supporting more titles natively than doing so through Worklets?