Let’s Go!!! Can’t wait to see what you all come up with. 

Wi-fi Network Adapter Info:

Script: 

Output 

Here’s a uesfull worklet I have created, this worklet ensures that no users have admin level access on there workstations. We do have service accounts such as domain admin etc that can remain there, it will remove any users that are not listed.

pretty cool!

I have to share since Ivanti was called out on the Automox website when we first started to look for a new patch deployment tool .  

We needed something to begin the removal process.

Script to remove the Ivanti Scheduling services and clean up the ProPatches directory.  

Hi Folks,

Thought this worklet might help people as well. I created this worklet to enroll all company managed devices to enroll in Intune and add in Azure AD. it will save you ton of time for enrollment process if you are migrating from tenant to tenant in Azure or just onboarding with your Azure tenant.

I havent got a chance to trim it but you could add evaluation script like below. In my script i just skipped evaluation part with exit code 1.

(Note: You need to create provisioning package for Azure/Intune to deploy it through Automox. Refer to this link for how to create provisioning package: https://techcommunity.microsoft.com/t5/intune-customer-success/bulk-join-a-windows-device-to-azure-ad-and-microsoft-endpoint/ba-p/2381400)

 Evaluation Script: 

# Check if the device is Azure AD joined
$azureAdStatus = dsregcmd /status
$azureAdJoined = $azureAdStatus | Select-String "AzureAdJoined" | ForEach-Object { $_.Line -match "AzureAdJoined\s*:\s*(\S+)" ; $matches$1] }

# Check if the device is enrolled in Intune by looking for the Intune certificate
$intuneCertificatePath = "Cert:\LocalMachine\My"
$intuneCertificate = Get-ChildItem -Path $intuneCertificatePath | Where-Object { $_.Issuer -like "*Intune*" -or $_.Subject -like "*Intune*" }
if ($azureAdJoined -eq "YES" -and $intuneCertificate) {
    Write-Output "Device is enrolled in Azure AD and Intune."
    exit 0
} else {
    Write-Output "Device is not enrolled in Azure AD or Intune."
    exit 1
}

 Remediation Script: 

# Define the local path to the provisioning package
$ppkgPath = "testIntune.ppkg"

# Check if the provisioning package file exists
if (Test-Path -Path $ppkgPath) {
    try {
        # Apply the provisioning package silently without restarting
        Add-ProvisioningPackage -Path $ppkgPath -Quiet -ErrorAction Stop
        Write-Output "Provisioning package applied successfully."
    } catch {
        Write-Error "Failed to apply the provisioning package. Error: $_"
    }
} else {
    Write-Error "Provisioning package not found at $ppkgPath."
}

More than happy to trim this worklet for couple of likes lol.

A little something I threw together to find out the age of our MacOS computers so we know which computer to start replacing.

SO helpful to stay ahead of things! Thanks for sharing @slammert! Sending you a DM so we can get you a Lego Otto set! 

I use the “Windows - Enterprise Branding - Set Desktop Background for All Users” to set the Wallpaper for our Manager PCs.  Works pretty well and helps us standardize across 500+ devices.  I like being able to go to remote to any device in that group and see the same Wallpaper across each device.  It helps to see the Wallpaper as I am a heavy multitasker!

I wrote a worklet that will interrogate .NET installations and patch them as required.

I created this one to enable SSH on our MAC devices in case we need to remote in to the command line and troubleshoot a device.

Are we still doing this?  Maybe this isn't the right place for this, but I wanted to share a really simple worklet that's been very helpful. 

There are times when a user’s Automox try pop-up message seems to get stuck and never clear out.  Yesterday we had a user with the “Installing Updates: Your computer is preparing to install updates” Automox  tray message pop up that was there for 3 days, even after multiple reboots and shutdowns.  The below worklet is intended to be used “on demand” against a device with a stuck Automox agent pop up message.  This will reset and clear out any pending messages.

Always check the worklets results and outputs against the device in the “Activity Log” report first.

This is a really simple but effective worklet.

Evaluation:

(I started using an Exit 0 instead of Exit 1 with the OnDemand worklets evaluations to prevent it from running in the event its accidentally scheduled.  I also noticed when using Exit 1, the evaluation logic would result in a “command timed out” error when the device is being scanned.)

write-output "On Demand. No evaluation needed."
Exit 0

Remediation:

# Define the path to the Automox agent executable
$automoxAgentPath = "C:\Program Files (x86)\Automox\amagent.exe"

# Check if the Automox agent exists at the specified path
if (Test-Path $automoxAgentPath) {
    # Execute the command to remove all notifications
    & $automoxAgentPath notifications remove --all
    # Output a success message
    Write-Output "All AutoMox tray notifications have been removed."
    exit 0
} else {
    # Output an error message if the agent is not found
    Write-Output "Error: AutoMox agent not found at $automoxAgentPath"
    exit 1
}

Maybe im missing something here, but is there not a way for me to see peoples replies in this thread?  Most of these shared worklet posts have many replies but for the life of me, i cant figure out how to see them.