Automox Worklets

Shout out to the 2 authors of this worklet:  John Guarracino and Eric Liles. We’re a little late in updating all of our laptops to Windows 11 but this past month we successfully updated all of our 200 laptops using the Windows 11 Feature Update worklet. The worklet was easy to setup and the downtime for the users was minimal. Thanks!

Hi,We’ve been a Automox client since May 2022.When we started to deploy the Automox Agent to our end user Windows 10 and 11 laptops we ran into a problem after about a month when a not insignificant amount stopped communicating with the Automox console. Without exception, when we investigated we found the Automox Agent wasn't running on the end point. Starting the service or restarting the machine would fix it.Reviewing amagent.log would present messages about abnormal closure to websocket.2022/09/25 00:54:07 stompclient.go:399: Error in axstomp readframe: websocket: close 1006 (abnormal closure): unexpected EOF2022/09/25 00:54:07 stompclient.go:437: Consumer error: websocket: close 1006 (abnormal closure): unexpected EOFWe were told the root cause was because our end users connect to a corp VPN and that the momentary change in connectivity for those devices was causing the Automox agent to to crash. While I understood the logic, I felt the agent should be able to handle a change in co

Hello Community!Does anyone have a worklet they can share to enable the local administrator account?Thanks!

Hi guys!We are testing Automox and are very impressed of its capabilities.  I already deployed winget successfully using Automox to our Windows machines. Now I am looking for a way to store the result of our worklet to check for winget updates into a field of the device (the “notes” field?). Or can we create an own field and put it in there?This way I can see the winget status directly in the device. What do you suggest how to realize this? Looking forward for your ideas.

We are trying to remove an old local account that is on most of our windows computers.  The code removed the account when I ran it locally but not when I run it through automox. # Delete a local account named "tommyboy" $AccountName = "tommyboy"# Check if the account existsif (Get-LocalUser -Name $AccountName -ErrorAction SilentlyContinue) { # Forcefully delete the account Remove-LocalUser -Name $AccountName -Force Write-Host "The account '$AccountName' has been deleted successfully."} else { Write-Host "The account '$AccountName' does not exist."} 

I am new to automox and learning. I am currently just testing on a worklet that will change the background of windows os. My scipt will upload the file in the c drive but the background is not changing.

I am writing a PS worklet to prompt the user to close Outlook to allow the install of the Mimecast for Outlook plugin. I would like to not go down the road of creating a scheduled task to perform this action. I have tried a couple different options:Send-ActiveUserMessage -Title 'Close Outlook' -Message 'Outlook will close automatically in 1 minute for the Mimecast plugin Install. Please wait 5 mins before opening Outlook again. Thanks, IT.' DialogType 'OK' -Timeout 60&# Add required assembly for MessageBoxAdd-Type -AssemblyName "System.Windows.Forms"# Show MessageBox that Outlook is closing[System.Windows.Forms.MessageBox]::Show('Outlook will close automatically in 1 minute for the Mimecast plugin Install. Please wait 5 mins before opening Outlook again. Thanks, IT.','Close Outlook','OK','Warning') Neither seem to display an interactive message for the user but work in ISE. I read in a previous post here that this was due to the worklet being run as system user and that makes sense

Good morning! I am attempting to use the worklet to set a login screen for Windows but was wondering if anyone had successfully changed the image source from a URL to an image uploaded into the worklet. If they have, could you please share the syntax used to replace this line? # define the path to download the background image$ImageURL = 'https://www.automox.com/static/images/default-og-image.png'

Hi everyone,Has anyone successfully installed OpenEdge using Automox?Given the payload limitations in Automox, it seems like this might be challenging—or possibly not feasible at all. However, I wanted to check if anyone has attempted this in their environment and managed to get it working.More details about the silent installation process for Progress OpenEdge can be found here:Progress Documentation – Silent Installation Thanks in advance!  

I need help upgrading our windows 11 machines to 24h2. We moved from Sccm/gpo to Intune and now we use automox for all our updates. We are currently pushing the 24h2 feature update with intune, but some devices aren’t getting the update. I wonder if there’s a conflict between intune and automox somewhere? I found this worklet that looks promising, has anyone had success?  Worklet Details · Automox Also, we have machines on 23h2 that are listed as showing 24h2 installed, but they are on 23h2. See the attached photos. 

