Google File Stream 44.0.10.0 Problems

[Michael]

I managed to track down a File Stream 44.0.12.0 install and asked the end user to sign out and sign in using a .sch.uk account. Same problem and had to uninstall File Stream, reboot and re-install File Stream 43.0.80.0. File Stream then works as expected.

[Ratcliffepg]

Oh dear.... Google are still working on our support call for this issue.

[Michael]

I've tested File Stream 44.0.10.0 with a .co.uk domain and it works absolutely fine signing in.

[Michael]

Nope. Still saying it's up to date on 43x.

 

If you download from here Google have now made available 44.0.10.0. Just as well I still have a copy of 43.0.80.0

[Ratcliffepg]

Work with a hotmail or outlook email address as well.... but not with our .com address.....

[LeMarchand]

Don't know if they've fixed that version, but a net, org and com address all signed in OK.

[Michael]

Don't know if they've fixed that version, but a net, org and com address all signed in OK.

 

I've concluded similar - any chance you can try a .sch.uk address?

[LeMarchand]

I've concluded similar - any chance you can try a .sch.uk address?

 

Sorry - that's all the Google address types I have access to.

[RLR]

Have you tried changing the auth type to browser to see if that works: https://support.google.com/a/answer/7644837?hl=en

 

ForceBrowserAuth

[Ratcliffepg]

Now on Version: 44.0.12.0 still cannot signin with a .com address

[sparknm]

same issues here (.org.uk domain) across 2 campuses - added a thread to google community but as yet nothing helpful - https://support.google.com/drive/thread/86329442?hl=en

 

strange thing is those with a roaming profile seem to have escaped the silent upgrade to 44.0.10.0 unscathed - probably going to regret saying that tomorrow!

most users here have a mandatory profile, but once the machine "breaks" even a local admin user has the same 404 issues.

 

as with everyone else 43.0.8.0 works fine in all settings until the update to 44.0.10.0

[Michael]

Have you tried changing the auth type to browser to see if that works: https://support.google.com/a/answer/7644837?hl=en

 

ForceBrowserAuth

 

Unfortunately after extensive testing, authenticating via the browser makes no difference.

[Michael]

same issues here (.org.uk domain) across 2 campuses - added a thread to google community but as yet nothing helpful - https://support.google.com/drive/thread/86329442?hl=en

 

strange thing is those with a roaming profile seem to have escaped the silent upgrade to 44.0.10.0 unscathed - probably going to regret saying that tomorrow!

most users here have a mandatory profile, but once the machine "breaks" even a local admin user has the same 404 issues.

 

as with everyone else 43.0.8.0 works fine in all settings until the update to 44.0.10.0

 

Local or roaming profile, standard or admin user, if you're signed in using version 43.0.80.0 and FS silently upgrades to 44.0.10.0 or 44.0.12.0, it will continue to work. It only becomes an issue if a user manually signs out, or they try to login to versions 44.0.10.0 or 44.0.12.0 from the beginning.

 

According to Google v44 is just a bug fix release, but it very much appears to be a bug creator release. The error is 'Account restricted', so automatically I think 'permissions' or somehow FS v44 handshakes differently to FS v43 and creates the error. I think it's very far from just being a bug fix release.

[Ratcliffepg]

We have received this solution from our support call with Google, I can confirm making the change below in Admin console resolves the issue for us.

 

I request you to turn ON this setting in the Admin Console:

 

Apps > Additional Google Services > Access to additional services without individual control > Service status.

 

I had a similar case where turning this setting ON resolved the Drive File Stream issues. Note that there will likely be some propagation delay before the change kicks in (max. 24 hrs).

[Michael]

We have received this solution from our support call with Google, I can confirm making the change below in Admin console resolves the issue for us.

 

I request you to turn ON this setting in the Admin Console:

 

Apps > Additional Google Services > Access to additional services without individual control > Service status.

 

I had a similar case where turning this setting ON resolved the Drive File Stream issues. Note that there will likely be some propagation delay before the change kicks in (max. 24 hrs).

 

Interesting - I can confirm my working tenancies have this switch on/enabled already. Sounds promising!

[LeMarchand]

I request you to turn ON this setting in the Admin Console:

 

Apps > Additional Google Services > Access to additional services without individual control > Service status.

 

interesting... we already had this set. Wondering if I actually paid attention to one of the emails they send out about changing things. Bit unlikely, TBH!

[Michael]

I can confirm 44.0.12.0 now working with an .sch.uk account, it does appear to be that setting.

 

I tried 30 mins after enabling it

[Michael]

I have to be honest and say I think Google's at fault here.

 

I have Core services (including Drive) set to enable on one page, and then I have to enable a setting under 'Additional Google Apps', even though Drive is a Core app

 

If someone can explain this logic, I'll buy them a drink.

[sparknm]

Seems to work for both our campuses on versions 44.0.10.0 and 44.0.12.0

Hope it works for you too !

[Michael]

Just to confirm all's well here, not a single issue reported since.

[k-strider]

44.0.14.0 Working here with .sch.uk as others have said had to turn on access to file stream in the admin console