Coexistence Manager for GroupWise 1.7 - FBC Configuration Guide

4.3: Configure trusted sites for computers hosting F/B components

Log in as the CMG account to be used with the F/B Connector (if you haven’t already). Then, in Internet Options (via Windows Control Panel or IE Tools):

By default, CMG is installed with the log42net utility to generate log files of CMG components’ system activity. This information is critical to diagnosing any problems that may arise. Logging is enabled by default for all CMG components.

The default configurations will be suitable for almost all organizations and circumstances, but you can customize logging features if you like. The log42net utility may be configured to work a particular way with each CMG component. Configuration instructions are nearly identical from one component to another, so we present those details separately, in Appendix C of the CMG User Guide (not in this FBC Configuration Guide).

4.5: Run CMG's Management Console to configure FBC components

Use CMG’s Management Console to configure the Free/Busy Connector’s components—to identify the participating servers and their locations, register the necessary account access credentials, and set other operating parameters and preferences. See chapter 4 of the CMG User Guide for field notes and application notes for each screen in the F/B Connector Management Console.

IMPORTANT: For a hybrid Office 365: 1 Be sure to add the O365 suffix (yourdomain.onmicrosoft.com) to the UPN (User Principal Name) suffixes in the Active Directory Domains and Trusts MMC. This lets CMG sign-on to both O365 and the on-prem Exchange with the same credentials (assuming the passwords are the same). If the credentials are different, the FBC lookups to O365 will fail. 2 Make sure the O365 suffix is assigned as the coexistence admin’s user logon name for the on-prem Active Directory.

NOTE: You may use PowerShell commands to configure CMG Free/Busy Connector components, instead of CMG’s Management Console as described here. For information about using PowerShell to configure the Free/Busy Connector, see Appendix B in this Guide: Appendix: Configuring and troubleshooting the FBC with PowerShell.

Step 5: Configure and test connections among GroupWise, Exchange and CMG's FBC Web Server

To configure and test connections among GroupWise, Exchange and CMG’s FBC Web Server:

5.1: Synchronize Exchange and GroupWise directories

Before running any of CMG’s F/B Connector subcomponents, you must synchronize GroupWise users as Exchange contacts, and Exchange users to GroupWise. For best performance, Quest recommends using the CMG Directory Connector. The Directory Connector is another CMG component that you may have already installed and configured, or you can install it now. For complete information about the CMG Directory Connector, see User Guide chapter 2.

If you are configuring the FBC for a local, on-premises Exchange environment (with or without a hybrid O365), use CMG’s Directory Connector to define a bidirectional update (a pair of single-direction updates, in opposite directions, run sequentially). Most admins schedule the pair to run automatically at regular intervals to keep both directories current throughout the coexistence period. Be sure that at least one bidirectional update has completed before continuing.

CMG’s Directory Connector does not support directory synchronizations directly between GroupWise and Office 365. In a hybrid O365 scenario, you can facilitate that directory synchronization by this "two-step" approach:

The combination of the two, run in tandem, would configure an effective directory coexistence between GroupWise and Office 365.

Whatever method you choose to synchronize directories, make sure that the GroupWise SOAP web service is enabled (step 2.2 above), since that is also an environmental requirement for CMG’s Free/Busy Connector.

NOTE: GroupWise sometimes mistakenly generates F/B queries for addresses in the form user-domain-com@domain.com (instead of user@domain.com). Queries to such addresses will fail if AD does not recognize the address, so be sure to add that address form as an alias in AD for each Exchange user.