You're looking at the Yellow Pages for Community Worklets... find Worklets and share your own here!
Recently active
Hi, we currently have a policy which only patches and does not reboot devices automatically. Since user initiated reboots “do not count” by Automox - What is the best way to prompt a reboot notification to the users, without forcing a reboot of course?
Hi Everyone!I am trying to create a worklet for Linux servers that requires a file to be put onto the servers. I have uploaded the file to the worklet, but I cannot find details on where this file will be located for me to interact with it. Where do the files get placed when the worklet runs? My evaluation and remediation code will need to interact with this payload file.
Hello Team-We want to close all running processes without user intervention. I have tested this script locally and have no issues however, I am unable to get it to process through automox. Any ideas? # Get the current PowerShell process$currentProcess = Get-Process -Id $PID# Processes to exclude from closure$excludeProcesses = @("amagent", "powershell")# Get a list of all running processes except the current PowerShell process and the excluded processes$runningProcesses = Get-Process | Where-Object { $_.MainWindowTitle -ne "" -and $_.Id -ne $currentProcess.Id -and $_.ProcessName -notin $excludeProcesses }# Iterate through the list of processes and close themforeach ($process in $runningProcesses) { Write-Host "Closing $($process.ProcessName)..." $process.CloseMainWindow() # Wait for a few seconds to allow the application to close gracefully Start-Sleep -Seconds 5 # If the application is still running, terminate it forcefully if (!$process.HasExited) { W
I have a full script that uninstalls Teams classic as Microsoft is pushing the new teams however I cannot get it to work properly by breaking it up. I put this in for the evaluation and remediation - could someone with automox savviness assist? Evaluation#Locate installation folder $localAppData = "$($env:LOCALAPPDATA)\Microsoft\Teams" $programData = "$($env:ProgramData)\$($env:USERNAME)\Microsoft\Teams" If (Test-Path "$($localAppData)\Current\Teams.exe") { unInstallTeams($localAppData) } elseif (Test-Path "$($programData)\Current\Teams.exe") { unInstallTeams($programData) } else { Write-Warning "Teams installation not found" }Remediationfunction unInstallTeams($path) { $clientInstaller = "$($path)\Update.exe" try { $process = Start-Process -FilePath "$clientInstaller" -ArgumentList "--uninstall /s" -PassThru -Wait -ErrorAction STOP if ($process.ExitCode -ne 0) { Write-Error "UnInstallation failed with exit code $($p
I have a handful of Windows 11 21H2 devices that I would like to get to 23H2 so they can continue to receive security updates. How can I do this with Automox? We have had good success in getting Windows 10 devices using the worklet “Windows - Configuration - Windows 11 Feature Update” but any time that is run on a Win 11 21H2 device it simply checks out as already on Windows 11, and doesn’t apply anything. I could be overlooking something as simple as including a specific update in our regular monthly patch policies, but I can’t seem to find what I’m looking for. How have others done this?
Hi all,Has anyone had issues with a feature update showing for a device in Automox after setting the target release version in registry?This is the second time I’ve had this issue.I set the target release version to 23h2, enabling it with the value of 1, and specifying the product version of win 11. Once I set those values, I rescan the machine and usually the update is showing as a patch for the device in Automox, but in this case, it isn’t. The device is win 11 ready.Any ideas?This is the PS script I’m using to push out the reg keys. I’ve ran this on 20+ devices and the update shows up with no issues.#># Define Values in this section#############################################$rValue = '1' #Enable Target Release Version 0 = Disabled, 1 = Enabled$rInfoValue = '23h2' #Specify Windows 11 Target Release Version. Select the preferred version from https://docs.microsoft.com/en-us/windows/release-information/$rWindows = 'Windows 11' #Specify Windows 11###################################
Evaluation code: $testFile = "$env:windir\RemovedBloatware.txt" $testFileValue = (Test-Path $testFile) if ($testFileValue -eq $true ) { Exit 0 } else { Exit 1 } Remediation code: schtasks /delete /tn GlanceDiscovery /f Get-AppxPackage -Allusers -Name MirametrixInc.GlancebyMirametrix | Remove-AppxPackage -AllUsers Get-AppxPackage -Allusers -name "Microsoft.ZuneMusic" | Remove-AppxPackage -Allusers Get-AppxPackage -Allusers -name "Microsoft.Music.Preview" | Remove-AppxPackage -Allusers Get-AppxPackage -Allusers -name "Microsoft.XboxGameCallableUI" | Remove-AppxPackage -Allusers Get-AppxPackage -Allusers -name "Microsoft.XboxIdentityProvider" | Remove-AppxPackage -Allusers Get-AppxPackage -Allusers -name "Microsoft.BingTravel" | Remove-AppxPackage -Allusers Get-AppxPackage -Allusers -name "Microsoft.BingHealthAndFitness" | Remove-AppxPackage -Allusers Get-AppxPackage -Allusers -name "Microsoft.BingFoodAndDrink" | Remove-AppxPackage -Allusers Get-AppxPackage -Allusers -name "Microsof
Is there any existing worklet to uninstall Snagit?I’ve attempted to use the uninstall worklet template titled Uninstall Specific App by Name and Uninstall all apps under specific version and both have resulted in command timeout.
How do you generate a report of installed updates on app systems for a certain period of time ( 1 month up to 1 year) for adding purpose
I do have the exe installer from adobe and have tried to create a worklet but it doesn’t appear to be workingI tried looking through the catalog and previous threads and couldn’t find anything. Is there already a worklet that exists to install adobe acrobat pro? I am posting the worklet I tried to create in hopes that someone could try to fix it. I use a payload with the setup.exe file. However this doesn’t appear to be working. Any help is much appreciated! <#.SYNOPSIS EXE Software Installation (System Wide-All Users) - Evaluation Script OS Support: Windows 7 and above Required modules: NONE.DESCRIPTION This worklet is designed to grant an Admin the ability to install a (System Wide-All Users) EXE with minimal knowledge of the bitness, command line, or other EXE properties. By placing an application name between the single quotes, the worklet will scan the registry for the matching application. If the application is not found, it will return an Exit code of '1'
This has been an interesting one I thought I’d share. I’m honestly still very hands on with this one and only run it manually. Meaning I fully expect this to be a journey, not a perfect solution.Also please note, I’m using the Get-Win32 and Remove-Win32App cmdlets available by using Automox’s amazing WDK https://developer.automox.com/developer-portal/wdk/overview/ (saves me from writing so much code) Another call-out. These worklets will install dotnet-uninstall-tool version 1.6.0 explicitly (update code to use newer versions). Learn more about that at Emanuele Bartolesi blog here https://dev.to/kasuken/removing-old-version-of-net-4052 or just go checkout the latest releases of the Microsoft built tool here https://github.com/dotnet/cli-lab/releases My workflow consists of using two worklets as such:Update variable versions in BOTH worklets manually based on my own internal needs of what versions need removed (typically get this list from a vulnerability scanner’s output) Run the NET C
I am in looking at purchasing Automox and currently in the trials phase. One thing I am interested in is the Remote Wipe Worklet. The question I have is, is it possible to have a worklet launch another worklet? I would like to be able to launch the Remote Wipe worklet and when this finishes, launch either individual worklets (for the additional software that needs to install afterwards) or maybe have one worklet built specifically for installing multiple packages. We currently run an on-prem solution that can run through sequences to load the OS and install apps. We have another solution that we can build custom packages (like installing apps or running powershell scripts) and then have them all run in sequence.
Hi Team,Just wanted to know about different methods to install agent on bulk to the remote Linux nodes. Do we have any scripts to install agent on Remote Linux machine? if so, can you please share the script for install agent to a remote Linux OS?ThanksShoaib
Hi Everyone, we just recently switched from PDQ to Automox and im new to this platform, and im migrating our baseline applications to Automox.. im using required software policy to install it on endpoint devices.. simples stuff attaching msi or exe and writing installation command in there but the thing it comes out at installed software in Automox policy activity log but its not actually installed at endpoint.. im pasting command here that im using.. let me know if im doing something wrong here.. $exitCode = (Start-Process -FilePath 'msiexec.exe' -ArgumentList '/qn', '/i', '"CitrixWorkspaceApp.exe"', '/norestart' -Wait -PassThru).ExitCode exit $exitCode then i tried this one to see if can get log file to see whats wrong but it giving same thing and dont see a log folder on device.. $logPath = "C:\AutomoxLogs\CitrixWorkspaceAppInstallLog.txt"try { $exitCode = (Start-Process -FilePath 'msiexec.exe' -ArgumentList '/qn', '/i', '"CitrixWorkspaceApp.exe"', '/norestart' -Wait -PassThru
How do you export current policies and groups in automox. I don’t see any options available to this in the platform.
Hi, folks! I’m happy to share a Linux Worklet script that we at Mapbox IT have now fully open-sourced. The Worklet we created here ultimately wound up turning into a full-fledged project that we’ve since named: “Lockbox.” Lockbox builds off of pre-existing Linux encryption tools and aims to offer IT staff with a linux endpoint encryption experience that feels similar to Windows Bitlocker or macOS FileVault. That is, it: Allows admins to remotely rotate, store, and clear encryption keys on Linux endpoints Utilizes TPM key storage for a seamless boot-up experience (No need to enter a recovery key each time) Stores encryption keys as device tags in the Automox console (Drew on inspiration from this awesome worklet Creates a platform for administrators to “lock” devices remotely with a simple tpm2_clear command. (Clears TPM so the user is locked out but leaves a remaining admin recovery key) Never stores API credentials in plain-text Note that this does require your endpoint to be encry
Has anyone ran this worklet successfully? I am trying to run it but i am getting a 0x1 error in Task Scheduler which refers to permission errors. Is that correct? The driver is already installed so it should just need to map the printer to the logged on user’s profile. Am i missing something?
Hi,Do you have a working worklet for Fireeye agent removal? We have a batch file to remove the agent. Is there a way to create a worklet using a batch file?Thanks
I have ran this worklet on 3 or 4 machines now and I can see the processes running in Task Manager, but the machine never reboots and never updates to 11.I saw a thread on checking for registry entries and removing them but they aren’t present. Just curious if anyone has had success with this.
Can someone explain when Automox decides to run the remediation code of a worklet? I am using the worklet “Windows - Maintenance - Maintenance Window Reboots” from the worklet catalog and have the restart days as Saturday and a maintenance window of 4:00AM - 4:30AM”. After applying this worklet to a group I scan the device and it shows as “Compliant”. When the worklet scheduled time comes around there is no activity when it should in fact have rebooted the devices because they are all pending updates. Do I need to change the restart days to every day so Automox thinks it needs to be rebooted and set the worklet schedule to the day it needs to be remediated?
In an effort to reduce our required outage time for patching, I’ve created a worklet that sets a few registry keys on Windows systems to enable Windows Update to download (but not install) any newly relevant patches. This should significantly improve our ability to execute patching windows quickly, especially for systems at remote locations or with restricted bandwidth. Note: only the ‘NoAutoUpdate’ and ‘AUOptions’ keys are actually required to enable this behavior. There are two other keys we have included to better manage this process for our needs. (Special shoutout to @Josh-W for some assistance/finishing touches!) Evaluation Code: # Check registry key/value to enable Automatic Downloading of all relevant patches - DOES NOT INSTALL ############################################# $regPathAU = 'HKLM:\Software\Policies\Microsoft\Windows\WindowsUpdate\AU' $regPathWindowsUpdate = 'HKLM:\Software\Policies\Microsoft\Windows\WindowsUpdate' $regPropertyAUOptions = 'AUOptions' $desiredValueAU
Hi Team, i see a worklet to deploy file to certain directories for windows but not macOS. How would i be able to move a file into a certain directory in macOS? thanks
Hello, I am having issues with the worklet mentioned in the title. I have a PC from our environment that I am testing with this worklet. I have changed nothing on the worklet except change the cutoff day to 60 days. I can see under This PC > Windows > Users that there are profiles that show under the “Date Modified” column as not having any changes since April. However, the worklet is not removing those. It runs the first check and says there are no old profiles. I’ll admit I’m still learning Powershell, so maybe I have something confused, but if someone could point me in the right direction of what I need to modify I would appreciate it. Let me know if you’d like more info. TIA!
Hey Y’all! Automox offers a fully customizable end-user notification feature that clearly indicates to users when Automox will be patching and potentially rebooting their systems. This feature also allows you to set custom deferral options empowering users to control when their device should be patched. This gives peace of mind to system admins that their environment will be patched without interfering with their users everyday use. Although this is a great feature, Automox recognizes that it does not offer the predictability to users to when the actual reboot event will take place. We are currently working on improving our current notifications to give users better reboot predictability. Automox has gathered a lot of customer feedback aimed to make this feature enhancement as effective as possible. The great thing about this is it will be built into the product and be offered in the same fashion as the current end-user notifications. So, what can you do until this feature is released?
What is the best way to have automox execute two one line commands? the commands would be: winget install Microsoft.DotNet.DesktopRuntime.7winget install Microsoft.DotNet.AspNetCore.7 would i create a worklet with both remedaition and execution code to something like this:winget install Microsoft.DotNet.DesktopRuntime.7 && winget install Microsoft.DotNet.AspNetCore.7 i dont know if the && works the same way in windows as it does linux?
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.