Jump to content

Recommended Posts

Posted

Has anyone had a go at using the new 'Restrict File Stream to company devices' yet?

 

I was trying to workout how this setting would effect users that already have File Stream installed, if their laptop has not already been added to the company devices list, and so far it seems to do nothing.

 

So in apps > drive > features > file stream, it says that devices need to be added as company devices, which my test computer is not and file stream still works, but it is listed as approved in End point.

 

Do you think this is a glitch, or just the fact that my test computer was already listed in end point before the new restricted access rolled out.

 

Anyone else had a play yet?

Posted

Not had so much of a play yet, but I found that some devices were already approved within the endpoint section, despite the verification extension or msi not being present on the machine.

 

Issue I'm having atm is that as we have some users will login to multiple devices and after 2 or 3 devices being accessed from the same user, it then starts sending out emails to themselves and administrators of G-Suite informing that device is currently 'pending approval'.

 

Oh, and the msi they ask you to deploy to workstations also doesn't seemed to be recognised by the endpoint verification browser extension. :confused:

Posted
I found that some devices were already approved within the endpoint section, despite the verification extension or msi not being present on the machine.

 

Looks like nearly all our computers are listed as approved in the endpoint section, also without anything having been deployed. I did have auto approval enabled at some point. Perhaps it's an either or situation, you either need to approve a device (manual or auto in G Suite) or you need to deploy the MSI or Chrome extension. Otherwise I can't see how the devices are already listed.

  • 10 months later...
Posted

I'm testing this now and I have File stream to start on login, however the popup to login doesn't show for newly logged in users until after they have clicked on the Application and signed in. If they sign out of Drive Stream and logoff \ login the popup shows how I would expect it to.

Is this normal behaviour and do I have to expect end users to run the app themselves ?

Posted

Think I've got this where I want it,

 

Set HKEY_LOCAL_MACHINE\SOFTWARE\Google\DriveFS\AutoStartOnLogin to 0

 

and create a new string value under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run pointing to the Drivestream link at C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Drive File Stream.lnk

  • Thanks 1
Posted (edited)

What're people doing with regard to GDFS folder structure and creating shortcuts?

 

We've done a small test case of it here and it's worked great, so I've told SCCM to push it out to all staff machines, but looking at the ones that already have it installed, there's a myriad of versions dotted around (42.0.10.0, 42.0.11.0, 43.0.8.0) each with their own complete structure and GoogleDriveFS.exe.

 

I tried just making a shortcut to the .lnk file in ProgramData but apparently Windows doesn't like you doing that.

 

Edit: Closest I've got is the previous post with the reg keys, but that throws the software up and login and I'd rather users choose whether to use it or not.

Edited by Garacesh
Posted
Am I missing something or does the Google FS link in the startmenu do the same thing ? I guess that updates itself when the app does ?

 

Too many bits of software clutter themselves in the root of the Start Menu, so we have Remove common program groups from Start menu enabled.

  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...