Using Automox

What happens if I create a Required Software Policy for an application like a Crowdstrike agent that automatically upgrades itself periodically? When the version number of the agent changes due to the upgrade, does my Automox Required Software Policy try to install the old version specified in the policy? Or does Automox recognize that the current version is higher than the one specified in the policy and take no action? Thanks

New KB here: https://support.automox.com/help/patching-cyberduck-on-windows TL;DR - We can only patch 64-bit Cyberduck and can no longer patch 32-bit versions.

I am wondering how the community handles software in use that is not being patched because it isn’t supported, the three ways I was advised of to identify them were: • Open a device details page and check if you see a value in latest version • Check the software page and see if a patch is available for a product • Reference the supported software page: https://docs.automox.com/home/software/third-party-software Unfortunately, none of these options provide me with an efficient means to get visibility to all unsupported (potentially unpatched) software currently in use. This could leave an endpoint vulnerable. My deployment is small and it is already a challenge, so I am assuming that there is a way to monitor this that I am not currently aware of. Any recommendations?

https://support.automox.com/help/20200421-01-release-notes

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

https://support.automox.com/help/20200416-01-release-notes

https://support.automox.com/help/20200415-01-release-notes

docs.microsoft.com Windows message center - Windows Release Information Windows message center reddit discussion here: reddit r/sysadmin - Support for Windows 10, 1809 extended till November 10, 2020 52 votes and 15 comments so far on Reddit

https://support.automox.com/help/20200414-01-release-notes

https://support.automox.com/help/20200413-01-release-notes

Happy Friday! Check out all the items we released this week. https://support.automox.com/help/week-in-review-weekly-release-note-summary-for-week-ending-4102020

https://support.automox.com/help/week-in-review-weekly-release-note-summary-for-week-ending-4102020

Not wearing pants Not having to shower (until Zoom adds smell-o-vission) Not having to lock your computer when you go for a snack Nobody asks for IT help when you’re on the way to the restroom Sleeping in No waiting for the microwave Only have to fight with spouse over thermostat and not the whole office Tank of gas lasts forever Working from bed Every link is now SFW 0 voters

Add last reboot time to the details pane within a device details Group patch policies like device groups. Better organization - I have various staff members managing devices and the patch schedules (macOS, Windows 10, Servers, Point of Sales). Tried to group by numbers for now. image1125×457 26 KB Initiate device reboots though follow the reboot workflow (warn users before a reboot) Indication noting software pending to be installed requires a reboot image2421×556 63.1 KB Sort devices by status image2077×131 20 KB

See full release notes here.

I wanted to start a topic to list job opportunities for those that have been impacted by the quarantine and are looking for a new gig. I just saw this listing on LinkedIn: https://www.linkedin.com/jobs/view/1789864470/ (IT manager at RingCentral. I have a connection who works there, so let me know if you want an introduction). Post any good job leads you find on here, and let us know if you want help with resume feedback or any other part of the job hunting process.

https://support.automox.com/help/20200407-01-release-notes

During our current implementation, we ran into an issue where there were Service Stack updates required on some systems before they could accurately report outstanding patches/apply patches. An update to the SSU on the given systems proved to solve the discrepancies, but leaves us with an interesting gap to fill… How can we maintain (preferably automate) updated SSU on our endpoints? Should this be automation attached as a ‘pre-step’ that needs to be executed before our scheduled patch windows? Or can this be rolled out as a daily check policy that will auto-execute whenever a new update becomes relevant (since this doesn’t require a reboot, but will our customers align)? How are you handling Service Stack updates?

I was looking at the weekly digest email that arrived yesterday and was pleased ( if a little taken aback) to see that 63.8% of our 105 devices were up to date. Our offices have been closed for a couple of weeks, so only servers and laptops should be up to date. I know the pcs in the offices are off and I am not looking forward to getting them up to date when we get back. I was wondering if it wouldn’t be better to consider a device not up to date if it had not been online since (say) the previous Wednesday?

Bug Fix: Fixed the reset filter link for software filters https://support.automox.com/help/20200406-01-release-notes

Bug Fixes: Consistent device statuses across the console Zoom on macOS will now patch successfully and without disruption if a meeting is in progress Removed ability to edit email address from SAML users Fixed the invite link in the email that invites others to join a given organization Running Chrome instance no longer fails when Chrome is upgraded on Mac Harmonized device statuses across the console so that all device statues are consistent Enhancements: New third party patching support for Slack on macOS and Windows New third party patching support for VMware Horizon Client on macOS and Windows New third party patching support for PuTTY on Windows New third party patching support for Box Drive on Windows New third party patching support for Microsoft OneDrive on macOS and Windows New third party patching support for Zoom Outlook Plugin on Windows New third party patching support for Wireshark on macOS and Windows https://support.automox.com/help/week-in-review-release-notes-for-

Enhancements: New third party patching support for Slack on macOS and Windows New third party patching support for VMware Horizon Client on macOS and Windows https://support.automox.com/help/week-in-review-release-notes-for-week-ending-04032020

Bug Fixes: Zoom on macOS will now patch successfully and without disruption if a meeting is in progress Enhancements: New third party patching support for PuTTY on Windows New third party patching support for Box Drive on Windows https://support.automox.com/help/20200401-01-release-notes

Bug Fixes: Consistent device statuses across the console https://support.automox.com/help/20200402-01-release-notes

I am wanting to build out a detailed Splunk Dashboard. Is there a way in the API to get a list or count of devices needing a patch based on severity? Like showing all the machines with Critical Patches