

But if WebEx was installed prior to all of this, then the package receipt won't be understood or parsed by the jamf binary that's doing the uninstall work. One thing that's not clear - I'm almost certain that this uninstaller functionality relies on a package receipt being installed on a system. But it's the route I'd go - basically use Jamf Admin to index the WebEx installer which then enables the uninstall option in Jamf Pro. Obviously, you'd need to test this and if your software has already been deployed/installed (which is sounds like), this process may not work.so YMMV. On May 5th, 1992, the gaming world chang.I don't have any experience with installing or uninstalling WebEx, but for other applications that I've wanted to silently uninstall on my fleet, I've successfully been able to build (or rebuild) the installer package/dmg, make sure that I've indexed the package/dmg in Jamf Admin, which then allows Jamf Pro to silently uninstall the software via a policy. Just a reminder, if you are reading the Spark!, Spice it



Somehow it came down from MS and it wasn’t a Windows Update. The app 100% wasn’t installed in the image. Today all my Windows 11 22h2 Enterprise imaged desktops had Teams auto install itself. Powershell $productNames = "*WebEx*" ) $UninstallKeys = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall', 'HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall', 'HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall' ) $uninstallKeys = foreach ( $key in ( Get-ChildItem $UninstallKeys ) )
