Coexistence Manager for GroupWise 1.7.1

4.6: Run Coexistence Manager for GroupWise's Management Console to configure FBC components

4.6: Run Coexistence Manager for GroupWise’s Management Console to configure FBC components

Use Coexistence Manager for GroupWise’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 Coexistence Manager for GroupWise User Guide for field notes and application notes for each screen in the F/B Connector Management Console.

IMPORTANT: For a hybrid Office 365:

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 Coexistence Manager for GroupWise 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.

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 Coexistence Manager for GroupWise Free/Busy Connector components, instead of Coexistence Manager for GroupWise’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 Coexistence Manager for GroupWise's FBC Web Server

Step 5: Configure and test connections among GroupWise, Exchange and Coexistence Manager for GroupWise’s FBC Web Server

To configure and test connections among GroupWise, Exchange and Coexistence Manager for GroupWise’s FBC Web Server:

• 5.1: Synchronize Exchange and GroupWise directories
• 5.2: Configure Exchange server connections
• 5.3: Configure DNS

5.1: Synchronize Exchange and GroupWise directories

Before running any of Coexistence Manager for GroupWise’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 Coexistence Manager for GroupWise Directory Connector. The Directory Connector is another Coexistence Manager for GroupWise component that you may have already installed and configured, or you can install it now. For complete information about the Coexistence Manager for GroupWise 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 Coexistence Manager for GroupWise’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.

Coexistence Manager for GroupWise’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:

Configure the Coexistence Manager for GroupWise Directory Connector for bidirectional updates between GroupWise and the local, proprietary Active Directory, and then

Configure Microsoft’s AD Sync tool to synchronize the local AD with the hosted (Office 365) AD.

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 Coexistence Manager for GroupWise’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.

5.2: Configure Exchange server connections

Configure and verify the link from the Exchange server to the domains/subdomains supported by the GroupWise server. This procedure tests whether the certificate on the Coexistence Manager for GroupWise Web Server is trusted by the Exchange server.

To configure the Exchange Server link to the Coexistence Manager for GroupWise Web Server and verify that certificates are trusted by Exchange:

At the Exchange Server, open Exchange Management Shell and enter the following cmdlet:

Add-AvailabilityAddressSpace -ForestName <smtpdomain> -AccessMethod OrgWideFB

... where <smtpdomain> is the name of the GroupWise domain.

Open a web browser and enter the URL http://autodiscover.<domain>/autodiscover/autodiscover.xml to ensure that the Exchange server resolves it to the Coexistence Manager for GroupWise FBC EWS without any certification errors.

Ensure the certificate created earlier is trusted by Exchange. If it is not, see 4.2: Obtain and install web services certificates.

For a multiple-domain or subdomains environment, repeat the above steps for each domain.

NOTE: If you created a self-signed certificate and a certification error appears in the Web browser:

Click the SSL button in the Web browser, then click View Certificates.

Right-click the certificate to open the Import Certificate Wizard.

Install the certificate in Trusted Root Certification Authorities, and click Next.

Click Import, then Finish.

If you requested a certificate from a public CA, the certificate is already trusted by Exchange.

For F/B coexistence with an Exchange 2013 in a single-namespace environment: On all servers running a mailbox role, modify the hostfile to add the IP address and host name of the Coexistence Manager for GroupWise Autodiscover.

To enable shared SMTP namespace F/B lookups in the Exchange-to-Notes direction, add the Coexistence Manager for GroupWise F/B Web Services IP address to the host file on the Exchange CAS server.

If Exchange has sites that are handled by Exchange 2003:

•