This message was deleted.

One thing that might help: Docker Desktop's uninstall leaves behind the

DockerDesktopVM

WSL distro and Hyper-V virtual switches. You might need to explicitly clean these up: powershell

wsl --unregister DockerDesktopVM
Get-VMSwitch | Where-Object {$_.Name -like "*Docker*"} | Remove-VMSwitch -Force

Also worth noting: Rancher Desktop on Windows installs a privileged service that requires admin rights - make sure your Intune deployment runs in SYSTEM context. For upgrading/reinstalling Rancher itself, the official approach is MSI-based removal: powershell

msiexec /x {GUID} /qn

You can grab the GUID from registry at

HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

macOS side: Podman machine VMs can persist after package removal. Before installing Rancher, you might want to: bash

podman machine stop
podman machine rm --force

For Rancher Desktop itself on macOS, the standard drag-to-trash cleanup should handle most cases, but check for leftover files in

~/Library/Application Support/rancher-desktop

Broader approach: Have you considered creating a "pre-flight" cleanup script that runs first as a separate Jamf/Intune policy? It could: 1. Detect what's installed 2. Gracefully stop services 3. Clean up networking/VMs/leftover configs 4. Remove previous Rancher installs using official methods 5. Log the state 6. Only then trigger fresh Rancher Desktop install This way the Rancher install always runs on known-clean state. What specific failure modes are you seeing? (Install hangs? Runtime conflicts? Networking issues?) Also, are you tied to Rancher Desktop specifically, or could Podman Desktop be an option? It has better conflict handling with existing Docker installs in my experience.

-> #C0200L1N1MM