Why does the Conflict Resolver display conflicts between iCal and BusySync?
BusySync uses Apple’s Sync Services to sync calendar data to iCal. Sync Services has a fundamental limitation that two events with the same name and date cannot exist on two different calendars. If they do, the Conflict Resolver will pop up and require you to choose which event to keep and which to delete. This can cause havoc when sharing calendars on the network. To avoid such problems, you need to work within the limitations of Sync Services. This means you need to be careful when first setting up BusySync to remove any duplicate calendars on a subscribing machine that may be left over from using previous syncing applications (such as .Mac/MobileMe). Also, you need to design a workflow that avoids duplicating events. Often companies want to create a shared calendar for each employee, but when several people put the same event on their calendars, that can lead to conflicts. One solution is to prefix such common events with the person’s initials, so there won’t be conflicts with other
