Tag Archives: Drive File Stream

Real-time presence in Microsoft Office to become available October 17th

On October 17th, 2018, we’ll begin rolling out real-time presence for Microsoft Office files in Google Drive to all G Suite domains. Admin controls for real-time presence are available today.

This feature, included in Drive File Stream, will help you avoid version conflicts when editing Microsoft Office files in Google Drive. Real-time presence will let users know if another user is editing a Word, Excel, or PowerPoint file stored in Drive File Stream, in real time. This feature will start rolling out to end users on October 17th.

Avoid version conflicts when editing Microsoft Office files in Drive

Real-time presence will check to see if someone else is viewing or editing a Microsoft Office file while you have it open. It’ll alert you and them to help avoid version conflicts. When conflicts do occur, it’ll help you resolve them with a side-by-side view of the document versions, allowing you to easily merge them into one up-to-date file. For more details and to fully understand the feature:



Admin controls available now

Admins can choose whether to make real-time presence available to their organizations. Admin controls are live today and on by default. Real-time presence can be disabled for an entire domain or for individual organizational units (OUs) within a domain. To change the setting, go to Apps > G Suite > Drive and Docs > Features and Applications > Allow users to enable real-time presence in Microsoft Office from Drive File Stream in the Admin console.

For more granular control, admins can also deploy a configuration setting to enable or disable real-time presence in Microsoft Office on a per-machine basis.

End user feature available after October 17th

On October 17th, Drive File Stream users will begin to see an educational message when opening Office files stored in Drive File Stream. This message (pictured below), explains that real-time presence helps users see who is editing Microsoft Office files stored in Drive. After opting in to this feature, users will begin to see real-time presence status indicators in the bottom right-hand corner of Word, Excel, and Powerpoint windows that are focused in the foreground.
On macOS, enabling real-time presence may require users to grant accessibility permissions. Additionally, some users may be asked to confirm their identity before using real-time presence, by logging in with their G Suite account. Starting October 17th, employees at G Suite organizations will be able to visit our Help Center to learn more about how to use real-time presence.

Launch Details
Release track:
  • Admin console setting launching to both Rapid Release and Scheduled Release today
  • End user feature included in version of Drive File Stream that will become available to both Rapid Release and Schedule Release on October 17th

Editions:
Available to all G Suite editions

Rollout pace:
Full rollout (1–3 days for feature visibility)

Impact:
Admins and end users

Action:
Admin action suggested/FYI

More Information
G Suite Updates blog: Avoid version conflicts when editing Microsoft Office files in Drive
Demo video: Real-time presence in Microsoft Office
Help Center: Use work or school files on your computer with Drive File Stream


Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates

New Content manager role coming to Team Drives

In October 2018, we will make several changes to membership roles in Team Drives. Most importantly, we’ll add a new “Content manager” role, which will make it easier to manage files in Team Drives. When it takes effect, Content manager will become the default role for new members of a Team Drive.

Many organizations have asked for this role in Team Drives. To help them take full advantage at launch and reduce manual work, we’re offering a one-time migration to move users who currently have “Edit access” to the Content manager role. G Suite admins can opt in to this migration by filling out this form before September 26th.

Content manager role will make file management easier 

Users with the Content manager role will be able to edit, reorganize, and delete Team Drive content, but they won’t be able to modify Team Drive membership or settings. Content manager will replace “Full access” as the default role for new Team Drive members.

There are some important differences between the permissions for Content managers and users with Edit access that are particularly helpful if you use Drive File Stream:


  • Unlike users with edit access, Content managers will be able to reorganize and delete files in a Team Drive. 
  • Content managers will have read and write access to files in Drive File Stream, allowing them to easily manage Team Drive files through their computer’s file system or the Drive web interface. Users with Edit access won’t have this access and so will still need to access Team Drive files on the web to edit them. 


Optional: Enroll your organization in a one-time role migration by September 26th 

We recommend organizations with Drive File Stream enabled use the new role and consider opting in to the migration. However, no action is required in response to these changes. If you don’t do anything, the roles of Team Drive members in your organization will not change in October. If you opt in to the migration:


  • All individual users and groups in your organization who are members of Team Drives with “Edit access” will become “Content managers.” 
  • External users who are members of Team Drives in your organization will not be migrated, unless they belong to a group that also contains internal users. If they belong to a group that also contains internal users and that group is a member of a Team Drive with “Edit access”, those external users will be migrated to the Content manager role. 


To opt in to the migration, complete this form by September 26th, 2018.

To access the form, you must be a G Suite admin for your organization and have received an email with the subject line “Introducing a new role in Team Drives.” If you received this email but can’t access the form, please contact G Suite support and reference ID: 78256060.

Migration will take place in October 

If you fill out the form above and enroll your organization in the one-time migration, it will start on October 15th, 2018, for Rapid Release domains and October 29th, 2018, for Scheduled Release domains. It will be a gradual rollout, so it may take up to 15 days after those dates to reach all domains. When the migration takes place, users and admins will not be explicitly notified, but will be able to see the different role description when they look at their Team Drive membership.

Launch Details 
Release track:

  • Migration applications open now until September 26th, 2018 
  • Migration will start on October 15th for Rapid Release domains and October 29th for Scheduled Release domains (for organizations who’ve opted in only) 


Editions:
Available to G Suite Business, Enterprise, Education, Nonprofit, and Enterprise for Education editions only

