Customer Appreciation Day: Thank you for your dedication and leadership

At Automox, we have a library of favorite words and phrases. And, if you’re a customer, you’ve likely seen the following usual suspects quite a bit when reading our content:

• Endpoint management

• Patching

• Scalable

• Safe

• Fast

• Easy

• Secure

• Automate

But there’s a phrase we don’t use enough, especially when it comes to you: Thank you! Thank you. A million times, thank you.

Thank you to our Automox customers and superusers for inspiring us to keep finding and fixing, patching and remediating.

You keep us innovating, problem-solving, and striving to meet your growing needs as well as surpass your expectations. 

To that end, today we wanted to take the opportunity to revisit some of our top time-savings Worklets with you. In case you missed them, or in case you just need a little inspo to get through your day today: read on!

Automox developed customized Worklets for SentinelOne that include pre-built scripts for automatic deployment of the SentinelOne agent across Windows, Linux, and macOS devices – without manual intervention or wasted IT cycles. Big thanks to @Zac-Automox.

The Black Lotus vulnerability is an important, actively exploited zero-day that allows an attacker with physical access or administrative rights to a target device to install an affected boot policy and potentially bypass secure boot. This Worklet helps administrators automatically find the vulnerability and ensure that the May 2023 updates from Microsoft have been applied prior to remediation. If the endpoint meets the criteria, then we’ll remediate it.

This is an older CVE that Microsoft reissued on January 21, 2022. There’s no patch for this vulnerability. It affects all current and previous versions of Windows OS. And it’s considered “opt-in” with no plans to enforce stricter verification.

Updated reissue: CVE-2013-3900 – Security Update Guide - Microsoft - WinVerifyTrust Signature Validation Vuln. Shout out to Juanmbi

Community member jesumyip sometimes has to replicate the behavior of GPOs that run in the user context. This means you need to execute a task under the current logged-on user and trigger it to occur only when the user logs on. To achieve this, you can use a scheduled task with two special settings:

1. It is triggered only when a user logs on

2. It runs under the context of the local “USERS” group.

With #2, you can access all the usual user-context-specific data such as %USERNAME%, HKCU, etc. And, this approach makes the scheduled task run under the context of ANY user that logs on. Thank you jesumyip!