| Supporting Blackberry Enterprise Server on | | | | Directory. This meant that we would have to |
| Exchange 2010 in “Greenfield’ | | | | deploy Windows Server 2008 R2 as a domain |
| Implementations | | | | requirement. As it happens, this is also a |
| | | | requirement for Exchange 2010, so our plan was |
| | | | | to start with a Windows Server 2008 R2 server |
| | | | | and simply perform a dcpromo to make the |
| Since RIM first began selling the Blackberry | | | | server a domain controller of the new Active |
| messaging devices, they have been the | | | | Directory. We began putting together a project |
| recognized leader in mobile e-mail solutions. | | | | plan that would guide our team through the |
| Combining a server infrastructure with directly | | | | implementation, and started going down the list of |
| interacts with Exchange, and a device which can | | | | requirements for the new environment. When we |
| receive e-mail in many cases sooner than Outlook, | | | | reached the mobility requirement, we realized that |
| the Blackberry has become a mainstay in | | | | we needed to support BES in the environment, |
| corporate messaging environments. As newer | | | | and began researching which version of BES was |
| versions of Exchange have been released, RIM | | | | compatible with Exchange 2010. What we found |
| has kept pace with Microsoft, by using native | | | | put a fly in the ointment of our plans; RIM does |
| Microsoft connectivity methods such as MAPI to | | | | not currently have a version of BES that supports |
| connect to the mailbox server for forwarding | | | | Exchange 2010! Not only did RIM not have a beta |
| e-mail to mailbox user’s Blackberry devices. | | | | that we could use, but there was no information |
| With Exchange 2007, there was a slight delay in | | | | at all about a projected date for a version that |
| providing support via the Blackberry Enterprise | | | | supports BES. This required that we rethink how |
| Server (BES), however, today we enjoy the | | | | we would deploy Exchange 2010. |
| same compatibility and reliability that we have | | | | Our first thought was that we could deploy |
| come to associate with BES integration. With | | | | Active Directory based on Windows Server 2008 |
| Exchange 2010, there is a bit of an issue with BES | | | | R2, with Exchange 2010, and then add Exchange |
| support. Previous to Exchange 2010, connectivity | | | | 2007 for BES compatibility. In migration of |
| to the mailbox servers was made via the MAPI | | | | Exchange 2007 to Exchange 2010, we have done |
| protocol. This standard allowed RIM to provide | | | | something similar in the past, where we would |
| compatibility relatively quickly. Even Exchange | | | | add Exchange 2010 to an existing Exchange 2007 |
| 2007, with its Client Access Server role used for | | | | organization, and decommission all but the mailbox |
| client connectivity, still allowed direct connectivity | | | | server that supported BES. But this was a new |
| to the Mailbox Server role via MAPI. With | | | | implementation of Active Directory, and a new |
| Exchange 2010, that has changed, and so we | | | | implementation of Exchange 2010. Furthermore, |
| have a slight issue for those of us developing | | | | Exchange 2007 is not support on Windows |
| “greenfield” or new implementations of | | | | Server 2008 R2, which further complicated things. |
| Exchange 2010 for our clients. | | | | Our Solution |
| BES: Our Client’s Requirement | | | | With all of these requirements, and issues, we |
| Our client currently has a deployment of | | | | came up with a very simple solution; we would |
| Exchange 2003. This implementation has significant | | | | deploy Exchange 2007 in a new Windows Server |
| reliability issues, and the client does not want to | | | | 2008 Active Directory forest. This would require |
| carry forward any issues from the Active | | | | deploy both a Client Access Server and a Mailbox |
| Directory and Exchange implementation. Because | | | | Server based on Exchange 2007. The reason we |
| of this, the client has specifically asked that we | | | | had to deploy the Client Access Server even |
| implement Exchange 2010 in a | | | | though we only need a Mailbox Server for BES |
| “greenfield”, or as a new implementation | | | | integration is because the first Exchange 2007 |
| of Active Directory and Exchange. Our initial | | | | server in a new Exchange organization must be a |
| thought was that we could simply deploy | | | | Client Access Server. Once the Exchange 2007 |
| Windows Server 2008 R2 with Exchange 2010, | | | | server is deployed, we would then deploy BES. |
| and implement a BES in that environment. Our | | | | Only after we have our Exchange 2007 |
| research determined that it would not be quite | | | | “environment” implemented, would we |
| that simple. Because BES does not yet support | | | | begin deployment of Exchange 2010. First we |
| Exchange 2010, we had to come up with an | | | | would install a Windows Server 2008 R2 server |
| alternate deployment method, one that provided | | | | as the operating system for our first Exchange |
| the “greenfield” implementation that the | | | | 2010 server, which would need to be a Client |
| customer desired, supported Exchange 2010 AND | | | | Access Server, just like Exchange 2007. We |
| supported BES. | | | | would then install the Exchange 2010 Client |
| Exchange 2007, Exchange 2010 and Windows | | | | Access Server, and the subsequent roles of |
| Server 2008 | | | | Exchange 2010, based on our individual design |
| The client wanted a deployment of | | | | specifications. Using this methodology, we are able |
| Microsoft’s latest and greatest Windows | | | | to provide Blackberry access via BES to our |
| platform to form the basis of their Active | | | | Exchange 2010 environment. |