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:
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 .
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:
This procedure begins with the assumption that you have already reviewed the introductory chapter of this FBC Configuration Guide to . This chapter explains how to configure the FBC and the coexisting environments for F/B scenario #12, specified above.
Review the System Requirements (in the Coexistence Manager for GroupWise Release Notes), and verify either that your environment conforms to the requirements, or that you will have the necessary hardware and software to meet the requirements.
Scan through the installation and configuration procedures in this chapter, and think through what this process will entail in your own environment, to accommodate your own needs and preferences. Identify any special circumstances or issues, and determine how these will be addressed.
For any given scenario and configuration, it is possible to install all Coexistence Manager for GroupWise F/B Connector components on a single server, as shown in the illustrations in the introductory chapter () of this Guide. However, many production environments experience sufficient query volume to warrant separate servers to ensure optimal performance. The instructions here therefore describe how to install Coexistence Manager for GroupWise’s F/B Connector on two servers. If you prefer that all subcomponents reside on a single server, simply combine the components of Coexistence Manager for GroupWise Server 1 and Coexistence Manager for GroupWise Server 2 as they are listed below. All Coexistence Manager for GroupWise Free/Busy Connector subcomponents are installed by the AutoRun utility included in the Coexistence Manager for GroupWise product kit, as described in a later step in this chapter.
For Exchange queries for GroupWise F/B information, the simplest approach is to dedicate a separate Coexistence Manager for GroupWise FBC Server 2 (as noted just above, for Exchange queries to GroupWise, and GroupWise replies) for each GroupWise server, with all the Coexistence Manager for GroupWise servers feeding into the single Exchange server.
It is technically possible, but somewhat more complicated, to configure a single instance of the GroupWise FBC Service, EWS and Autodiscover to process free/busy traffic to and from multiple GroupWise servers—an approach that requires more elaborate GroupWise configurations.
Use the worksheet in Appendix A of this FBC Configuration Guide to gather and organize the information you will need to enter into Coexistence Manager for GroupWise’s Management Console application when configuring the Free/Busy Connector. You can print the worksheet to paper, and use a pen or pencil to write the information into the wide right margins.