Technical findings while developing Essential Business Server v2

During development of EBS v2, “we tackled quite a few challenges in integrating Microsoft server technologies. We developed solutions and workarounds, proved them through exhaustive testing, and implemented them in EBSv2. Due to external factors, EBS v2 did not release to public. Therefore, we decided to gather some of our solutions and findings, and share […]

During development of EBS v2, “we tackled quite a few challenges in integrating Microsoft server technologies. We developed solutions and workarounds, proved them through exhaustive testing, and implemented them in EBSv2. Due to external factors, EBS v2 did not release to public. Therefore, we decided to gather some of our solutions and findings, and share it with our community. 1. Performing an 'isolated' installation of Exchange 2010: There’s no supported way to rollback a failed Exchange installation from forest. However, there’s a proven way to control and contain the Exchange installation inside the forest, so that in case it fails and blocks, it doesn't spread across domain and leave forest in an undesirable state. We implemented this approach in our automated EBS v2 installation and verified it in Beta and RC0 releases,” notes Microsoft EBS team.

Full Article: Our Technical Findings While Developing EBS v2