Hello,I’m trying to find a way to remove Chrome Extensions.  I have found this script but in Automox I just get a command timeout when it runs:Remove or block Chrome extensions with PowerShell – 4sysopsAnyone have any ideas?Cheers,Mark

I created a worklet using two PowerShell scripts: one for the Evaluation Code and the other for the Remediation Code. I tested both scripts locally on a PC with Microsoft Silverlight installed, and they worked as expected. However, when I created the worklet, it did not perform any actions.

Hi,We have around 600 HP endpoints.  I’d like to run HPImageAssistant.exe to silently install all drivers.  Previously I’ve used a scheduled task/GPO, but I’m hoping some one might have some knowledge on how to do this via a Worklet.  The file will need copying to the local machine too, again not sure if this is how the Payload works?This is the script I’ve used before:C:\HPIA\HPImageAssistant.exe /Operation:Analyze /Action:Install /Selection:All /Silent /ReportFolder:C:\HPIA\Logs /SoftpaqDownloadFolder:C:\HPIA\DriversI’m really not sure how to achieve this - any help would be appreciated. Thanks,Matt

Just checking if somebody here in the community created a worklet that upgrades vmware tools and works?

We had to do a rest on some computers and the reset created Windows.old folders that I need to get removed.  The worklet says it removes the folders but they are not removed.  Any help would be greatly appreciated. $folders = @("C:\Windows.old", "C:\Windows.old(1)", "C:\Windows.old(2)")foreach ($folder in $folders) { if (Test-Path $folder) { Remove-Item -Path $folder -Recurse -Force Write-Output "Deleted: $folder" } else { Write-Output "Not found: $folder" }} 

Hello! I have used this Automox approved worklet in the past but now in the Activity log it only outputs “1”  and never encrypts the drive Computer is on 22H2 Windows 10 ProPowerShell 5 Eval<#.SYNOPSIS Enforce Bitlocker Encryption - Evaluation Script OS Support: Windows 8(Server 2012) and above Powershell: 4.0 and above Run Type: Evaluation or OnDemand.DESCRIPTION This Worklet is designed to grant an Admin the ability to encrypt physical drives on a client device using BitLocker. A TPM chip is required to perform the default actions of this worklet. If a non-TPM device is encountered, the Worklet will exit without making any changes, and a note will be added to the Activity Log. Usage: The Evaluation script uses only 1 variable that controls the scope of drives to be encrypted. This variable should be the same value as the Remediation script to ensure devices are targeted correctly. Values provided should be between quotes after the "=". Use only one

I'm trying to install some software (Snagit) with an MSI installer that references an MST file.  I have been able to do this in the past for a required software policy for another piece of software, but my hangup here is that prior to the installation, I have to run an uninstaller to remove previous versions or else the user will have side-by-side installations, which we don't want.  Also, this wouldn't be a required software policy, rather a worklet, and I don't know how to convert the “start-process” command line into a workable worklet argument that would meet the requirements. Requirements:-Only run the worklet if they are under the major version 25.XXX as anything with version 25 won't need a full uninstall and the update policy should handle the minor version update from 25.X to 25.Y.-Run the uninstaller (only if they have a version less than 25) to prevent side-by-side installations. Using their uninstaller tool will suppress the confirmation popups the user would normally get a

Hi all, Put in a support ticket for this as well, not sure if AM support helps with custom worklets or not, anyways… here’s the issue i’m trying to solve.  We’re migrating our printers to Universal Print in Azure as we’re slowly removing on-prem servers.  So, I need to remove printers from users' computers that were previously hosted via a print server.  So, I had Otto help me out, because I don’t know Powershell scripting for crap, and this is what the results were -  Here's the Evaluation Code -# ======================# Otto AI Generated Code# ======================# Define the printer names to check$printerNames = @('\\fpwc03\CO-HR1', # First printer to check'\\fpwc03\CO-Main PS' # Second printer to check)# Initialize a flag to determine if any printer is installed$printerFound = $false# Loop through each printer name to check existenceforeach ($printerName in $printerNames) {if (Get-Printer -Name $printerName -ErrorAction SilentlyContinue) {# If the printer exists, set the flag to

