Planning calendars and scheduling

Answer the questions in this topic to help you understand and plan for the use of calendars and scheduling in the service.

About this task

Table 1. Calendars and scheduling questions
Question Considerations

Do you want on-premises users to look up the free-time of service users?

When an on-premises user requests the free-time of a service user, the request is sent to the service user’s mail server. The following on-premises configuration is required:
  • The on-premises user’s mail server must run the Calendar Connector (CalConn) server task.
  • An on-premises server in the service user’s domain must send the request to the service. This server must be Domino 8.5.1 Fix Pack 2 or a later version and must run the CalConn server task.
  • If the on-premises user making the request is in a different Domino domain than the service user, the Calendar server in the on-premises user’s domain must be able to send the request to the Calendar server in the service user’s domain. The Calendar server in the service user’s domain then sends the free-time request to the service user’s mail server.
  • If the service user is not in the on-premises hub domain, you must create a Connection document that enables servers in the domain to connect to the service to send the free-time request. This same Connection document is also required to connect to the service to route mail. This step is unnecessary for the on-premises hub domain because the Domain Configuration tool creates the required Connection document.

Do you want service users to look up the free-time of on-premises users?

When a service user requests the free-time of an on-premises user, the service user’s mail server sends the request to a mail hub server in the on-premises hub domain. The following on-premises configuration is required to process the request:
  • The CustomerMailHubs group, which includes the names of the on-premises mail hub servers, must replicate to the service. This step provides the service user’s mail server with the information necessary to connect to the mail hub servers. The Domain Configuration tool creates the group in the primary directory of the on-premises hub domain. If you do not synchronize this directory, you must copy the group to a directory that you do synchronize.
  • If the on-premises user’s domain is not the on-premises hub domain, a Calendar server in the hub domain must be able to connect to the Calendar server in the on-premises user’s domain to forward the request.
  • If the on-premises user information is available in the on-premises hub domain only through an extended directory catalog, the mail hub servers in the on-premises hub domain must use directory assistance to look up names in the directory catalog.

Do you want service users to reserve rooms and resources when scheduling meetings?

A service user can schedule rooms and resources in on-premises Resource Reservations databases. The following on-premises configuration is required to process the request:
  • You must synchronize the directory of the domain in which a Resource Reservations database is located. Synchronization replicates the Mail-in database documents that are required to route the reservations on-premises.
  • When a service user reserves a room or resource, the reservation is mailed to a mail hub server in the on-premises hub domain. If the Resource Reservations database that contains the room or resource is in another domain, you must configure mail routing to the other domain. This requirement is similar to the requirement for routing mail to an on-premises user in another domain.
  • To enable a service user to look up the free-time of a room or resource, the service user’s mail server must be able to connect to a mail hub server in the on-premises hub domain. An on-premises server must be able to look up the free-time in the Resource Reservations database and return it to the service. These requirements are similar to the requirements to look up free-time of on-premises users.
  • You can replicate the directory of the domain that contains a Resource Reservation database to the service through a directory catalog. In this case, specific fields required for resource reservations must be aggregated in the catalog.
  • Avoid the use of duplicate site names that are used for rooms and resources. If two sites have the same name, the service lists resources from both sites under one site name. This situation can lead users to reserve resources at the wrong site.