![]() ![]() Today, users in our test group are reporting seeing a message appear at random, with the title bar reading "Google Drive Error". Shouldn't be an issue, since from what we've seen part of the Google Drive migration wizard is that Backup and Sync is disabled (but still installed). Because of how we are doing things, we have opted to leave Backup and Sync installed on all machines until we are happy that users have been migrated over to the new client. We have started testing our deployment and all is going fairly well. On my test machine with File Stream 35.0.13.0 installed, the Google Drive deployment silently replaces the old File Stream client and retains the auth token- the user ends up being automatically signed in to the new client. The upgrade process from File Stream to Google Drive is much simpler / smoother (not surprising, seeing as that is what the new unified client is based on). Potentially the work flow for us will be to instruct users to select the 'not now' option when prompted to uninstall Backup and Sync, and then action the uninstall via SCCM at a later date when we are happy with the uptake of the new Drive client. ![]() With the above scenario, even without removing the old Backup and Sync client, it does disable it. I'm attempting to find out from Google if this first run process can be customised in any way, so that we can skip over options that won't apply to our users. Which is a bit pointless for our users who don't have admin rights. The 'guided flow' process works fairly well, but one immediate issue I can see is that near the end of the process it prompts users to remove Backup and Sync. Initial testing (deploying the new client to machines that have an in use Backup and Sync installation). I'll post what I end up going with here as well. Keen to hear from any of you that are impacted by this, and how you plan to manage the transition. So the aim (as always) will be to automate as much of the transition from Backup and Sync to Google Drive as possible. From my initial reading of Google's recommendations there's a fair bit of 'instructing the user to do the thing' Now, this may be unavoidable, but if your users are like mine I try and involve them in the app deployment / configuration process as little as possible. However, for replacing the Backup and Sync app it sounds a bit more involved. The File Stream users have already been migrated to the new Google Drive app (which was fairly straight forward- as long as their File Stream app was reasonably current, the new app cleanly replaces it without losing the existing authentication token, so the users don't even need to sign back in). More details in this blog post:įor myself, we have a mixed environment with some users on the old File Stream app, and some on Backup and Sync. To continue syncing with Drive and/or Google Photos, users will need to transition to Drive for desktop.Īs many of you are no doubt aware, the new unified file syncing app from Google now has an official timeline to replace the 'legacy' Backup and Sync app. Starting October 1, 2021: Any users still on Backup and Sync after that point will no longer be able to sign in to Backup and Sync. Starting August 18, 2021: Any users still on Backup and Sync will start to receive in-product notifications prompting them to transition to Drive for desktop. Starting July 19, 2021: Backup and Sync will support a guided flow to help users transition onto Drive for desktop.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |