This guide will help administrators ensure that Rippling MDM and associated components are completely removed from macOS devices, preventing conflicts or interference with Swif's MDM-installed profiles.
Step-by-Step Guide
Step 1: Create a Command in Swif
Follow the instructions provided here to create a new command. When defining the command, use the following shell script:
#!/bin/bash
sudo launchctl unload /Library/LaunchDaemons/com.rippling.*
USER=$(stat -f "%Su" /dev/console)
su $USER -c 'launchctl remove com.rippling.tray'
sudo launchctl remove com.rippling.tray
sudo rm -rf /Applications/Rippling.app/
sudo rm -rf '/Library/Application Support/Rippling/rippling_agent.json'
sudo rm -rf /Library/LaunchDaemons/com.rippling.*
sudo rm -rf /Library/LaunchAgents/com.rippling.*
sudo rm -rf /opt/rippling /opt/rippling-readonly
sudo rm -rf /usr/local/rippling
# To remove any profile installed by Rippling
for identifier in $(sudo profiles -Lv | grep profileIdentifier | grep 'com.rippling.*' | awk '{print $4}' )
do sudo profiles -R -p $identifier
done
rm -rf '/Applications/msc.app'
rm -f /Library/LaunchDaemons/com.rippling.munki.*
sudo profiles -R -p com.rippling.munki
Step 2: Configure the Command to Run Every 30 Minutes
Set the command frequency to execute every 30 minutes, ensuring it regularly checks and removes any lingering Rippling files or profiles.
Step 3: Create a Device Group
Create a dedicated device group or use an existing device group in Swif.
Assign the previously created command to this device group.
Add all devices from which Rippling should be removed into this group. The script will automatically execute on these devices according to the set schedule.
Verification and Troubleshooting
Regularly check Swif’s command execution status reports to verify successful command deployment.
Manually verify on macOS devices by ensuring Rippling and associated files and profiles no longer exist.
For further assistance or troubleshooting, please contact Swif Support.