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

Exchange free/busy errors

To troubleshoot errors retrieving free/busy information from Exchange, you can use these PowerShell cmdlets:

To get F/B info for an Exchange user via the Exchange F/B Connector Service:

Table 12.  

Get‑CmgExchangeFreeBusy

[-UserEmailAddress] <String>
[-StartDate] <DateTime>
[-EndDate] <DateTime>

UserEmailAddress: Email address of an Exchange user.
StartDate: Starting date for the F/B search.
EndDate: Ending date for the F/B search.

To get F/B info for an Exchange user via the FreeBusyBridge Web Service:

Table 13.  

Get‑CmgFreeBusyBridge

[-WebServerName] <String>
[-UserEmailAddress] <String>

WebServerName: Name of server where FreeBusyBridge Web Service resides.
UserEmailAddress: Email address for whom to get F/B info from Exchange.

These cmdlets retrieve free/busy information for one or more users directly from Exchange using the same code used by the Exchange F/B Connector Service or Bridge Web Service. The cmdlets can be used to narrow down whether the problem is retrieving Free/Busy information from Exchange, or the configuration of the Bridge, or of the Autodiscover service or EWS.

GroupWise free/busy errors

To troubleshoot errors retrieving Free/Busy information from GroupWise, you can use the Get-CmgGroupWiseFreeBusy cmdlet. This cmdlet will retrieve F/B information for one or more users using the Coexistence Manager for GroupWise Mail Connector service.

To get F/B info for a group of GroupWise users via the GroupWise F/B Connector Service:

Table 14.  

Get‑CmgGroupWiseFreeBusy

[-UserEmailAddresses] <String[]>
[-StartDate] <DateTime>
[-EndDate] <DateTime>

UserEmailAddresses: List of email addresses of GroupWise users.
StartDate: Starting date for the F/B search.
EndDate: Ending date for the F/B search.

This cmdlet can be used to narrow down whether the problem is retrieving Free/Busy information from GroupWise, or the configuration of the Autodiscover or Availability web services.

"Unable to generate a temporary class" error when attempting Exchange-to-GroupWise F/B query

An Exchange-to-GroupWise F/B query will generate this error:

... if the IIS_IUSRS user does not have List folder / read data permission. To resolve this, grant the user that List folder / read data permission.

Outlook/OWA users cannot see free/busy information for GroupWise users

Verify that Add-AvailabilityAddressSpace has been executed on the Exchange server. To see if the cmdlet has run, type on the Exchange Management Console: Get-AvailabilityAddressSpace
Add-AvailabilityAddressSpace -ForestName <YourDomain.com> -AccessMethod OrgWideFB -Credentials $adminCreds -UseServiceAccount $true
Add-AvailabilityAddressSpace -ForestName <YourDomain.com> -AccessMethod OrgWideFB -Credentials $adminCreds -UseServiceAccount <AccountName> -TargetAutodiscoverEpr 'https://autodiscover.<YourDomain.com>/autodiscover/autodiscover.xml'
Ensure you can ping <smtpdomain> or autodiscover.<smtpdomain> and that it resolves to the computer running the Coexistence Manager for GroupWise F/B Connector.
Open a web browser such as Internet Explorer and type https://<host>/autodiscover/autodiscover.xml (where <host> is either <smtpdomain> or autodiscover.<smtpdomain>), and ensure an .xml file appears and that you do not have any certificate errors.
If the .xml file displayed has the text "this is a placeholder file", then IIS is not properly configured with an XML Handler.
2
Ensure the Managed Pipeline mode for CMxAutodiscoverAppPool and CMxEWSAppPool are both set to Integrated.
3
Access https://<host>/autodiscover/autodiscover.xml, and ensure you do not see the error message "this is a placeholder file".
4
From the Exchange server, open a web browser such as Internet Explorer, and type https://<host>/EWS/Service.asmx (where <host> is either <smtpdomain> or autodiscover.<smtpdomain>), and ensure an .xml file appears and that you do not have any certificate errors.
Ensure that the appropriate DNS entries have been made to route <smtpdomain> or autodiscover.<smtpdomain> to the computer running the Coexistence Manager for GroupWise Free/Busy Connector.
On the computer running Coexistence Manager for GroupWise Free/Busy Connector web services, run the Get-CmgAutodiscoverConfig cmdlet, and verify that the CmgAvailabilityUrl is set to https://<host>/EWS/Service.asmx (where <host> is either <smtpdomain> or autodiscover.<smtpdomain>).
On the computer running Coexistence Manager for GroupWise Free/Busy Connector web services, ensure that Get-CmgAvailabilityConfig is configured to communicate to the correct host and port for the computer running the Coexistence Manager for GroupWise GroupWise Free/Busy Connector service.

If you see the following error message: The maximum message size quota for incoming messages (65536) has been exceeded, you must increase the quota by using the MaxReceivedMessageSize property on the appropriate binding element.

If you are using OWA or Outlook and querying Free/Busy information for a GroupWise user, edit the Web.Config file in the EWS folder on the Coexistence Manager for GroupWise Web Server:

Add the maxReceivedMessageSize property to the file and set it to a large value:
<netTcpBinding>
<binding name="Coexistence Manager for GroupWiseFreeBusyClientSettings"
openTimeout="00:01:00"
receiveTimeout="00:01:00"
sendTimeout="00:01:00"
closeTimeout="00:01:00"
maxReceivedMessageSize="655360">
<security mode="None"/>
</binding>
</netTcpBinding>
Related Documents