Other than an accommodation for multiple subdomains (see next subtopic below), no additional Exchange configuration is necessary for the FBC to work with an Exchange environment whose Outlook clients are all version 2007 or later, and where Exchange will connect with the FBC by Microsoft’s Autodiscover and EWS (without Exchange public folders). This Exchange-side scenario is illustrated here:
If you are configuring FBC for a hybrid Office 365: Remember that the FBC for a hybrid O365 is configured only between GroupWise and the local on-premises Exchange, while synchronization of the local Exchange to O365 is configured apart from Coexistence Manager for GroupWise (and documented separately by Microsoft). Configuration of Coexistence Manager for GroupWise’s FBC for a hybrid O365 is therefore the same as configuring for a local on-premises Exchange—as described here.
Coexistence Manager for GroupWise’s Free/Busy Connector can facilitate the flow of free/busy information among multiple subdomains supported by both the Exchange and GroupWise servers. To support this scenario, run the Add-AvailabilityAddressSpace cmdlet on the Exchange server or Office 365 for each GroupWise SMTP domain supported.
To configure Coexistence Manager for GroupWise’s FBC Web Server:
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 (Determine your FBC scenario) of this Guide. However, many production environments experience sufficient query volume to warrant separate servers to ensure optimal performance. The installation 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 in step 1 above. All Coexistence Manager for GroupWise Free/BusyConnector subcomponents are installed by the AutoRun utility included in the Coexistence Manager for GroupWise product kit.
IMPORTANT: Before you install, on any computer that will host any Coexistence Manager for GroupWise FBC web subcomponent, remove the IIS DefaultWebSite: In the navigation tree at left, right-click DefaultWebSite, and then select Remove from the pop-up menu. Coexistence Manager for GroupWise requires a dedicated server for its own web subcomponents. |
IMPORTANT: Remember, the Coexistence Manager for GroupWise AutoRun installer must be run on the computer where you want to install a particular subcomponent. If you are deploying the F/B Connector to two different computers, you must run the AutoRun installer twice—once on each computer. |
Remember: 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 in step 1 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.
Coexistence Manager for GroupWise includes an Autodiscover Certificate Wizard to automate much of the process of installing this necessary certificate for the Free/Busy Connector. The wizard can be launched from Coexistence Manager for GroupWise’s Management Console, on the Quest Web Services screen (under GroupWise Free/Busy Connector), as described in the procedure documented in the next subtopic below (see Using the Autodiscover Certificate Wizard to Obtain and Install a Certificate). Alternatively you can manually request and install a certificate, as described in the second subtopic below (see To Manually Request and Install a Certificate Using IIS 7.0–8.5).
To use the Autodiscover Certificate Wizard to install the necessary web services certificate using IIS 7.0–8.5:
1 |
In Coexistence Manager for GroupWise’s Management Console, on the Quest Web Services screen (under GroupWise Free/Busy Connector): Click the Autodiscover Certificate Wizard button to launch the wizard. |
a |
From a web browser, enter https://<Local_Certification_Authority_computer>/certsrv |
b |
c |
Select Submit a certificate request by using a base-64-encoded CMC or PKCS #10 file, or submit a renewal request by using a base-64- encoded PKCS #7 file. |
e |
f |
Click Submit. |
g |
4 |
5 |
Specify the path and filename of the certificate file downloaded in step 3 above, and click Finish to register the file and dismiss the wizard. |
1 |
From Internet Information Services, click Server Certificates. |
2 |
From the Actions Pane, select Create Certificate Request. |
3 |
Enter autodiscover.<smtpdomain> or <smtpdomain> for the primary domain and all required subdomains. Then click Next. |
4 |
5 |
Specify the file name, and click Finish. |
a |
From a web browser, enter https://<Local_Certification_Authority_computer>/certsrv |
b |
c |
Select Submit a certificate request by using a base-64-encoded CMC or PKCS #10 file, or submit a renewal request by using a base-64- encoded PKCS #7 file. |
e |
Copy and paste the text from the certificate request into the Saved Request box when you selected Submit a certificate request by using a base-64-encoded CMC or PKCS #10 file, or submit a renewal request by using a base-64-encoded PKCS #7 file. |
f |
g |
Click Submit. |
h |
1 |
From Internet Information Services, click Server Certificates. |
2 |
From the Actions Pane, select Complete Certificate Request. |
|
First, you must enable the SAN (Subject Alternate Name) flag on your CA. On the machine running CA services, run these commands at the command prompt to enable the flag:
When the SAN flag is enabled, you can create the certificate:
1 |
Open IIS on the machine running F/B and select the server. Scroll to the bottom, open Server Certificates, and click on Create Certificate Request. |
2 |
For the common name, enter something appropriate for your larger domain. For example, for a domain alejandro.xyzcorp.com, the common name on the certificate is *.xyzcorp.com. (This is somewhat generic, as we will later add specific namespaces to the certificate.) |
4 |
Open the certificate request you just created, and select and copy all of the text. |
5 |
Open the certificate web enrollment page for the CA of your domain— e.g., https://hostname/certsrv. Then select Request a Certificate, and then select Advanced Certificate Request. |
6 |
Select Submit a certificate request by using a base-64-encoded CMC or PKCS #10 file, or submit a renewal request by using a base-64-encoded PKCS #7 file. |
7 |
In the Base-64-encoded certificate request box, paste all of the text that you copied from the text file in step 4 above. |
8 |
9 |
In the Additional Attributes box, enter any alternate-domain information in this format: |
10 |
12 |
Go back to IIS and click Complete Certificate Request. |
13 |
For the Filename containing the certification authority’s response, click the Browse button and select the certificate you just saved. (Be sure to change the file type to *.* instead of *.cer, or you won’t see the file you saved—since it is a .P7B extension.) Type a friendly name that is easy to remember and identify so you can find your certificate on the list later. You should then see your new certificate on the list. |
15 |
Click the Details tab, and scroll down to Subject Alternative Name. Highlight this field, and you should see all of your domains in the Details box. |
Now bind your certificate to the HTTPS protocol on the QuestFreeBusy website:
2 |
3 |
4 |
In the Edit Site Binding window, in the SSL certificate drop-down list: Select the certificate you just created. |
5 |
Click OK. |
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy