Decommission Binary Tree DirSync and Coexistence – Part 3
Option 3 – HCL Directory Sync
For AD to Domino, if you are brave, you could battle your way through HCL Domino Directory Sync.
You would still need to decommission Binary Tree Coex and DirSync but switch to making your Group updates in AD and then back-sync them to Domino.
You need to set up a Directory Assistance to Active Directory and then configure Directory Sync in the Domino Directory.
Option 4 – Migrate to Quest’s alternative product
Contact Quest and work with their Professional Services or trusted partner to rip and replace the Binary Tree products with the Quest original tooling:
- Exchange Binary Tree Directory Sync Pro for Notes for Coexistence Manager for Notes.
- Exchange Binary Tree Integration for Notes for Coexistence Manager for Notes.
- Exchange Binary Tree Migrator for Notes for Migrator for Notes to Exchange.
This is likely to be a very significant undertaking with detailed project planning, elapsed time, downtime and professional services costs.
Probably as big as the original coexistence deployment.
New servers will be required and BAU operational staff will need to be pulled on to the project disrupting their current workloads. The interruption between decommissioning and going live will need to be very well planned to avoid any serious outage. There will of course be a completely different admin and user experience.
Unfortunately, the outcome of that project is simply having a working Coex and DirSync – which is what you already had anyway!
Our advice, decommission Binary Tree once and for all, and begin your decommissioning of Lotus Notes and Domino completely!
Decommission Binary Tree DirSync and Coexistence – Part 1
Decommission Binary Tree DirSync and Coexistence – Part 2
