ZCS Administrator Guide 7.2.1
ZCS Administrator Guide 7.2.1
Open Source Edition


Managing ZCS Configuration > Zimbra Free/Busy Interoperability

Zimbra Free/Busy Interoperability
When ZCS is deployed in a mix of ZCS servers and Microsoft Exchange servers and Calendar is an important feature with your users, you can set up free/busy scheduling across the mix so that users can efficiently schedule meetings.
ZCS can query the free/busy schedules of users on Microsoft Exchange 2003, 2007, or 2010 servers and also can propagate the free/busy schedules of ZCS users to the Exchange servers.
To set free/busy interoperability, the Exchange systems must be set up as described in the Exchange Setup Requirements section, and the ZCS Global Config, Domain, COS and Account settings must be configured. The easiest way to configure ZCS is from the administration console.
Note:
Exchange 2003/2007/2010 Setup Requirements.
The following is required:
*
*
The ZCS server must be able to access the HTTP(S) port of IIS on at least one of the Exchange servers.
*
*
ZCS users must be provisioned as a contact on the AD using the same administrative group for each mail domain. This is required only for ZCS to Exchange free/busy replication.
*
The Exchange user email address must be provisioned in the account attribute zimbraForeignPrincipal for all ZCS users. This is required only for ZCS to Exchange free/busy replication.
Configuring Free/Busy on ZCS
To set Free/Busy Interoperability up from the administration console, configure the following:
*
*
Add the o and ou values that are configured in the legacyExchangeDN attribute for Exchange on the Global Config Free/Busy Interop tab, the Domain Free/Busy Interop tab or on the Class of Service (COS) Advanced tab. The o and ou values correspond to the ZCS domain attribute zimbraFreebusyExchangeUserOrg.
*
In the Accounts Free/Busy Interop tab, configure the foreign principal email address for the account. This sets up a mapping from the ZCS account to the corresponding object in the AD.
Note:
To find these settings on the Exchange server, you can run the Exchange ADSI Edit tool and search the legacyExchangeDN attribute for the o= , ou= , and cn= settings.
Global Config Setup
The ZCS Global Config Settings are configured from the Free/Busy Interop tab on the administration console. Here you configure the Exchange server settings as follows:
*
*
*
*
Microsoft Exchange user name and password. This is the name of the account in Active Directory and password that has access to the public folders. These are used to authenticate against the Exchange server on REST and WebDAV interfaces.
*
The O and OU used in the legacyExchangeDN attribute. Set at the global level this applies to all accounts talking to Exchange.
Global Settings Advanced Tab
The features configured in the Advanced tab include:
*
*
Briefcase Share Configuration
When a Briefcase folder is shared with an external guest, they must log in to view the shared item.
The Authentication Required dialog that displays references the company name “Zimbra”. You can change the company name from Zimbra to your company name in the Global Settings or Domains Advanced tab.
Setting Account Email Validation Rules
The ZCS server validates an email address or domain name using javax.mail.internet.InternetAddress when accounts, groups, or domains are created or renamed.
You can define additional email validation rules to validate email addresses for messages sent from the advanced Zimbra Web Client. This validation is done from the Zimbra Web Client.
1.
 
2. In the Regular expression for invalid email address field enter a regular expression (regex) to filter out email addresses that should be considered invalid. You can add multiple regular expressions.
Example of regular expressions:
*
test@\\d+.com. This regular expression identifies email addresses with a number in the domain name as invalid. That is test@123.com or test@1.com are not valid addresses.
*
mail@donotreply.com (any specific address). This type of regular expression identifies a specific email address that is invalid.
Note:
 
 
Copyright © 2012 VMware Inc.