PPPC utility download here

Config profile with Approved Kernel Extensions payload.

We do exactly what @cbrewer does and use a PPPC entry in the same profile.

I don't use jamf yet, I remotely kick the script, so I wondered if something like that could be edited in the script?

@cbrewer solution worked even without PPPC configs.

I actually configured it like you but I still got this notification if I started Google FS for the first time. Did I something wrong?

@svallas With the release of the rebranded Google Drive File Stream, it is now called Google Drive. I had to update your script to accommodate for this:

#!/bin/zsh



# Make temp folder for downloads

mkdir "/tmp/googledrive"

cd "/tmp/googledrive"



# Download Google Drive

curl -L -o "/tmp/googledrive/GoogleDriveFileStream.dmg" "https://dl.google.com/drive-file-stream/GoogleDriveFileStream.dmg"



# Mount and install GoogleDriveFileStream.dmg

hdiutil mount GoogleDriveFileStream.dmg

installer -pkg "/Volumes/Install Google Drive/GoogleDrive.pkg" -target "/Volumes/Macintosh HD"



# Tidy up

hdiutil unmount "/Volumes/Install Google Drive"

sudo rm -rf "/tmp/googledrive"

I deployed the same config profile @cbrewer mentioned but I still get the popup window asking to approve it from system preferences !!

Anybody managed to fix it ?

interested in this too!

Be mindful, Kernel Extensions are 10.15 while System Extensions are 11.
@Flaurian @MacJunior

Yes, I already found it out but thanks to clarify it. I also checked Google working on a new tool for Google Drive to combine Drive and Backup as one product. So, fingers crossed it using System Extensions.

Hello,

same problem as Flaurian, what ever i set up, i still have the approval asking.... but with the message "Google, Inc has been blocked" :'(

Adding some things here that can hopefully help someone. I modified the script posted by @McLeanSchool so it will still install File Stream even if the Volume Name is unique and has a space in it (ex. "Joes Mac" instead of "Macintosh HD"). I tested and this is working on multiple MacBooks via Jamf on Catalina and Big Sur (caveat below).

#!/bin/zsh



# make temp folder for downloads

mkdir "/tmp/googledrive"



# change working directory

cd "/tmp/googledrive"



#download Google Drive File Stream

curl -L -o "/tmp/googledrive/GoogleDriveFileStream.dmg" "https://dl.google.com/drive-file-stream/GoogleDriveFileStream.dmg"



# Mount the DMG

hdiutil mount GoogleDriveFileStream.dmg



# Get Volume Name

Volume=$(diskutil info / | grep "Volume Name:" | awk '{print $3,$4,$5,$6}')



# Install Google Drive

sudo installer -pkg /Volumes/Install Google Drive/GoogleDrive.pkg -target "/Volumes/$Volume"



#Tidy Up

hdiutil unmount "/Volumes/Install Google Drive"

sudo rm -rf "/tmp/googledrive"

In Big Sur I still haven't found a way to approve the necessary System Extension via Jamf...but it is possible to open System Preferences, Security and Privacy, General Tab, click Allow, reboot...then it works great. Hoping someone can find a fix or this is resolved by Google at some point.

@mosermat Had to Update the script a bit in more than the places listed above:

#!/bin/zsh



# make temp folder for downloads

mkdir "/tmp/googledrive"



# change working directory

cd "/tmp/googledrive"



#download Google Drive File Stream

curl -L -o "/tmp/googledrive/GoogleDrive.dmg" "https://dl.google.com/drive-file-stream/GoogleDrive.dmg"



# Mount the DMG

hdiutil mount GoogleDrive.dmg



# Get Volume Name

Volume=$(diskutil info / | grep "Volume Name:" | awk '{print $3,$4,$5,$6}')



# Install Google Drive

sudo installer -pkg /Volumes/Install Google Drive/GoogleDrive.pkg -target /



#Tidy Up

hdiutil unmount "/Volumes/Install Google Drive"

sudo rm -rf "/tmp/googledrive"

This at least seems to be downloading and installing properly now.

Now to work on getting Auth to happen after launching the app, if anyone has any tips, please reply

After running the most recent script the volume is not removing from the desktop. Does something need to be altered?

Tidy Up

hdiutil unmount "/Volumes/Install Google Drive"

it logs as successful

installer: Package name is Google Drive
installer: Installing at base path /
installer: The install was successful.
"/Volumes/Install Google Drive" unmounted successfully.
sudo rm -rf "/tmp/googledrive"

I'm not having luck the the Kext CP and PPPC. Does something need to change now that its been renamed from Google Drive FileStream to Google Drive for Desktop? NM, got it working.

@KSibley what was the solution?

Anyone got an updated version of the PPPC config they can share? We're still getting Google Drive asking for system extension approval on big sur.

Hey @RLR ,

we use the following:

Privacy Preferences Policy Control - App Access

Identifier

com.google.drivefs

Bundle ID

identifier "com.google.drivefs" and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = EQHXZ8M8AV

APP OR SERVICE:

Accessibility: Allow

System Extension:

Google Drive - Allowed System Extensions - EQHXZ8M8AV - com.google.drivefs.filesystems.dfsuse

Hope that works for you :). Feel free to give some feedback!

@RLR  and @konstantinb    since it's not GOOGLE DRIVE FILE STREAM anymore but changed to GOOGLE DRIVE FOR DESKTOP  are the values to create the  'system extension' the same? I used the values that @konstantinb provided in the reply above two weeks ago.  (images attached of my sys ext config profile)

specifically these values below, do they stay the same?  i'm thinking maybe 'drivefs' would reference 'file stream' but since it's not file stream anymore i'm kinda just assuming.

---- com.google.drivefs

----- com.google.drivefs.filesystems.dfsuse

Pulling the App "Google Drive" Into PPPC Utility it shows the same as before, so looks like it is indeed still using the com.google.drivefs. I wondered the same thing 🙂

so does my Config Profile settings look correct?

is that similar to your config profile?

does it work for both intel and M1  macs running Big Sur?  I'm testing but wont be able to for the next 2 weeks.

Testing on an Intel Machine in a bit need to wipe to fully test properly, will post results when done. I have the same as you plus a few others, which I likely do not need, The diff is that I approved both com.google.drivefs and com.google.drivefs.filesystems.dfsuse in the system extension, so we will see what happens. If it works I will post screenshots.

Also Testing this on macOS Monterey Beta FYI, 1 Big Sur Intel and 1 Monterey.