Hi Walt3R, Thanks for your reply. This issue is unrelated to using third-party drivers, although I am aware of the various security-based changes to macOS that would prompt you would to bring that up. The issue is not that the user cannot approve the Dropbox Kernel Extension. The issue is that the extension is already approved via Configuration Profile and Dropbox does not notice. Because of this, Dropbox still prompts the user to manually allow the kernel extension by opening System Preferences and clicking "Allow" so that the extension so that Smart Sync can be used. This is something the user will never be able to do because the extension has already been allowed and therefore needs no approval to run, thus never shows up in System Preferences. This causes a lot of confusion among users because Dropbox is prompting them to do something that cannot be done. The only way to get out of this impossible situation is to cancel out of setting up Smart Sync (thus enabling normal syncing and causing the app to start downloading everything) and then going into the Dropbox app settings and enabling Smart Sync there.
... View more
Starting with macOS 10.13.2, Apple gave MDM administrators the ability to automatically whitelist any desired Kernel Extensions so that the user would not be prompted to allow the extension manually. We do this to our machines in the field and, when enabling Smart Sync, Dropbox does not seem to notice that it's extension is already whitelisted. The user is still prompted to Manually Allow the Dropbox System Extension which they can't do because the extension has already been allowed (the option to manually allow doesn't show up in System Preferences). This puts them in a situation where they can only enable Smart Sync by canceling the Allow System Extension Prompt from Dropbox and clicking that they don't want to use Smart Sync, and then going into the Dropbox app settings and enabling Smart Sync in there. Please fix this so that Dropbox can notice that it's system extension is already approved and not prompt to user to allow it.
... View more