-
Notifications
You must be signed in to change notification settings - Fork 216
Hints & Tips
Although this is not yet available directly within OGCS, it is still possible to set this up by running multiple instances of OGCS at the same time, one for each calendar to be synced.
From v2.7.2, OGCS can be run with additional parameters to specify different settings and logfiles for each instance.
From v2.7.6, OGCS also supports two-way sync between a "common" calendar. For example, Outlook Workplace 1
Google calendar
Outlook Workplace 2
.
If you encounter a calendar item that is always flagged for deletion but shouldn't be, it may be possible to resolve this by forcing a full synchronisation.
The following example is for a problematic Google item:
- If you have two-way sync configuration, once you're sure Google has no further changes that need syncing to Outlook, set OGCS to one-way sync: Outlook to Google.
- Force a full sync by pressing and holding the
Shift
key while clicking theSync
button - Set OGCS back to two-way sync, if necessary
- Perform a normal (differential) sync by just clicking
Sync
and confirm if the problem has been resolved
To facilitate the synchronisation, OGCS will hold extra pieces of information (metadata) against calendar entries. These can be removed by carrying out the following steps, which will revert your calendar(s) to a state resembling that before OGCS ever performed its first sync.
- Go to the
About
tab and double click theConfig In
file location to open Windows Explorer, then close OGCS - From Windows Explorer, open
settings.xml
in a text editor and find theExtirpateOgcsMetadata
entry. - Change its value from
false
totrue
, save the file and close it - Start OGCS - you'll have a warning and a red sync button
- Click Sync and purge your calendars of metadata.
- Close OGCS and change the setting back to
false
- Start OGCS and run a sync - all your items will get "reclaimed" on the first sync before subsequent syncs continue as normal
Sometimes it may be desirable to remove all the items that have been synced to a calendar, for example due to a misconfiguration or wanting to back out some testing. This is not built into OGCS, primarily because it is a dangerous operation that I don't want to make easily available.
However, I have provided a guide on a semi-automated mechanism - it is reasonably technical, but probably tempting if you don't want to have to manually delete hundreds of items!
⚡ This feature is now built in to OGCS from v2.5.3, but for reference there is also the below manual workaround too.
If starting OGCS on startup of Windows causes problems with Outlooks own startup sequence, the following VBA script calls OGCS after Outlook has done its own startup things.
Copy and paste the code into Outlook's ThisOutlookSession
VBA module (hit Alt
+F11
to open the editor).
📍 Remember to correct the paths to point to your OGCS installation folder.
' Startup: runs on Outlook start up
Private Declare Function ShellExecute Lib "Shell32.dll" Alias "ShellExecuteA" ( _
ByVal hwnd As Long, _
ByVal lpOperation As String, _
ByVal lpFile As String, _
ByVal lpParameters As String, _
ByVal lpDirectory As String, _
ByVal nShowCmd As Long _
) As Long
Private Sub Application_Startup()
' Start the Outlook to Google sync
Dim RetVal As Long
On Error Resume Next
RetVal = ShellExecute(0, "open", "P:\Apps\OutlookGoogleCalendarSync\OutlookGoogleCalendarSync.exe", " ", "P:\Apps\OutlookGoogleCalendarSync", 3)
End Sub