[go: up one dir, main page]

What’s changing 
When Google Cloud Directory Sync (GCDS) attempts to create new users, it may encounter unmanaged accounts that conflict with the accounts it’s attempting to create. In these instances, GCDS will now comply with the conflicting accounts management settings specified in the Admin console. This update helps reduce the time spent migrating user accounts to business accounts, helping to accelerate the adoption of Google Workspace and Google Cloud. Visit the Help Center for specific information on how GCDS will handle conflicting accounts based on your configured settings. 

Getting started 
  • Admins: Google Cloud Directory Sync will automatically respect your existing Admin console settings for handling conflicting unmanaged accounts. We do not recommend turning this feature off in GCDS, rather you should configure these settings as you see fit in the Admin console. Visit the Help Center to learn more about handling conflicting unmanaged accounts with Google Cloud Directory Sync, as well as unmanaged accounts in general. 
  • End users: Depending on your admin configuration: 
    • You’ll be invited to transfer your account — if accepted, your admin will have the ability to manage your account. 
    • If you do not accept the request, your admin may replace your unmanaged account with a managed one. In that case, you’ll receive a new @gmail.com address and retain your content in this unmanaged, personal Google account. 
Rollout pace

Availability
  • Available for all Google Workspace customers 
 Resources 
Labels: , , ,

What’s changing 
Google Workspace Admins can now use Directory Sync to sync users and groups from Azure Active Directory. Directory Sync is an alternative to Google Cloud Directory Sync (GCDS), which admins can use to synchronize user and group data with their Google Cloud directory without the need to manage on-prem hardware and deployments. 




Directory Sync is available in open beta, which means no beta sign-up or registration is required. Please read more about Directory Sync and its features to determine if it best suits your needs.




Additional details 
Admins can add up-to one Azure Directory connection to sync users and groups information to the Google Cloud Directory. On your Microsoft Azure Active Directory side, Global Administrator privileges are required for using this feature — this is so that full user profiles, groups, and group memberships can be “read” through in order to sync these objects into the Cloud Directory. 


Getting started 
  • Admins: 
    • To use the Directory Sync beta, go to Admin console > Home > Directory > Directory Sync. No beta sign up or registration is required. 
    • You can delegate the ability to manage Active Directory with the new Directory Sync admin user role. Use our Help Center to learn more about using the new Directory Sync. 
  • End users: No end user impact 

Rollout pace 

Availability 
  • Available to all Google Workspace customers and Cloud Identity customers
Resources
Labels: , , , ,

Quick launch summary 

You can now find and view additional information about people within your organization, your Contacts, and more across additional Google Workspace products. This information includes: 

  • Contact information, such as phone number and email address,  
  • Team and manager, 
  • Office and desk location, 
  • Whether you’ve received email from them before, and more. 

This feature is already available for Gmail, and will now be available from the following products: Google Chat, Calendar, Docs, Sheets, and Slides.

Getting started 

  • Admins: To maximize this feature, it’s helpful to have user data fully populated across Google Workspace apps. Workspace admins can populate this data in a few locations: 
  • End users: There is no end user setting for this feature. Click “Open Detailed View” while hovering over a user’s information card, or select the Contacts icon in the side panel. Visit the Help Center to learn more about using Google products side by side. 

Rollout pace 

Availability 

  • Available to all Google Workspace customers, as well as G Suite Basic and Business customers 

Resources 

Labels: , , , , , , , ,

Quick launch summaryYou can now set group membership deletion limits in Google Cloud Directory Sync (GCDS). By adding these limits, you can prevent accidental removal of memberships from groups, as those errors can inadvertently cause users to lose access to things like Drive files and Google Cloud Platform resources.

Limits are not required and can be anywhere from 0-100% or any number greater than 0. Once a limit is set, if a sync attempts to delete more than that percentage or amount of members in any group, the sync will abort.



Please make sure you are using the most up-to-date version of GCDS to access this feature.
AvailabilityRollout details
G Suite editions
  • Available to all G Suite editions
On/off by default?
  • This feature will be OFF by default and can be enabled at the GCDS group level.
Stay up to date with G Suite launches
Labels: , ,

In September, we introduced Google Cloud, a portfolio of products, technologies, and services designed for enterprises. Following that announcement, we’re rebranding our Google Apps Directory Sync tool to better reflect the wide variety of products and services it supports. Going forward, Google Apps Directory Sync will be known as Google Cloud Directory Sync. In addition to this change, the latest version of Google Cloud Directory Sync will include the features and fixes described below.

What’s new

  • The GCDS interface now shows only those sync features supported by your domain type. 
  • The tool uses the latest Java JRE v1.8, which by default uses TLS v1.2 for HTTPS connections. 
  • The GCDS EULA has been updated to include customers who may use a domain covered by the Managed Google Domain Terms.


What’s fixed

  • “Force new users to change password” is now properly set on account creation. 
  • Group memberships are now added properly on initial sync with group creation. 
  • Instead of displaying “Connected failed - null” when there is a connection error testing SMTP notifications, GCDS now displays a proper error message. 
  • Random passwords for accounts are no longer synced on the first and subsequent syncs; they are now set on the first sync only. 
  • Users are now properly provisioned with the defined default password. 
  • You can now re-authorize GCDS using a different account, even if GCDS has a valid auth token. 
  • You can now perform a sync in GCDS, even if you haven’t configured email notification settings.
  • Instead of displaying the raw HTML EULA when installing from the command line, the installer now displays the plain text EULA. 

Check out the Help Center for more details, and download the latest version of GCDS.

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

Editions:
Available to all G Suite editions

Rollout pace:
Gradual rollout (potentially longer than 3 days for feature visibility)

Impact:
Admins only

Action:
Admin action required

More Information
Help Center: About Google Cloud Directory Sync
Help Center: What’s New in Google Cloud Directory Sync


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

A new version (v4.3.0*) of Google Apps Directory Sync (GADS) is now available for download. With this latest update, Google Apps admins can now use GADS to sync additional LDAP attributes into Custom User Fields for use with SAML SSO, or for simply building out richer Google Apps profiles for their users.

For example, a SAML application may require an account ID value for SSO access. With this launch, admins can now use GADS to sync an account ID value from LDAP into a custom user field. Then, within the SSO configuration of the SAML app, they can specify to use the account ID from the custom user field.

This latest version of GADS also includes the following bug fixes:

  • Fixed an issue where user-created groups' permissions were being reset by GADS to the default group permissions settings. 
  • Fixed an issue where the City field was not synced properly and did not display correctly in the contacts interface.
  • Fixed an issue where group descriptions containing a new line in LDAP would fail when being applied to the Google group. 

Check out the Help Center for more details and download the latest version of GADS.

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

Rollout pace:
Gradual rollout (potentially longer than 3 days* for feature visibility).
*Update - July 6, 2016: Please note that GADS version 4.3.0 was rolled back shortly after launch to address a bug. The fix has now been deployed as version 4.3.2, which is now available for download.

Impact:
Admins only

Action:
Admin action required (download the latest version of GADS)

More Information
GADS Overview
What’s New in GADS


Note: all launches are applicable to all Google Apps editions unless otherwise noted

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