![]() The path will depend on your server's configuration and the affected shared Calendar.īy default, for a user calendar, this will be similar to the following path: To help isolate the behavior, you should collect and review the status.fld file from the mail store in the filesystem. ![]() If all of the expected Sharing and Delegation settings appear valid within the Kerio Connect Client UI, this may indicate an issue on the backend. Note that if you use user groups to share, you will want to confirm that the expected individuals appear within these groups, as shown in Managing User Groups in Kerio Connect. You can reference how to share calendars to verify that the users affected have been provided with the necessary access rights. When users report issues specifically with viewing the shared Calendar or its events, this can often be traced back to incorrectly configured sharing settings. You can reference Configuring Delegation (On Behalf of) in Kerio Connect Client for guidance on setting this up for your Shared Resource. In these situations, you can instead use Delegation, a more advanced form of sharing that enables this functionality. Within Kerio Connect, when a Shared calendar event contains more than one attendee, it is expected that only the event owner will be able to make changes to the event. It is suggested that you first recreate the event using the same settings initially used to verify whether or not the behavior reappears. When a single event is exhibiting unexpected behavior, such as users with sharing rights being unable to view or edit the event, the individual event may have become corrupted. Recreate the event and attempt to reproduce.
0 Comments
Leave a Reply. |