Rollout pace: 
Gradual rollout (up to 15 days for feature visibility)

Impact: 
Migration decision applicable to admins only Full launch in October applicable to all end users 

Action: 
Admin action suggested/FYI and change management suggested/FYI


More Information 
Learning Center: Get started with Team Drives
Form to enroll in one-time Team Drives role migration


Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates

Avoid version conflicts when editing Microsoft Office files in Drive

We’re adding a new feature to Google Drive that lets you see when other people are editing files in Microsoft Office products. This will help you collaborate better and avoid version conflicts. This feature uses the Drive File Stream cloud sync solution. Make sure you’re using Drive File Stream to take advantage.

Avoid version conflicts 

When you open a Microsoft Word, Powerpoint or Excel document in Drive, we’ll check if anyone else is currently editing the document. We’ll then let you know if it’s safe to edit or if you should wait. Drive may tell you:


  • Safe to edit: No one else is editing. 
  • Wait to edit: Other people are editing, so your edits will create multiple, conflicting versions. 
  • New version created: Another editor saved a newer version of the file. 
  • New version created (conflict): While you were editing the file, another editor also edited it. Click for a side-by-side comparison to help you create one version.
See when it's safe to edit a file


If conflicts do happen, compare and resolve side by side

If version conflicts do occur, Drive will show the two document versions and their changes side by side. This unique feature will help you quickly merge the multiple versions into a single, up-to-date document.

Compare conflicting versions to create one up to date document 

We believe this feature will go a long way to eliminating “document collisions,” and reduce the frustration and duplicative work caused when they do occur. We also hope that this makes it easier to collaborate on more file types in Drive.

Use Drive File Stream to see this feature 

This features is a part of Drive File Stream. Drive File Stream is a cloud file sync solution that we believe is best for most G Suite organizations. It lets you stream My Drive and Team Drive files directly from the cloud, which:


  • Makes Drive files available for offline access 
  • Frees up disk space and network bandwidth 
  • Minimizes the amount of company data stored on users’ hard drives 
  • Enables new features such as version conflict alerts for Microsoft files 


See the Help Center for how to choose and deploy a sync solution for Google Drive.

Launch Details 
Release track:
Launching to both Rapid Release and Scheduled Release

Editions: 
Available to all G Suite editions 

Rollout pace: 
Gradual rollout (up to 15 days for feature visibility)

Impact: 
All end users

Action: 
Change management suggested/FYI



Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates

Important additional information about the legacy Google Drive desktop sync client shutdown on May 12

As previously announced, the old Drive desktop sync client for Mac and PC—a feature officially known as “Google Drive for Mac/PC”—will start to shut down on May 12th, 2018. After May 12th, the sync client may not work for your organization.

Here are some important things to know: 

1. If you haven’t already, upgrade to a newer sync solution. 

This shutdown is happening because we have better sync solutions available for Drive users. G Suite organizations still using Drive for Mac/PC should transition to Drive File Stream. For non-G Suite users, we recommend Backup and Sync. For more information on choosing the right sync solution for your users, check out this Help Center guide.

2. The turn-down will be gradual. 

We will start the shutdown process on May 12th, but it will be gradual and may take several weeks to impact all organizations. After May 12th, however, updates to files may stop syncing between your users’ computers and Drive, so we recommend upgrading by that date.

3. Once the client shuts down for you, the Google Drive folder will stop syncing. 

When the legacy Google Drive desktop sync client shuts down, it will stop syncing the Google Drive folder to Google Drive. The local Drive folder (containing users’ files) will not be deleted from the machine, but changes made inside this folder will no longer sync to Drive. We don’t recommend editing files inside of this folder after May 12th, as it could lead to users misplacing their edited files (not realizing that this folder isn’t syncing to Drive). To avoid confusion, you may want to delete the legacy Google Drive folder. By default, this folder is located at:

  • Windows: “C:\Users\%USER%\Google Drive” 
  • macOS: “/Users/$USER/Google Drive” 


Use caution when deleting this folder, as it may contain content that has not yet been saved or synced.
In addition, after the legacy desktop client shuts down for you, the app will display this dialog when it starts up:
This message will be shown to end users still using the legacy sync client after it is shut down. 

4. After May 12th, Drive File Stream will display a dialog and rename the old Google Drive folder to clarify that the old folder is not syncing. 


If a user signs in to Drive File Stream and it detects that the old Google Drive folder (from the same account) is still present on the machine, it will append “(Not Syncing)” to the old Google Drive folder, and display the following dialog:


After renaming the old Google Drive folder, Drive File Stream will display this dialog. 
If you don’t want your users to see this dialog, you may remove the old Google Drive folder before May 12th.

After May 12th, if you choose to automate the removal of “~/Google Drive/”, you should remove “~/Google Drive (Not Syncing)/” as well. Note that for users who use Drive File Stream in another language, this folder name will be localized.

It’s important to note that while this folder name change is intended to discourage users from editing files inside the old Google Drive folder, it does not prevent users from making changes in it. We strongly encourage administrators to educate their end users to use Drive File Stream, and not the old Google Drive folder.

More Information 
Blog post (Sept 2017): Drive File Stream launching to all G Suite customers 
Blog post (Jan 2018): Legacy Google Drive desktop sync client now shutting down on May 12th, 2018
Help Center: Deploy Drive File Stream
Help Center: Choose a sync solution


Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates