So Far worked perfectly on macOS Monterey, Testing Big Sur momentarily

No go for Big Sur, **bleep**!

Ok So Here is what I have:

Big Sur on M1 = Works
Big Sur on Intel = Fails
Monterey Beta (21a5506j) on Intel = Works
Monterey Beta (21A5304g) on M1 = Works

My setup is a bunch of me reading various items and is likely overkill, I was going to make a bunch of settings and then if it worked I could pull some back, just keep that in mind.

(Update) same results after changing a mistake i had in the screenshots below:

com.google.drivefs.filesystems.dfsuse

Any Other findings from People Specifically with Intel Macs on Big Sur would be greatly appreciated.

@Geissbuhler  so you applied that single config profile to both intel & m1 ?  

so no separate config profile for each arch type? (probably not necessary)

Correct exact same on all of the above, only intel and Big Sur combo seems to fail. So weird

So far this config did work for all our clients. But I will try to check it again on M1 next weeks. The Config i also pulled from the new client the name has just changed but the config is still the same basically.

@konstantinb @Geissbuhler  are you applying this Google Drive system extension config profile to only Big Sur computers?

and a seperate Google Drive kernel extension config profile to Mojave and Catalina computers?

also the system extension you configured, I see the pictures you posted, does the config profile have 2 'Allow Team IDs and System Extension' sections in it?

@tcandela Theoretical yes you would need to. 

The Systems extensions are as following:

@konstantinb ok thanks. 

I'm confused with the @Geissbuhler images he attached to his reply specifically the 5th image that has the 'driver extension' box checked. Do you have that in your system extension configuration?

here is the image i'm talking about, it looks like another section of 'Allowed Team ID's and System Extensions' was added to the same config profile

I got one to work with an intel computer with 10.15 on it with a kext. I noticed that there is a letter missing in the com.google.drivefs.filesystems.dfsuse it should be 

com.google.drivefs.filesystems.dfsfuse  notice that there is a F missing from the first one.  Never got anything about allowing and never had to go security and privacy to do anything

Thanks! Actually you are totally right this is missing.

Yes in my test environment I was basically trying anything, hence the comment where I try way too much and scale back later. The way those pics are listed, is the top pic is the Config Profile as whole, then the next is of the PPPC Payload, The next is the System Extensions payload, the following snaps are of the individual sections within the System Extensions Payload.

I read early on that if you are unsure with System Extensions which bit works, like in this instance here, trying to troubleshoot, you start with approving the team as a whole, Then start on the individual extensions, Then the types, if your big old way overkill sys extension works, scale it back like maybe delete the Team as a whole bit of the payload, and get right to the bits that you actually need.

This is not in prod

Would love to know what I actually need, hence the testing above. This is currently working on Big Sur with M1, but not working on Big Sur with Intel.

Thank you for that trying now

I haven't tried it on a Big Sur computer yet.   I was trying to find a solution for my 10.15 computers. This is a kernel extension so i know it will not work on Big Sur I am making a new config profile for my Big Sur computers will let you know how the testing is going after I get that one built. 

Trying your Missing F right now, crossing fingers

Even with that and a reboot, I am still seeing this:

With M1 and Big Sur

@Geissbuhler  those are the same popups i get when installing google drive for desktop. I have users install google drive via self service (using the pkg provided directly by the google drive download).

  I haven't applied any system extension config profile yet.  

Did you apply the system extension config profile before installing google drive?  

are you testing on both intel and m1 ?

For me on my M1 with Big Sur i didnt have any system extensions profile sent to the computer just installed it and then it launched.  On my Intel with 10.15 I put the profile on before i installed and there was no pop up.   I then installed drive before the profile was sent to the computer and had a pop up.  I quit Drive and then pushed the KEXT profile and relaunched drive and then I didnt get any pop ups.   I am getting ready to try it on a Intel with Big Sur.

Currently still at with the System Extension and PPPC config profile like above:

Big Sur on M1 = Works
Big Sur on Intel = Fails
Monterey Beta (21a5506j) on Intel = Works
Monterey Beta (21A5304g) on M1 = Works

Yes I we are doing kernel extension for Catalina and Mojave, and a separate Config Profile with System Extension for Big Sur and Monterey Beta.

Still Nada with Big Sur and Intel

Iam still trying also still havent found anything that is working

I know this was a while back, but If you are still looking you can get the newest version here:

https://github.com/jamf/PPPC-Utility/releases