If you're using an older version of Google Cloud Directory Sync (GCDS), you might not be getting the most from the tool.
Google occasionally releases new versions of GCDS. We recommend installing the latest version to make sure you have the most recent features and fixes. To review additions and improvements to the most recent versions of GCDS, see Google Cloud Directory Sync release notes.
Note: Google Cloud Support only provides help with issues found in the latest version of GCDS.
There are two options when updating GCDS. Most customers can update their GCDS setup in-place. However, if your organization requires you to keep your existing setup running, while you configure and test the latest version, you can follow the side-by-side update instructions below.
GCDS in-place update
To update your existing GCDS setup, follow these steps:
- Perform a manual GCDS sync so you have fewer changes to review after the update. Learn more
- Download the correct GCDS version for your platform:
- Open the installer and follow the instructions to install GCDS.
If you're installing it on the same machine as the current GCDS installation, the installer should detect GCDS is already installed and suggest an upgrade.
- After you install GCDS, start the GCDS Configuration Manager:
- Select File
Open to load your existing XML configuration file.
- Review the configuration file settings and save it.
Note: You won't be able to run a synchronization until the XML configuration file has been saved using the updated GCDS version.
- Select File
- Run a synchronization simulation and review the proposed changes. Learn more
If any undesired changes are listed, review your configuration, make corrections, and save the XML file.
- If you use a utility like a scheduled task or cron job to run GCDS, trigger the job scheduler manually to ensure the sync works as expected.
This step is especially important if the job scheduler utility runs under a different system user from the one used to configure GCDS.
GCDS side-by-side update
To install another version of GCDS, follow these steps:
- Perform a manual GCDS sync so you have fewer changes to review after the update. Learn more
- Download the correct GCDS version for your platform:
- Open the installer and follow the instructions to install GCDS.
- If you're installing it on the same machine as the current GCDS installation, the installer should detect GCDS is already installed and suggest an upgrade.
- Select No, install into a different directory to install the new version in a different location, without removing the existing version.
- After you install GCDS, start Configuration Manager.
- Verify you're using the new GCDS version by selecting Help
- Select File
- Review the configuration file settings and save it with a new name to create a copy for this new GCDS version.
Note: You won't be able to run a synchronization until the XML configuration file has been saved using the new GCDS version.
- Verify you're using the new GCDS version by selecting Help
- Run a synchronization simulation and review the proposed changes. Learn more
If any undesired changes are listed, review your configuration, make corrections, and save the XML file.
Note: To ensure GCDS sees the entire Google Workspace directory, select Clear cache when running a synchronization simulation.
- If you use a utility like a scheduled task or cron job to run GCDS, update it to use the new version and then trigger the job scheduler manually to ensure the sync works as expected.
This step is especially important if the job scheduler utility runs under a different system user from the one used to configure GCDS.
- To prevent undesired changes due to an outdated configuration file, make sure the previous version's configuration file is disabled. For example, rename the XML file from sync.xml to sync-DISABLED.xml.
- Once you're sure the new version is operating as expected, uninstall the previous version to prevent confusion.
Related topic
Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.