部署分为3个阶段

1. Core IT
2. Early Adopters
3. Global Go-Live

大概需要3个月的时间，CoreIT是第一阶段，主要是25人以下的小团队确定测试项目，熟悉GWS系统，第二阶段也占用1个月时间，主要是验证迁移的有效性，获得FB，测试变更计划，最后阶段，是全面展开

• GCDS is installed on a local server, connect to local directory
• Data is extracted as a list from AD
• GCDS connects to GWS and generates a list of objects to synchronize
• GCDS compares the lists and updates the Google domain to match the AD data

GWS structure will not reflect AD hierarchy, so don't use OU sync.

分为4部分

1. Users
2. Groups
3. Shared contacts
4. Calendar Resources

How does GCDS support password synchronization from Active Directory?

1. GCDS monitors Active Directory for changes to a user’s password and then pushes the change up when the next synchronization operation occurs.
2. GCDS does not support the Active Directory password format. Customers should deploy G Suite Password Sync to support password changes.
3. GCDS continuously monitors Active Directory for changes to a user’s password and then pushes the change up immediately.

What is Google’s preferred method for verifying domain ownership?

1. Add a metatag to your web site’s home page.
2. Send Google a copy of your DNS invoice stating you own the domain.
3. Add a TXT record to your DNS records.
4. Add a CNAME record to your DNS records.

How does Google’s recommend Core IT users to book calendar resources?

1. Manually create all resources in Google Workspace as part of the Core IT phase so they can book resources from Google Calendar.
2. Core IT users should not be using Google Calendar. They should continue to use the legacy system calendar and resource booking system.
3. Deploy GCDS as part of the Core IT phase so resources can be synchronized and they can be used from the legacy system and Google Workspace.
4. Ask Core IT users to book resources in the legacy platform.

How does Google Cloud Directory Sync synchronize directories?

1. GCDS ensures the Google directory matches the local LDAP directory by pushing updates to Google only.
2. GCDS performs a two way sync so changes made in either directory are updated in the other. Conflicts are handled by applying the most recent change made to an object.
3. The GCDS administrator can choose to make either the Google directory or the local LDAP directory the master directory.
4. GCDS ensures the LDAP directory matches the Google directory by pulling changes down from Google only.