With all of the great features provided by
Exchange UM comes the risk of ???putting all your eggs in one basket.??? Traditionally, if you
318 Chapter 10 ??? Integration with Exchange 2007 Unified Messaging
lost your e-mail system, voice mail would still be available, or vice versa. However, after
implementing Exchange UM, if your e-mail system goes down, so does your voice mail.
This is why it??™s important to ensure that you properly design your Exchange environment
before you deploy. If you require 99% uptime, you had better plan accordingly.
To properly implement Exchange 2007 UM, it is important to understand how Exchange
is architected and deployed. Implementing Exchange 2007 is somewhat different than
Exchange 2003. You will remember that implementing Exchange 2003 required installing all
Exchange components, then disabling those that were not needed, and then properly confi guring
a server to provide a specifi c service. For example, after installation you must properly perform
a series of confi guration steps to designate that server as a front-end server. Exchange 2007
introduces a concept known as server roles. Server roles allow you defi ne a server??™s purpose before
installing Exchange. By doing so, only the components needed to perform that specifi c function
are installed. Exchange 2007 incorporates fi ve server roles, each performing a particular
function (See Figure 10.1).
Figure 10.1 Exchange 2007 Server Roles
Integration with Exchange 2007 Unified Messaging ??? Chapter 10 319
Requirements
Before you jump in and deploy Exchange, it is important to understand the necessary
requirements, both hardware and software.
Pages:
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343