Have been testing out running some PS scripts but nothing seems to be sticking with the scripts I’ve tried Curious is anyone here has tried anything that removed Outlook (new) from users profiles and keeps it removed, leaving only Outlook (classic)  

Is it possible to create a worklet that will join a workstation to a corperate domain?  Has anyone attempted this before?

Disclaimer - this will apply all Dell driver updates without a reboot. It is up to you to configure this to your environment. This worklet will Install Dell Command Update. Be sure to include the binaries and update the name to the EXE you use. https://www.dell.com/support/home/en-us/drivers/DriversDetails?driverId=JDXHH Once installed or if already installed the worklet is setup to install updates then parse through a log to provide some details on what updates, if any were installed. Activity Log Output Evaluation Code $system = Get-WmiObject win32_computersystem IF($system.Manufacturer -match "Dell"){ Exit 1 }else { Exit 0 } Remediation Code # Dell Command | Update executable uploaded to worklet $exe = 'Dell-Command-Update-Application-for-Windows10_JDXHH_WIN_4.2.0_A00.EXE' # Dell Command Version [version]$version = '4.2.0' # Log location $log = 'C:\Windows\Temp\DellCommand_Install.txt' $system = Get-WmiObject win32_computersystem IF($system.Manufacturer -match "Dell"){

This isn't a worklet because if you are like us and are constantly battling disconnected agents or agents that never even made it to the portal you will have to resort to your MDM to resolve.  In our case, the agents are installed, service running, but not connected. We tried restarting the service but had no effect. 75% of the MDM installs of automox agent went fine, so it is not our install strategy.What we had to do is run the readily available amox cleaner script and then re-install the app. But we needed something to trigger it off of and Automox has nothing to determine on the client side if the agent is either in the portal or connected.  We ended up creating a powershell with an API Call to check if the computer was A) in the portal and B) connected. Again, a quick search for something like Automox agent clean or something similar will yield you the removal script which properly removes the service.  Here you go… function Check-Connection{# Define the API endpoint and token$bas

My Helpdesk team is encountering an issue in our Warehouse where multiple users will sign into a PC and fill up the disk space seemlingly overnight.I need a worklet that will evaluate the disk space on a shared PC and then delete user profiles that haven’t been modified or used in over 30 days if that disk exceeds 50%. I would also like it to also run disk cleanup every night.

Sometimes the auto-update process can fail for an agent and when it does, it gets stuck at the older version as newer versions are released. This worklet seeks out those older agents and attempts to upgrade them. If the agent is very old or not functioning properly, this worklet may not work. I’ve only been able to test on systems going back to v1.0.25, but I’m betting it can get older ones upgraded as long as the agent is functional. If you’re unsure of the status of your agent versions, you can run this agent health report which will give you all of the agent versions on your devices along with some other information on them you might find handy:    Based on a query by @d.mccleskey that support would have to run for customers, I’ve adapted it so that customers can run it for themselves. This query is useful for customers to review their Automox patching configurations and review agent communication/health.$apiKey = 'YOUR_API_KEY' - in your console, go to Settings->API and select t

Have a worklet that find and removes appdata for a legacy application from all user profiles on a system. Unfortunately it doesn’t appear to be working when I run it for all endpoints ( worked fine for a single endpoint test ). $NameShort = "Q-Pulse" if ($NameShort.Length -gt 7) { $NameShort = $NameShort.Substring(0, 4) + "\." } $rex = $NameShort + "\..+" $Paths = @( "$env:Localappdata\Apps\2.0" "$env:Localappdata\Deployment" "$env:Localappdata\Microsoft\Windows\INetCache\IE" "$env:Temp\Deployment" )foreach ($Path in $Paths) { Get-ChildItem -Recurse $Path | ForEach-Object { If ($_ -match $rex) { Remove-Item -Force -Recurse $_.FullName } } } $startMenuPath = [Environment]::GetFolderPath("StartMenu")$appShortcut = Get-ChildItem -Path $startMenuPath -Recurse -Filter "*$($NameShort)*.appref-ms"if ($appShortcut) { Remove-Item -Path $appShortcut.FullName -Force}Remove-Item -Path "$env: