Install Google Drive File Stream - System Extension Blocked

Still having issues with this. Getting this pop up telling us we need to approve it in Security and Privacy area. 

When we go to Security and Privacy it isn't listed to allow. 

Odd thing is we just setup a new MAC before it got put into DEP and Google Drive worked fine. It stopped working as soon as we wiped it and put it through DEP and had Jamf manage it. I've gone through each Profile on jamf and removed them from the MAC one by one and the only ones that are left on there are the default ones that Jamf installs. 

@Geissbuhler@konstantinb  hi - i'm going to try the following system extension config profile on Big Sur M1 @ Intel machines.  Let me know if any of it is extra stuff that i shouldn't need.

The third image is a little smaller because i wanted to include the whole 'system extensions' section in 1 screenshot.

Having the same issue as the rest with intel macs on Big Sur, real head scratcher. Tried so many different settings in sysext but can't find a silent way to get this to work without a users manually accepting the new sysext and rebooting. 

I manually accept the system extension but when i go to terminal and put in systemextensionsctl list

i do not see anything for google drive !!!!  does anyone else see this?

my system extension config profile doesn't work

@Geissbuhler i'm testing with the PPC settings and the System Extensions settings - but only the 'allowed system extensions'  like you have in your images.

do you see the system extensions listed in your terminal when you put in the command systemextensionsctl list ???

Any update to this matter? Have a Intel MBP 11.6 where the user has nothing to approve in Sys Prefs...

Our issues was we had multiple PPPC profiles being installed. It seems like all the PPPC settings have to be in one profile so if you have multiple bits of software that require PPPC settings then put them all into one profile. This seemed to fix it for us.

I was able to fix it by deploying the Kernel Extension as follows:

Sort of off topic/on topic, I made a thread for this but probably more useful posting it here.

I am trying to push Google Drive from Jamf using the scripts provided here, however when it asks for permissions (I am not at the point of making PPPC or system/kernal extensions), but when this pop up comes up:

"To approve, open System Preferences > Security & Privacy. Click the lock to make changes, and enter your administrator ID and password. Under the “General” tab, you’ll see that some system software requires your attention before it can be used. After you give approval, restart your computer."

There is no "allow" and Google Drive does not appear in the General tab where you would generally allow this.  Has this happened to anyone/have any tips on how to resolve this?

We have seen this and the only fix for us was to deploy the kernel extension per my screenshot above. Since Google Drive is widely used in our Org - it was necessary to deploy it to all Macs.

You could try resetting all your kext approvals in Recovery via Terminal and:
kmutil trigger-panic-medic -R “/Volumes/Macintosh HD”

All previously installed kexts will prompt the user to re-approve them when they are loaded or installed.

I missed your response above with the config file, it would perfectly.  Thanks you for sharing.

@kevin_v  @jlombardo  did you apply that Kernel Extension to Big Sur running macs?  did Google Drive prompt the user afterwards when they installed Google Drive for desktop?

I have Google Drive for Desktop in Self Service and whenever a BigSur user installs it there are all sorts of popups and even a restart prompt.

I have that kernel extension for Catalina

Sorry haven't heard of any additional pop-ups with the above CP in place

@kevin_v  so you have that exact same configuration profile running on a BigSur intel Mac and it works?

I get nothing but system popups after installing google drive and then signing into my google drive account.

Once I sign into the google drive account then all the system popups to verify google drive was downloaded from google, then to approve the system extension and then restart.

so in total there is like 3 things that a user would have to do

1 - approve it was downloaded from google

2 - approve extension

3- restart

Fun fact, if you mess up your hosts file, Google Drive will fail to load on an M1 Mac (macOS 12.2) and complain about the system extension, despite having a PPPC profile.

I had to regenerate the "127.0.0.1 localhost" definition before Google Drive would load off-campus (for some reason it would load fine on the campus network but not offsite).

Just leaving this here in case it helps another user or frustrated googler.