Chat now with support
Chat with Support

Coexistence Manager for GroupWise 1.7 - FBC Configuration Guide

About the CMG 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

On-premises Exchange vs. Office 365

CMG supports F/B coexistence with an on-premises Exchange, or with a hybrid or non-hybrid Office 365 (“O365”) scenario.

Hybrid Office 365: O365 is synced to an on-premises Exchange, and CMG’s FBC is configured only between GroupWise and the local on-premises Exchange. Synchronization of the local Exchange to O365 is configured apart from CMG, as described in Microsoft’s documentation. The configuration of CMG’s FBC for a hybrid O365 is therefore the same as for a local on-premises Exchange, and we let Microsoft document the instructions for synchronizing the local Exchange with O365.
Non-hybrid Office 365: Configuration of CMG’s FBC for a non-hybrid O365 (where there is no local Exchange) is a qualitatively different scenario, described in chapters 5, 6, 11 and 12 of this Guide.

Outlook 2003 clients vs. Outlook 2007 or later (with on-premises Exchange)

CMG supports F/B coexistence with Outlook 2007 or later clients connected to Exchange 2007 or later, or with Outlook 2003 clients connected to Exchange 2003 or 2007 (only). These different scenarios require different CMG F/B subcomponents, because the implementation of Exchange F/B features changed between Exchange 2003 and Exchange 2007.

Older versions of Exchange (e.g., Exchange 2000 and 2003) stored free/busy information in system public folders. Beginning with Exchange 2007, F/B information is stored by default in object mailboxes, although Exchange 2007 also lets you store F/B information in public folders, making Exchange 2007 backward-compatible with Outlook 2003 clients.

CMG's Free/Busy Connector was originally designed to function as a direct, immediate query-and-response system, as shown here for Outlook 2007 and later clients connected to an Exchange 2007 or later server:

In this scenario, CMG’s FBC facilitates processes where an end-user client in system "A" asks system "B" for the free/busy info for one of its users, and system "B" immediately replies with the requested information. This model, designed for F/B coexistence with Outlook 2007 or later, is also suitable for Microsoft’s Office 365. But the same approach does not work for Outlook 2003, which can communicate F/B information with external systems only by relaying it through Exchange public folders.

CMG now also supports the public-folders option, by alternate configurations with some different CMG subcomponents to facilitate F/B communications with Outlook 2003 clients connected to either Exchange 2003 or Exchange 2007 servers. The illustrations below show these Outlook 2003 configurations. The configuration instructions for scenarios (chapters) 3, 4, 9 and 10 in this Guide include more details for using Exchange public folders for F/B coexistence with Outlook 2003 clients.

The F/B Connector’s public-folders models for Outlook 2003 clients are not direct query-and-response systems when Outlook users seek GroupWise users’ F/B info. Exchange public folders instead function like a holding tank that must be repeatedly refreshed with updated data, so at any given moment the public folders data will lag some interval (typically several minutes) behind the true current state of GroupWise F/B data as it exists in the GroupWise environment. The polling interval is configurable, so the latency period can be minimized by a shorter interval, although an increased polling frequency imposes greater demands on system resources.

The public-folders FBC model does, however, support a direct query-response process in the other direction—when GroupWise users seek Outlook users’ F/B info. The Exchange public folders serve as a repository for F/B info for both systems’ users, but the information for Outlook users is very nearly current, almost continuously refreshed (internally, by Exchange), whereas the F/B info for GroupWise users must be explicitly obtained and relayed by CMG's F/B Connector, at less frequent intervals.

Single (shared) namespace vs. multiple namespaces

CMG supports F/B coexistence for either a single (shared) namespace environment (equivalent domain names) or separate (multiple) namespaces. In a single-namespace environment, equivalent domains are mapped to the primary domain in the Exchange server or GroupWise server.

In the FBC Configuration Worksheet table below, the odd-numbered scenarios (chapters) are for single (shared) namespace environments, while the even-numbered scenarios (chapters) are for separate (multiple) namespaces.

FBC Configuration Worksheet

Fill in the blanks in this short worksheet, then check the table below to determine your FBC scenario.

GroupWise version is ______, and the GroupWise connection to CMG will be (pick one):

The Exchange side is:

The coexistence environment will be (pick one):

The FBC configuration instructions appear in 12 separate chapters of this FBC Configuration Guide, a different chapter for each scenario. The Chapter column at the right edge of this table shows which chapter numbers of this Configuration Guide provide the configuration instructions for the various scenarios.

Table 2.  

GroupWise
Environment


Exchange Environment

Single (shared) or
Multiple Namespaces?


Chapter

GroupWise via API
(GW 7 or later)

On-Premises Exchange
(or a hybrid Ofc 365)

Outlook 2007 or later
via MS Autodiscover/EWS

Single/shared

1

Multiple

2

Outlook 2003 via
Exchange Public Folders

Single/shared

3

Multiple

4

Office 365 (non-hybrid)

Single/shared

5

Multiple

6

GroupWise via
Internet F/B URL
(GW 8 or later)

On-Premises Exchange
(or a hybrid Ofc 365)

Outlook 2007 or later
via MS Autodiscover/EWS

Single/shared

7

Multiple

8

Outlook 2003 via
Exchange Public Folders

Single/shared

9

Multiple

10

Office 365 (non-hybrid)

Single/shared

11

Multiple

12

 

Related Documents