What's new in this release?
As we add features, enhancements, and fixes to Google Apps Sync for Microsoft Outlook®, we'll release updates both automatically and from our download page. We'll also continue to update this page with the latest release information. Here's a look at what's new in the latest release, and how you can get it.Getting the latest release
Getting the latest release1. Update Google Apps Sync
- If you installed Google App Sync: Updates are checked for and downloaded to your computer automatically.
- If your administrator installed Google Apps Sync: Updates are downloaded to your computer automatically, if your administrator enables automatic updates.
You can also download the latest version at any time from the Google Apps Sync download page.
- If you have Windows XP: Restart your computer.
- If you have Windows Vista: Restart Microsoft Outlook ®.
To see if you've got the latest version, click the Google Apps Sync icon in the system tray and choose About from the menu.
Read about known issues
Check the "Email Clients and Mobile Devices" section of the Known Issues page for information about the current list of Google Apps Sync known issues.
October 20, 2014
Outlook sync version 3.2.353.947 and earlier clients are not prompted to re-authenticate after the tool is upgraded
Issue: Immediately after upgrading from version 3.2.354.947 or lower, user are not prompted to re-authenticate. As a result, the sync fails and requires the user to re-authenticate.
Resolution: The new version of the tool properly determines that re-authentication is required after upgrading from version 3.2.353.947 or lower.
September 19, 2014
Calendar event updates failed due to event sequence number complications
Issue:: After a calendar event is updated, its sequence number is increased by a value of one. The Google Apps Sync for Outlook tool was attempting to update the sequence number of a changed event twice, preventing the event changes from syncing to Google Calendar.
Resolution: The Outlook sync tool now only updates the sequence number of a changed event once.
September 15, 2014
Messages sent in Outlook 2013 are not delivered to particular contacts
Issue: If you create a contact in Outlook 2013 by right-clicking on a message you've received and selecting Add to Contacts, subsequent messages sent to that contact will not be delivered.
Resolution: Google Apps Sync now fixes the contact's address in Outlook by registering it as a valid SMTP address. Any existing invalid contacts will be fixed with this upgrade.
Updated calendar events cause local calendar sync failures in Outlook
Issue: Outlook Sync users may receive a local calendar sync error after the owner of an event they've already accepted updates the meeting time.
Resolution: Google Apps Sync now properly handles changes to calendar event sequence numbers.
February 20, 2014
Calendar sync issues
Issue: Some users experienced calendar sync issues when the calendar event feed included events that didn't have visibility, creator, and organizer provided.
Resolution: Google Apps Sync now syncs these events correctly even when visibility, creator, and organizer are missing.
Profile creation issues on Click-to-Run version of Outlook
Issue: Some users received errors when trying to set up a new Google Apps Sync user. Error codes 0x8007013d or 0x8007045a were visible in the trace log files.
Resolution: Google Apps Sync can now create profiles successfully on these system, without the need for any workaround.
November 21, 2013
Google Apps Sync now supports Click-to-Run editions of Microsoft Outlook 2013.
Calendar sync issues
Issue: Events with dates between the years 100 and 1600 would cause the entire calendar to not sync.
Resolution: Google Apps Sync now syncs these events correctly: Events in years up to 0099 are treated as events in years 2000-2099, and events in years 100-1600 are treated as events in year 1601, which is the earliest year Outlook supports.
September 26, 2013
"Remember me" is now checked by default to help ensure users don't have to go through authorization more than once.
Multiple prompts for authentication
Issue: Under certain scenarios, users are prompted for authentication multiple consecutive times, or when network issues occurred.
Resolution: Google Apps Sync now correctly stores authentication details during the session, and retries on network errors for two minutes.
Calendar sync issues
Issue: Events with dates prior to the year 1601 or with visibility set to "private" could cause the calendar to not sync.
Resolution: Google Apps Sync now parses these events correctly.
Appointments changing to meetings
Issue: Appointments (events with no attendees) would change to meetings (events with only the user as the single attendee) after being synced.
Resolution: Event type is now preserved.
Issues accepting invitations
Issue: In come cases, invitations to events sent from external systems (non-Google users) couldn't be accepted.
Resolution: All invitations can now be processed correctly.
Calendar invites would sometimes appear blank or have no RSVP buttons
Issue: When the recipient's email address didn't match the user's known email addresses in Outlook, RSVP buttons would be missing.
Resolution: RSVP buttons are now shown for all invitations.
Issue: In some cases, issues detecting browser authorization would cause authorization to fail even when the user completed it.
Resolution: Better means of detecting browser authorization have been implemented.
Google App Sync profile creation issues
Issue: Users with suspended Google+ profiles were not able to create a profile.
Resolution: Profile creation now handles users with suspended Google+ profiles correctly.
Incorrect detection of the Outlook version
Issue: In some cases, the installation would report that an unsupported version of Outlook is installed even when it was a supported version.
Resolution: Google Apps Sync installation now checks the correct Registry keys and values to detect Click-to-Run versions of Outlook.
June 3, 2013
Calendars with large number of events failed to sync
Issue: Some calendars with a large number of events failed to sync, instead returning errors after timing out.
Resolution:This problem has been fixed and should no longer occur.
May 22, 2013
Outlook 2013 support!
Google Apps Sync now supports Microsoft Outlook® 2013.
Easily change trace file and PST file locations
By default, Google Apps Sync stores your trace files and Outlook PST files with your local application data in a Google/Google Apps Sync folder (details here). If you want to change these locations, you can now do so using a simple menu command. Just right-click Google Apps Sync in the Windows system tray and choose Modify PST and Log folder path.
Enhanced security via web-based Authorization
In previous versions of Google Apps Sync, users authorized their Outlook profile by entering their Google Apps user name and password in Outlook. To enhance security, users setting up their Outlook profile for the first time are now redirected to a web page where they're prompted to authorize using OAuth—an open standard authorization protocol. As a result, users can now remotely revoke access to Google Apps Sync from their web-based Account Settings, should their computer be lost or stolen.
Delegate's calendar events appeared on subscriber's calendar
Issue: Subscribing to receive another user's calendar notifications caused Google Apps Sync to create events for the subscriber even if they weren't invited to the event.
Resolution: Google Apps Sync no longer creates events for subscribers unless the subscriber is themself invited to the event.
August 14, 2012
Simplified login when using SSO only
We've improved the login flow for Google Apps Sync users who have enabled Single Sign On (SSO) login to Google Apps, but not Google password login. The login dialog is simplified (shows only one option for entering a password), and the authentication landing page better redirects users back to the Google Apps Sync application.
Note: You enable or disable SSO vs. password login for individual users by making registry settings on the user's computer. Learn more
Address book error messages
Issue: Address book errors were being reported for domains that weren't using the Google Apps Global Address List (GAL). These errors were logged with a status code of 0x80041192.
Resolution: This status code is now disabled in the Google Apps Sync interface. Instead, for domains that aren't using the GAL, text appears stating that the service has been disabled by the administrator. No errors are displayed or sync issues logged.
Delegate profiles were replacing primary user's display name in outgoing email
Issue: In some cases, adding a delegate to your Google Apps profile in Outlook would replace your primary user's display name in outgoing mail.
Resolution: This has been fixed and should no longer occur.
May 23, 2012
Sent messages incorrectly appeared as coming from the wrong user
Issue: If you had delegate access to your manager's Gmail account in Google Apps Sync, but sent a message from your own inbox, the message looked like it came from your manager (or whoever you had delegate access to). Your return address was correctly displayed, but your name incorrectly appeared as your manager's.
Resolution: All messages sent from your own inbox now display your correct name in the From field.
May 9, 2012
New registry key for hiding the Synchronization Status dialog for new users
You can now prevent the Synchronization Status dialog from opening by default when a new user first launches Google Apps Sync. This only applies the first time the user starts Outlook, after creating their Google Apps profile. You do this by creating a Windows registry key on the user's computer (do this before they create their Google Apps profile).
For details, see Configure options via the registry.
Disabled services are now indicated in the Synchronization Status
If a particular service such as Google Calendar or Google Drive is disabled for your domain, that service is now marked as disabled in the Synchronization Status dialog and Google Apps Sync doesn't try to sync items from that service.
Error reported when trying to run Google Apps Sync
Issue: In some cases, running Google Apps Sync displayed the error, "Unable to open your default email folders. The information store could not be opened." To use Google Apps Sync, you had to close Outlook and start it again.
Resolution: Several issues that were preventing Google Apps Sync from opening the folders have been fixed, and this error no longer occurs.
Lots of task errors were being logged in the Sync Issues folders
Issue: Some users were seeing consistent task sync errors logged in their Sync Issue folder.
Resolution: We improved how Google Apps Sync handles retryable server errors so you should see fewer of these errors logged in Sync Issues.
184.108.40.206 / 220.127.116.11
January 24 / March 9, 2012
Outlook Tasks now synchronize with Google Apps!
You can use Outlook Tasks to track and manage to-do lists in your Google Apps account. The following information in Outlook Tasks synchronizes with your Gmail Task gadget, and is available from other devices where you access your Google Apps account:
- Tasks, including due dates and reminders
- Task state (whether a task has been marked as completed)
- Top-level task folders sync as separate tasks lists in the Gmail Task gadget.
For details, see:
Contact sync errors occurred when using Outlook with Solve360
Issue: If you were using the Solve360 CRM client management service from the Google Apps Marketplace with Google Apps Sync, you might have been unable to sync your Contacts with Google Apps.
Resolution: Contacts now sync successfully when using Solve360.