It is always Best Practice when upgrading to a new version of any software is to take a backup of the existing settings. This will allow you to restore the software back to a known state without doing a system restore. In addition you are able to document the settings for future reference. 

Upgrading Binary Tree Freebusy

The upgrade should not take very long and should preserve most settings using the connections.config and web.config files. Please keep in mind that the installation must also be running on the Domino COEX server. Although this part of the installation is not time critical it should be done as soon as possible after upgrading the IIS server.

Tasks to perform on the IIS server

1. Backup Binary Tree Folder under Program Files.
2. Check that the Default Application Pool is set to support 32bit.
3. Check Default Web Site bindings.
4. Check Autodiscover connection strings.
5. Check Autodiscover Application Settings.
6. Check BTAvailability connection strings.
7. Check BTAvailability Application Settings.
8. Check BTRouter connection strings.
9. Check BTRouter Application Settings.
10. Make a copy of the connections.config and web.config files for Autodiscover, BTAvailability and BTRouter.
11. Document the account used in the BTCOEX_DEFAULT_FB_ACCESS_ACCOUNT setting in the Notes.ini file.
12. Ensure the BTCOEX_FOREIGN_WS_URL parameter is known prior to the upgrade (the fully qualified hostname please refer to the Comprehensive User Guide for further questions
13. Validate the account used by the setFBcred utility credentials are known (if running O365) (defined by the EWS-username within Application Setting-BTAvailability virtual directory in IIS
14. Installing, upgrading and reinstalling BT Freebusy
15. Installing, upgrading and reinstalling BT Freebusy on the IIS server.

Task to perform on the Domino server

1.  Installing, upgrading and reinstalling BT Freebusy on the Domino server.

1. Back-up Binary Tree Folder under  Program Files

    This is a simple File System copy. 

2. Check the Default Application Pool to support 32bit. Application Pools.

The DefaultAppPool should always have Enable 32-Bit Applications set to true. 

3. Check Default Web Site bindings.

It is important that the site is bound to SSL as Microsoft Exchange and O365 requires a SSL connection.

4. Check Autodiscover connection strings.

 Autodiscover(BTAD) – Handles the initial request from Outlook and passes it to the BTRouter. 

These are the typical settings for Autodiscover.

• Name - domino.corp5.cmtsandbox.com
• Custom - https://autodiscover.domino.corp5.cmtsandbox.com/BTRouter/Exchange.asmx

 These are the typical settings for Autodiscover.

• EAD - https://w28ehub13.corp5.cmtsandbox.com/Autodiscover/Autodiscover.xml

5. Check Autodiscover Application Settings.

Best Practice is to create subdirectories under C:\Log for Autodiscover, BT Availability and BT Router. To ensue logs are created consider leaving LogAllRequests to True for a few days to ensure the logs are created.

 The Autodiscover log will contain requests from Microsoft Exchange or O365.

 6.  Check BTAvailability connection strings.

 BTAvailability(BTAS) – Services the free/busy requests from Domino to Exchange. 

These are the typical settings for BTAvailability.

• EWS - https://w28ehub13.corp5.cmtsandbox.com/EWS/Exchange.asmx

7.  Check BTAvailability Application Settings.

Best Practice is to create subdirectories under C:\Log for Autodiscover, BT Availability and BT Router. To ensue logs are created consider leaving LogAllRequests to True for a few days to ensure the logs are created.

 8. Check BTRouter connection strings.

BTRouter(BTAR) – Services the freebusy requests from the Windows Coexistence server to Domino.

• BTAS-NOTES - https://w12dom9coex.corp5.cmtsandbox.com/BTAvailability
• EWS - https://w28ehub13.corp5.cmtsandbox.com/EWS/Exchange.asmx

9.  Check BTRouter Application Settings.

•  map:@domino.corp5.cmtsandbox.com - corp5.cmtsandbox.com

10. Make a copy of the connections.config and web.config files for Autodiscover, BTAvailability and BTRouter. 

C:\Program Files\Binary Tree\CMT for Coexistence\Autodiscover

C:\Program Files\Binary Tree\CMT for Coexistence\AvailabilityService

C:\Program Files\Binary Tree\CMT for Coexistence\AvailabilityRouter

11. Document the account used in the BTCOEX_DEFAULT_FB_ACCESS_ACCOUNT setting in the Notes.ini file.

BTCOEX_DEFAULT_FB_ACCESS_ACCOUNT=tom.cruise@corp5.cmtsandbox.com

12. Ensure the BTCOEX_FOREIGN_WS_URL parameter is known prior to the upgrade

BTCOEX_FOREIGN_WS_URL=http://autodiscover.domino.corp5.cmtsandbox.com/BTAvailability/Availability.asmx

13. Validate the account used by the setFBcred utility credentials are known (if running O365) (defined by the EWS-username within Application Setting-BTAvailability virtual directory in IIS

C:\Program Files\Binary Tree\CMT for Coexistence\AvailabilityService\bin

For Exchange environments.

For O365 Environments. 

14. Installing, upgrading and reinstalling BT Freebusy.

 Uninstalling BT Freebusy 

 All websites are deleted. However, the IIS directories on the file system is not removed.  

Add-AvailabilityAddressSpace -AccessMethod OrgWideFB -ForestName domino.corp5.cmtsandbox.com -UseServiceAccount:$true

w28ehub13.corp5.cmtsandbox.com

w12dom9coex.corp5.cmtsandbox.com 

autodiscover.domino.corp5.cmtsandbox.com 

Add-AvailabilityAddressSpace -AccessMethod OrgWideFB -ForestName autodiscover.domino.corp5.cmtsandbox.com -UseServiceAccount:$true

15. Installing, upgrading and reinstalling BT Freebusy on the IIS server.

The error if Domino is still running

Reinstall BT Freebusy

autodiscover.domino.corp5.cmtsandbox.com