Chat now with support
Chat with Support

Coexistence Manager for GroupWise 1.7.1 - FBC Configuration Guide

About the Coexistence Manager for GroupWise Documentation Determine your FBC scenario FBC Scenario #1 FBC Scenario #2 FBC Scenario #3 FBC Scenario #4 FBC Scenario #5 FBC Scenario #6 FBC Scenario #7 FBC Scenario #8 FBC Scenario #9 FBC Scenario #10 FBC Scenario #11 FBC Scenario #12 Appendix: FBC Planning Worksheet Appendix: Configuring and troubleshooting the FBC with PowerShell Appendix: Troubleshooting the FBC

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 Office 365 contacts, and Exchange users to GroupWise. Coexistence Manager for GroupWise’s Directory Connector does not support directory synchronizations directly between GroupWise and Office 365. In this non-hybrid O365 scenario, however, you can configure Microsoft’s Azure AD Sync synchronization tool to synchronize a local AD with Office 365. See Microsoft’s Azure AD Sync tool documentation for instructions and guidance in configuring the Azure AD Sync tool for this purpose.

Make sure that the GroupWise SOAP web service is enabled (step 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 Office 365 connections

Configure and verify the link from Office 365 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 O365.

For FBC coexistence with Office 365, run Enable-OrganizationCustomization, and then create the availability address space by opening a PowerShell session and using the following commands:

New-AvailabilityConfig –OrgWideAccount <username@domain.onmicrosoft.com>
[replace <username@domain.onmicrosoft.com> with your O365 admin account]
$domain = "<domain.onmicrosoft.com>"
[replace <domain.onmicrosoft.com> with your SMTP domain name in Office 365]
$adminUserId = "<username@domain.onmicrosoft.com>"
[replace <username@domain.onmicrosoft.com> with your O365 admin account]
$adminCredsId = "<username@domain.onmicrosoft.com>"
[replace <username@domain.onmicrosoft.com> with your O365 admin account]
$adminCredsPassword = "<YourPassword>"
[replace <YourPassword> with your Office 365 admin password]

5.3: Configure DNS

You can use Network Load Balancing to permit multiple web servers to handle Autodiscover requests. This is optional, not required to deploy Coexistence Manager for GroupWise. For more information, see this Microsoft article.

Configure DNS to point autodiscover.<smtpdomain.com> to the computer where Coexistence Manager for GroupWise’s Autodiscover service is installed. For each domain, Exchange connects to predefined Autodiscover URLs using DNS host entries.

For Exchange to get free/busy information from the domain supported by a GroupWise server, through the Coexistence Manager for GroupWise Free/Busy Connector, you must make the Coexistence Manager for GroupWise Autodiscover Web Service resolvable to this URL:

Appendix: FBC Planning Worksheet

Use this worksheet to gather and organize the information you will need to enter into Coexistence Manager for GroupWise’s Management Console application to configure the Free/Busy Connector (FBC).

This worksheet is designed with wide right margins, to leave you room to write in the information you are gathering and any pertinent notes.

Related Documents