Clear search
Close search
Google apps
Main menu

    What's new in GSSMO?

    As we add features, enhancements, and fixes to G Suite Sync for Microsoft Outlook® (GSSMO), 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
    1. Update GSSMO
    • If you installed GSSMO: Updates are checked for and downloaded to your computer automatically.
    • If your administrator installed GSSMO: 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 GSSMO download page.
    2. For the update to go into effect:
    • 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 GSSMO icon in the system tray and choose About from the menu.

    Read about known issues

    Check G Suite known issues for information about the current list of GSSMO known issues.

    Release 3.8.440.1250
    December 16 , 2015

    What's fixed

    Fixed an issue that caused GSSMO to keep asking for authorization when some of the services have been disabled by the G Suite administrator.

    Release 3.8.430.1200
    December 2, 2015

    What's fixed
    • GSSMO didn't correctly handle a case where the OAuth token was no longer valid. It now asks the user to re-authorize if the OAuth token is revoked. 
    • The Delete saved GSSMO passwords tool (ProfilePasswordDelete.exe) now works with Outlook 2016 Click-To-Run.

    Release 3.8.420.1150
    November 11, 2015

    What's new
    GSSMO now supports Office 2016 and Windows® 10.


    Release 3.7.410.1100
    May 19, 2015

    What's fixed

    Issue: When deleting a subfolder in the Outlook Notes folder, the Google Drive folder was permanently deleted, including non-Notes content.


    • Notes and Notes folders removed from Outlook are now sent to Trash in Google Drive instead of being permanently deleted.
    • Deleting a Notes folder from Outlook will move all Notes items in the Drive folder to Trash. If the Google Drive folder is empty (contains no other Drive documents), the empty folder is moved to Google Drive's Trash.

    Release 3.7.400.1050
    April 28, 2015

    What's fixed

    Improved Notes synchronization

    Issue: Notes synchronization would crash the application if there were malformed responses returned by Drive API requests.

    Resolution: Optimized Notes synchronization by limiting the fields requested of the Drive API to only those fields that are needed to perform the update.

    Release 3.7.395.1040
    March 24, 2015

    What's fixed

    Notes synchronization no longer crashes the application if there are missing or empty data fields returned in Drive API requests.

    GSSMO automatically updates so users will receive the new version over the following days. If you have disabled automatic updates, or if you installed a version that doesn't include automatic updates (the Enterprise MSI version of GSSMO), you can get the latest version from our download page.

    All customers who have opted not to auto-update must upgrade to GSSMO 3.7.395.1040. Notes synchronization in older versions will stop functioning after April 20, 2015.

    Release 3.6.390.1030
    March 9, 2015

    What's new

    G Suite Sync for Microsoft Outlook now uses the Drive API for Notes synchronization
    (version 2).

    GSSMO automatically updates so users will receive the new version over the following days. If you have disabled automatic updates, or if you installed a version that doesn't include automatic updates (the Enterprise MSI version of GSSMO), you can get the latest version from our download page.

    All customers who have opted not to auto-update must upgrade to GSSMO 3.6.390.1030 before April 20, 2015. Notes synchronization in older versions will stop functioning after this date.

    What's fixed

    Accounts with more than 100 calendars can now sync Google Calendar correctly.

    Release 3.5.385.1020
    October 20, 2014

    What's fixed

    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.

    Release 3.5.380.1010
    September 19, 2014

    What's fixed

    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 GSSMO 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.

    Release 3.5.375.1000
    September 15, 2014

    What's fixed

    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: GSSMO 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: GSSMO now properly handles changes to calendar event sequence numbers.

    Release 3.5.370.990
    February 20, 2014

    What's fixed

    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: GSSMO 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 GSSMO user. Error codes 0x8007013d or 0x8007045a were visible in the trace log files.

    Resolution: GSSMO can now create profiles successfully on these system, without the need for any workaround.

    Release 3.5.365.980
    November 21, 2013

    What's new

    GSSMO now supports Click-to-Run editions of Microsoft Outlook 2013.

    What's fixed

    Calendar sync issues

    Issue: Events with dates between the years 100 and 1600 would cause the entire calendar to not sync.

    Resolution: GSSMO 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.

    Release 3.4.360.960
    September 26, 2013

    What's new

    "Remember me" is now checked by default to help ensure users don't have to go through authorization more than once.

    What's fixed

    Multiple prompts for authentication

    Issue: Under certain scenarios, users are prompted for authentication multiple consecutive times, or when network issues occurred.

    Resolution: GSSMO 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: GSSMO 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.

    Authorization errors

    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.

    GSSMO 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: GSSMO installation now checks the correct Registry keys and values to detect Click-to-Run versions of Outlook.

    Release 3.3.355.950
    June 3, 2013

    What's fixed

    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. 

    Release 3.3.354.948
    May 22, 2013

    What's new

    Outlook 2013 support!

    GSSMO now supports Microsoft Outlook® 2013.

    Easily change trace file and PST file locations

    By default, GSSMO stores your trace files and Outlook PST files with your local application data in a Google/GSSMO folder (details here). If you want to change these locations, you can now do so using a simple menu command. Just right-click GSSMO in the Windows system tray and choose Modify PST and Log folder path.

    Enhanced security via web-based Authorization

    In previous versions of GSSMO, users authorized their Outlook profile by entering their G Suite 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 GSSMO from their web-based Account Settings, should their computer be lost or stolen.

    What's fixed

    Delegate's calendar events appeared on subscriber's calendar

    Issue: Subscribing to receive another user's calendar notifications caused GSSMO to create events for the subscriber even if they weren't invited to the event.

    Resolution: GSSMO no longer creates events for subscribers unless the subscriber is themself invited to the event.

    Release 3.2.353.947
    August 14, 2012

    What's new

    Simplified login when using SSO only

    We've improved the login flow for GSSMO users who have enabled Single Sign On (SSO) login to G Suite, 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 GSSMO application.

    Note: You enable or disable SSO vs. password login for individual users by making registry settings on the user's computer. Learn more

    What's fixed

    Address book error messages

    Issue: Address book errors were being reported for domains that weren't using the G Suite Global Address List (GAL). These errors were logged with a status code of 0x80041192.

    Resolution: This status code is now disabled in the GSSMO 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 G Suite 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

    What's fixed

    Sent messages incorrectly appeared as coming from the wrong user

    Issue: If you had delegate access to your manager's Gmail account in GSSMO, 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

    What's new

    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 GSSMO. This only applies the first time the user starts Outlook, after creating their G Suite profile. You do this by creating a Windows registry key on the user's computer (do this before they create their G Suite 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 GSSMO doesn't try to sync items from that service.

    What's fixed

    Error reported when trying to run GSSMO

    Issue: In some cases, running GSSMO displayed the error, "Unable to open your default email folders. The information store could not be opened." To use GSSMO, you had to close Outlook and start it again.

    Resolution: Several issues that were preventing GSSMO 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 GSSMO handles retryable server errors so you should see fewer of these errors logged in Sync Issues.

    Release /
    January 24 / March 9, 2012

    What's new

    Outlook Tasks now synchronize with G Suite!

    You can use Outlook Tasks to track and manage to-do lists in your G Suite account. The following information in Outlook Tasks synchronizes with your Gmail Task gadget, and is available from other devices where you access your G Suite 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.


    What's fixed

    Contact sync errors occurred when using Outlook with Solve360

    Issue: If you were using the Solve360 CRM client management service from the G Suite Marketplace with GSSMO, you might have been unable to sync your Contacts with G Suite.

    Resolution: Contacts now sync successfully when using Solve360.


    Was this article helpful?
    How can we improve it?
    Sign in to your account

    Get account-specific help by signing in with your G Suite account email address, or learn how to get started with G Suite.