Duplicate calendar folder (e.g. Calendar1) being created while synchronising Calendar (4241058)

Duplicate calendar folder (e.g. Calendar1) being created while synchronising Calendar

Mailboxes might have a duplicate calendar folder (e.g. Calendar1) which might have been created during the synchronisation with Quest Migration Manager for Exchange (QMM).

It has been found that ActiveSync will sometimes create duplicate folders if it tries to write to the calendar at the same time as the Calendar Synchronisation Agent (CSA).

Scope
This affects mailboxes

• which are part of a calendar collection in QMM,
• and are synchronised with ActiveSync at the same time, that is a mobile device is connected to the target mailbox and is synchronising data with it.

Above conditions result in the default calendar folders being re-created in a mailbox by ActiveSync synchronising data from a mobile device into it. This might happen when the CSA and ActiveSync are working on the same folder simultaneously, as the calendar folder is then locked by the CSA. Due to the new calendar folder being the default folder, the CSA will synchronise this folder during the next session.

To prevent this possibility from a Quest agent perspective we recommend the following best practice:

1. ActiveSync should be disabled for target mailboxes that have not been switched yet, as calendar synchronisation takes place from source to target during this phase.
2. ActiveSync should be disabled for source mailboxes after the mailboxes are switched, as calendar synchronisation takes place from target to source after switching.
3. The calendar sync collection should be configured just for 1-way synchronisation of user mailboxes (a separate 2-way sync collection should be created for resource mailboxes). In this configuration the synchronisation direction changes after the switch so that calendars are then synchronised from target to source. As the target calendar is then only affected by a read operation, the target calendar folder will not be locked and ActiveSync will not create a duplicate folder. With this configuration ActiveSync can be safely enabled on the target mailbox after switching, allowing a little time first for any latency in writing all the data to the target mailbox.

RebuildContainerClass 1.0.2

In order to verify that ActiveSync has created the duplicate calendar folder, MFCMAPI can be used with the following steps: Start MFCMAPI Go to 'Session' - 'Log on and Display Store Table' Create an Exchange profile for the mailbox with the duplicate folder or select an existing one Open the mailbox from the store table Expand 'Top of Information Store' Select 'Calendar' Open the properties of the PR_CREATOR_SID property Verify the user shown in the 'Smart View' section The attached script checks mailboxes for this issue and attempts to repair them.  The installation instructions in the zip file refer to an older version but are still valid. If Outlook.exe /resetfolders was already executed and Calendar1 folder is present (PR_IPM_APPOINTMENT_ENTRYID is NOT EMPTY), simply set Const forceResetting = True.  Upon execution the script will replace the value of PR_IPM_APPOINTMENT_ENTRYID with the value of ENTRY_ID of the folder you specified in the constant CalName. Note: This folder should exist inside all mailboxes on your list, the default value Calendar should normally be OK. Notes: Make sure the users are logged out of Outlook before performing these steps. -  The script can be run against both source and target mailboxes as required. It is also a good idea to export users' appointments into PST as a precautionary measure. If running the script from an x64 platform it should be run from the 32-bit command line (C:\Windows\SysWOW64\cmd.exe).  If running against an Exchange 2010 platform the server name should be specified as the CAS server