Skip to main content

Hey all, looking for some help or confirmation here. I’m managing lab Macs (M1/M2, macOS Sequoia) where user accounts are deleted at reboot. I want to stop OneDrive from auto-launching that “Set up OneDrive” window every time a new user logs in — but still allow students to launch it manually if needed.


 


Here’s what I’ve tried so far:


 




  • Scoped a Jamf Managed Login Items config profile with a rule to block application.com.microsoft.OneDrive(Label Prefix, team ID UBF8T346G9)




  • Also added a rule to block com.microsoft.OneDriveLauncher just in case that agent is still around




  • Tried both Jamf’s GUI approach and uploading a signed com.apple.servicemanagement profile directly with <Authorization>false</Authorization> rules




  • Even layered on launchctl disable + login hook scripts to unload and delete the LaunchAgents




 


But the wizard keeps launching for brand-new users, even when all signs say the login item is blocked. Nothing shows in launchctl list, and the ServiceManagement profile looks like it’s applied properly (profiles -L shows it present).


 


Has anyone had success with suppressing this first-run behavior without breaking OneDrive completely?


Appreciate any pointers — this one’s driving me nuts.

That is strange that it auto launches on you...our existing setups do not auto launch the setup wizard...do you happen to have the one drive.app in one of your autolaunch login items?

OneDrive uses a LaunchDaemon, you could delete it but that would prevent it from ever auto launching for any user on the device. We dont get these prompts and everything is auto configured. Do you have a Configuration Profile configuring OneDrive? 


https://learn.microsoft.com/en-us/sharepoint/deploy-and-configure-on-macos

OneDrive uses a LaunchDaemon, you could delete it but that would prevent it from ever auto launching for any user on the device. We dont get these prompts and everything is auto configured. Do you have a Configuration Profile configuring OneDrive? 


https://learn.microsoft.com/en-us/sharepoint/deploy-and-configure-on-macos


We do have a Custom Settings profile for com.microsoft.OneDrive (pushing keys like OpenAtLogin = false, DisableTutorial = true, etc.), but since the 24.113 update OneDrive ignores that old plist and uses the new Background Services API instead.


 


To manage that we deployed a com.apple.servicemanagement payload blocking every OneDrive helper label (dynamic SMAppService entries, the “Microsoft OneDrive” label, and the Launcher agent) with Authorization = false. We even confirmed via profiles -P that the profile is installed and via launchctl print-disabled gui/$(id -u) that the updater daemon is disabled—but only the updater respects it. The Launcher and SMAppService helpers still fire the first-run wizard.


 



 


Why we haven’t just nuked the LaunchDaemon


Deleting /Library/LaunchDaemons/com.microsoft.OneDriveUpdaterDaemon.plist would stop OneDrive from ever launching (and thus kill the wizard), but it also prevents students from opening OneDrive manually when they need it. We need OneDrive available on demand, just not auto-configured for brand-new users.


 



 


Any hints on how to catch that Launcher agent (or the plain “Microsoft OneDrive” SMAppService record) before it fires its first-run window would be hugely appreciated. At this point we’re down to kill-on-login scripts just to stomp it out—but would love a cleaner profile-only solution if anyone’s found one.

That is strange that it auto launches on you...our existing setups do not auto launch the setup wizard...do you happen to have the one drive.app in one of your autolaunch login items?


I double-checked System Settings → General → Login Items → Allow in Background on a fresh test account—OneDrive.app is not listed at all. No manual login-item entry for OneDrive, and launchctl list | grep -i OneDrive shows only the helpers, not the app itself.

Reply


Terms & ConditionsCookie settings