Backgroud:
Google Drive uses a hard coded certificate so when SSL inspector dose it man in the middle it will force the client to drop the connection.

To solve this you have 2 options.

Option 1:
Configure SSL Inspector to Ignore the sessions you see that your Google drive client goes to.
For me in Europe it is 216.58.192.0/19

This makes so we Ignore parts of Googles infrastructure so if they switch so other parts use that segment it also will be ignored.

But this option dose not need any Client configuration.

Option 2:
Configure Google Drives Client to use "--unsafe_network"

Modify Google Drive by shortcut
From: C:\Program Files\Google\Drive\googledrivesync.exe
To: C:\Program Files\Google\Drive\googledrivesync.exe" --unsafe_network

To deploy via GPO:
Push this regkey
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run\GoogleDriveSync]
"C:\Program Files (x86)\Google\Drive\googledrivesync.exe" --unsafe_network /autostart

The bad thing with this solution is that Google Drive will always start in a "unsafe" so if the client is behind any other man in the middle situation it still will connect.

But with this option you don't need to "Ignore" any Google ranges.