81461.book Page 404 Wednesday, December 12, 2007 4:49 PM 404 Chapter Planning a Highly Available Exchange Server 2007 Implementation When configuring the CCR cluster, it is important to take into account the automatic database mount settings You can configure the server by using the Set-MailboxServer cmdlet and setting AutoDatabaseMountDial property with one of the following values: Lossless: The databases will not automatically mount on the passive node until all of the logs have been copied to the passive node If the active node goes offline, the databases will not be mounted until the logs are able to be recovered from the failed node GoodAvailability: The databases will mount on the passive node as long as the copy queue length is less than or equal to two Exchange will continue to copy the remaining logs from the failed node and attempt to mount the database BestAvailability: The databases will mount on the passive node as long as the copy queue length is less than or equal to five Exchange will continue to copy the remaining logs from the failed node and attempt to mount the database These settings affect the automatic mounting of the databases in a CCR cluster; an administrator can choose to force a database mount in case a failover occurs with data loss Figure 9.14 shows an example of using Set-MailboxServer to modify the AutoDatabaseMountDial setting from the default of BestAvailability to Lossless FIGURE 9.14 Using Set-MailboxServer to modify the AutoDatabaseMountDial setting Because CCR uses log-file replication to provide data redundancy, it is possible during a hard failover to the second node that log files are damaged on the second node This may cause email to be lost A feature that reduces this possibility is the transport dumpster The transport dumpster is enabled automatically on Hub Transport servers only for CCR clusters The Hub Transport servers will maintain a queue of recently delivered email messages to mailboxes that reside on a CCR clustered Mailbox server If a hard failover occurs that has the possibility of lost data, the clustered Mailbox server will notify the Hub Transport servers to redeliver email messages from the transport dumpster The clustered Mailbox 81461.book Page 405 Wednesday, December 12, 2007 4:49 PM Planning a Data-Redundancy Implementation 405 server will then reprocess the messages and deliver the non-duplicated items Unfortunately, the transport dumpster will not assist in recovering the following: Appointments (not meeting requests) Property updates (i.e., flagging, mark as read, etc.) Tasks Draft email messages created in Office Outlook in online mode Although the Microsoft Clustering Services Cluster Administrator tool can be used to manage the failover of a CCR cluster, it is not recommended because it does not contain logic to check the health of the replication status before it transfers the clustered Mailbox server Using the Cluster Administrator can lead to damaged databases The preferred method of managing the clustered mailbox is to use the Move-ClusteredMailboxServer cmdlet in the Exchange Management Shell as pictured in Figure 9.15 Using the cmdlet allows for an administrator to provide a documented reason for moving the clustered Mailbox server, and it properly checks the health of the server before performing the failover FIGURE 9.15 Using Move-ClusteredMailboxServer on a CCR server Deciding Which Mailbox-Availability Strategy to Adopt With so many options, it can be difficult to decide which mailbox-availability strategy to use in a specific situation Table 9.5 can help you to determine which availability strategy has specific features or limitations TABLE 9.5 Mailbox Availability Strategy Features Feature LCR CCR Can have only one database per storage group X X Can run other roles X SCC 81461.book Page 406 Wednesday, December 12, 2007 4:49 PM Chapter 406 TABLE 9.5 Planning a Highly Available Exchange Server 2007 Implementation Mailbox Availability Strategy Features (continued) Feature LCR CCR Can host public-folder replicas X Can span data centers Simplest, least expensive X X X Requires shared storage Provides data redundancy SCC X X Provides server redundancy X X X Using Dial-Tone Recovery Dial-tone recovery has been a recommend fast recovery method since Exchange Server 2003 When a database has failed and cannot be mounted, dial-tone recovery can be done Dial-tone recovery moves the damaged database out of the original database location, and then a blank database is mounted This database has no data in it, but it allows the end users to be able to connect to a mailbox and to send and receive new email while the old data is recovered The old data could be recovered by either repairing the database or by performing a restore to the recovery storage group Once the data is recovered, there are two options: The data can be merged back into the production mailboxes using the Recover Mailbox Data feature of the recovery storage group The data can be swapped into the location of the dial-tone database so that the dial-tone information can be merged into the recovered database Because mounting dial-tone databases loses mailbox rules, delegate data, and offline folder store encryption keys, administrators will often swap the original database back into the production storage group and merge the dial-tone database in using the Recover Mailbox Data feature of the recovery storage group Now that Exchange Server 2007 allows for database portability, these dial-tone recovery tasks can be done on a standby server rather than having to complete the recovery on the server where the original failure occurred More information about problems that can arise when performing a dial-tone recovery can be found at http://support.microsoft.com/?kbid=282496 81461.book Page 407 Wednesday, December 12, 2007 4:49 PM Implementing Database Portability 407 Managing Employee Relations During an Email Outage In real-world environments, emails are a very critical piece of business So when email is down, tempers are up If a failure occurs and the database needs to be repaired using the Extensible Storage Engine Utility (ESEUTIL) or recovered from a tape, there is usually a better end-user perception of the outage if the users are restored to service using a dial-tone recovery It is often difficult for Exchange administrators to admit that restores and repairs have a tendency to fail the first time, especially when you’re dealing with the executives’ email and your job is at stake A good way to not fall into this trap is to limit the length of time that you spend on trying to repair or restore the database, so that the end users are not left in the lurch without any access to Exchange services You should make it standard practice to mount a dialtone database if you aren’t able to repair or restore the database within 30 minutes After mounting the dial-tone database, send an email to the users describing the reason of the absence of their old mailbox content and what steps are being taken to restore that data Following this procedure should reduce the number of times your manager has to come to you with sweat running down his brow and scream at you that he is under a lot of pressure so you need to get Exchange working! Implementing Database Portability One of the most painful aspects in previous versions of Exchange Server is the fact that moving a database between servers wasn’t a supported way of moving users or of recovering from a server failure Exchange Server provides for mounting databases on different servers in the same Exchange organization and then modifying the mailbox objects so that they are associated with the location of the new database To allow for database portability, Exchange 2007 allows any mailbox database to be mounted on any other Exchange 2007 Mailbox server in the organization Database portability does not work with public-folder databases There are a number of scenarios in which you would use database portability: Recovering mailbox data between geographical sites Recovering a clustered Mailbox server to another operational server Using a portable dial-tone recovery (You can this by mounting empty databases on a new server while database restores are being done.) 81461.book Page 408 Wednesday, December 12, 2007 4:49 PM 408 Chapter Planning a Highly Available Exchange Server 2007 Implementation Database portability requires only a few steps that need to be followed when moving a database from one server to another The overview of the process is as follows: Make sure the database was shut down cleanly or perform a soft recovery if the database isn’t in a clean state Use either the Exchange Management Shell or Exchange Management Console to create a new database with the same name on the new server; however, not try to mount the new database Set the new database to allow a restore to overwrite the database Figure 9.16 shows using the Exchange Management Shell to create the new database and setting it to allow a restore FIGURE 9.16 Using the Exchange Management Shell to create a new database Move the database files to the new server in the location you specified for the new database Mount the new database with the Exchange Management Shell or Exchange Management Console Use the MoveMailbox cmdlet with the ConfigurationOnly option to point the mailbox configuration to the new location Figure 9.17 shows an example of running Get-Mailbox to gather the mailboxes from the old database and piping the output to the Movemailbox cmdlet with the -ConfigurationOnly option FIGURE 9.17 Using MoveMailbox with the ConfigurationOnly switch 81461.book Page 409 Wednesday, December 12, 2007 4:49 PM Exam Essentials 409 It is important to know how using database portability affects your user base Since the user’s mailbox is now on a server with a different name, the user’s client will need to be able to locate where the mailbox has been moved to without the original server being available As you can see in Table 9.6, both Office Outlook 2007 and Office Outlook Web Access are automatically redirected to the new location Problems may occur when older clients are in use These clients will need to be manually reconfigured, or an administrative script can be run on each of the users’ computers to reconfigure the older versions of Outlook TABLE 9.6 Client Redirection Methods Client Redirection Method Office Outlook 2007 Automatic Uses Autodiscover Outlook 2002 and 2003 Manual Needs to be reconfigured manually Office Outlook Web Access Automatic Uses Active Directory Summary In this chapter we talked about availability options for each of the Exchange server roles You saw how use of network load balancing as well as DNS round-robin and multiple MX records can provide high availability for most of the Exchange roles Then you learned how Mailbox roles can use LCR, CCR, and SCC to improve availability We also discussed the specific requirements for each of the availability options Last you learned how to leverage database portability and dial-tone recovery to provide rapid recovery during failure situations, even when a server is unrecoverable or if recovery will take longer than the permitted recovery window Exam Essentials Know the differences between the Mailbox role availability types In the exam you will most likely be asked to differentiate between the ways to make your Mailbox servers more available You need to know which server types provide data redundancy and which provide server redundancy only Remember that the single-copy cluster requires shared hardware and that local continuous replication and cluster continuous replication use server-attached storage devices Remember which servers can have public-folder stores in an enterprise environment and which ones require that only one database be in each storage group Know how to make all roles redundant Each role can be made redundant by adding multiple servers Most roles, however, require additional hardware or configuration to make the 81461.book Page 410 Wednesday, December 12, 2007 4:49 PM 410 Chapter Planning a Highly Available Exchange Server 2007 Implementation solution failure-resilient Be sure to understand the pros and cons for each of the redundancy options and what is required to configure each of them Know how database portability opens new methods of recovery Database portability is the new feature that allows a database to be mounted on any Exchange server in the organization Tools have been created to allow mailbox configuration to be modified so that the mailboxes are pointed to the new location New features in Microsoft Office Outlook 2007 also allow for the client computers to locate the new server the mailbox is hosted on 81461.book Page 411 Wednesday, December 12, 2007 4:49 PM Review Questions 411 Review Questions You have been asked to design a redundant Mailbox server design The business requires that the design allow for a single server failure Which server solutions could you design to meet this requirement? A LCR B CCR C SCC D Add two RAID arrays with a mirror set to a server The standard remote office deployment consists of two servers: one that has the Hub Transport and Client Access roles installed, and one that has the Mailbox role installed When the Hub Transport server is offline, internal email message delivery is impacted to the remote office mailboxes What can be done to reduce this effect? A Add an Edge Transport server at the remote office and create an MX record in the domain for it B Add a second Client Access server at the remote office and create a round-robin DNS entry for both C Create an MX record for the Mailbox server at the remote office D Add a second Hub Transport server at the remote site You have been asked to design a new redundant Mailbox server design The business requires that you allow for data redundancy and server redundancy Which solution could you use to meet the business requirements? A LCR B CCR C SCC D Add two RAID arrays with a mirror set to a server You have been asked to design a new redundant design for users to access Outlook Web Access The business requires that you allow for server redundancy and automatic failover Which solutions could you use to meet the business requirements? A Software network load balancing B Hardware network load balancing C Round-robin DNS entries D Multiple MX records 81461.book Page 412 Wednesday, December 12, 2007 4:49 PM 412 Chapter Planning a Highly Available Exchange Server 2007 Implementation One of your Mailbox servers has had a database failure The database may take hours to restore or repair The business requires that you allow users to be able to send and receive email as quickly as possible Which option will provide for the business requirement? A A dial-tone database B A recovery storage group C Database portability D Streaming database restores Your company plans to deploy standard Mailbox server roles with storage groups and 10 databases to each of the remote offices The servers were purchased with a single storage device What would need to be done to optimally reconfigure these servers to support LCR? (Choose all that apply.) A Create five additional storage groups and distribute the mailbox databases evenly B Add a second server C Add a second storage controller D Add a second storage device Your company plans to deploy centralized Mailbox servers The servers need to be redundant and minimize data storage on the SAN due to budgetary constraints What configuration would meet the business needs? A LCR B SCC C CCR D Network load balanced servers You need to deploy an SCC cluster with the fewest servers as well as provide redundancy for Hub Transport servers What is the lowest number of servers required to meet the requirements? A B C D You need to provide redundancy for your company’s three Edge Transport servers You need to have each server used equally Which of the following are supported options? (Choose all that apply.) A Create MX records with the same preference weight for the host name of each server B Create MX records with the sequential preference weights for the host name of each server C Create a network load balanced cluster with each server with a single MX record pointing to the host name of the cluster D Create MX records with the same preference weights for an alias record of each server 81461.book Page 413 Wednesday, December 12, 2007 4:49 PM Review Questions 413 10 Which tool should you use to manage the failover process on a CCR cluster? A Exchange Management Shell B Exchange Management Console C Cluster Administrator D Server Manager 11 Which of the following is not a requirement for a supported CCR cluster? A A shared disk system B A public and private network interface C Server hardware listed on the Microsoft website D Windows 2003 Server Enterprise or later 12 Which of the following commands would you use when moving a database between servers? A Move-StorageGroupPath B Move-DatabasePath C Move-ClusteredMailboxServer D MoveMailbox 13 On an Exchange server with high disk I/O utilization that also requires redundancy, which RAID type would you select? A RAID B RAID C RAID 10 D RAID 14 When using network load balancing for web services, which property should be set to the loadbalanced fully qualified domain name? A ExternalURL B InternalURL C ExternalAuthenticationMethods D Instance 15 You added two MX records (smtp1.domain.com and smtp2.domain.com) with a preference weight of 20 for domain.com You have added another server (smtp3.domain.com) at another location with a preference of 40 What behavior will this cause? A The smtp3.domain.com will be used first; if it is unavailable the others will be loadbalanced B All three servers will be load-balanced, smtp3.domain.com will be used only one-third of the time C The smtp1.domain.com and smtp2.domain.com will be load-balanced first; if both are unavailable smtp3.domain.com will be used D All three servers will be load-balanced; smtp3.domain.com will be used two-thirds of the time 81461.book Page 478 Wednesday, December 12, 2007 4:49 PM 478 Chapter 12 Planning the Exchange Server 2007 Server Role Deployment When defining the configuration or server roles, disk sizing is also a factor; we will discuss in detail in the next section how the space varies for each server role However, all of the Exchange roles require 1.2 GB of disk space on an NTFS-formatted volume that Exchange is installed to, and an additional 200 MB of space on the system partition We are now going to discuss the configuration of each of the roles and see how to create a configuration using standard guidelines The processor-core configuration recommendations are summarized in Table 12.1 and the memory configuration recommendations are summarized in Table 12.2 TABLE 12.1 Summary of Server Processor Configuration Server Role Recommended Number of Processor Cores Recommended Maximum Number of Processor Cores Client Access Edge Transport Hub Transport Mailbox Unified Messaging 4 Multiple server roles 4 TABLE 12.2 Summary of Server Memory Configuration Server Role Recommended Amount of RAM Recommended Maximum Amount of RAM Client Access GB or GB/core GB Edge Transport GB or GB/core 16 GB Hub Transport GB or GB/core 16 GB Mailbox GB + 2–5 MB/mailbox 32 GB Unified Messaging GB or GB/processor GB Multiple server roles GB + 2–5 MB/mailbox GB 81461.book Page 479 Wednesday, December 12, 2007 4:49 PM Defining Server Configurations Based on Roles 479 Configuring the Client Access Server Role If you are familiar with previous versions of Exchange Server you may immediately think that sizing a Client Access server would fall into your previous front-end server sizing guidelines The two previous versions of Exchange ran most of its processes within the STORE.EXE process on the back-end server; however Exchange Server 2007 processing has now been split into several individual roles The Client Access role is now responsible for converting content for IMAP4 and POP3 clients Since the Streaming Store file (.stm) is not present in Exchange Server 2007, all data presented to non-MAPI clients will need to be converted The Client Access server is now also responsible for rendering all of the web content This is done in a worker process in IIS that makes MAPI calls to the proper Mailbox server roles to render mailbox data A Client Access server role’s main services are as follows: Outlook Web Access Exchange ActiveSync Outlook Anywhere Exchange Web Services Autodiscover Offline address book distribution POP3 IMAP4 The Client Access server role is an important role indeed The minimum hardware configuration for a Client Access server role is one processor core; however, four processor cores are suggested for servers with moderate to heavy utilization The current sizing guidelines show that anything above four processors cores provides little benefit In a standard environment the suggestion is GB of RAM for each processor core to be used If the Client Access server is under high utilization or is primarily used for Outlook Anywhere, GB for each processor core should be used The disk I/O processing done on a Client Access server is negligible; most modern SCSI- or SAS-based disk subsystems should be able to handle the amount of disk I/O for a Client Access server 81461.book Page 480 Wednesday, December 12, 2007 4:49 PM 480 Chapter 12 Planning the Exchange Server 2007 Server Role Deployment Configuring the Edge Transport Server Role The Edge Transport role is a new role meant to be deployed in a perimeter network to route email traffic from the Internet into the Hub Transport servers inside the corporate network The Edge Transport server will send and receive SMTP messages as well as perform antispam tasks and antivirus scanning and apply customized rules on transported email messages The server can also maintain SMTP message queues for both inbound and outbound email The minimum configuration required is only a single processor core; however two processor cores are recommended for most Edge Transport implementations, with a maximum recommended number of processors being four Only GB of memory for each processor core is recommend to support email services; however, in very high-utilization environments GB per processor can be used if additional Edge Transport servers cannot be deployed Disk size is one of the important factors to consider for Edge Transport server roles First you must determine the amount of disk space required To make a reasonable estimate on disk sizing it is helpful to determine the number of email messages that the Edge Transport server will receive in a given period of time and the amount of time that would be required for the Edge Transport server to queue messages in both standard operation and in the possibility of a messaging-system failure If, for example, the Edge Transport server averages receiving 100,000 email messages each day and needs to be able to queue messages for up to 24 hours with an average size of 40 KB of each message, the queue could consume GB of disk space in just 24 hours Of course, there are other items that must be stored on disk, such as the protocol, message-tracking, agent, and connectivity logs, as well as the antivirus quarantine These logs, if kept for seven days, can easily consume GB of additional space using our example Also, by default the Edge Transport server requires GB of free disk space before it initiates back pressure, an internal process that prevents the system from being overwhelmed by new messages so that it will be able to deliver the already received messages The result of the back pressure process is that the Exchange server will refuse new connections If the total required is 16 GB (4 GB for the queue, GB for logs and quarantine, and GB for free space) it is suggested that you add at least 20 percent for future growth and for variance Disk I/O is the last factor that needs to be considered for an Edge Transport server role If the server has enough memory installed, the message queue should stay cached in memory The actual number of disk I/O per second (IOPS) required varies greatly from environment to environment and may need to be observed in production before accurate sizing can be done Configuring the Hub Transport Server Role The Hub Transport role handles delivery of email within the Exchange organization These servers handle virus scanning, transport rules, and message routing At least one Hub Transport server must exist in each Active Directory site that has an Exchange Mailbox role Since they both provide similar services, the Hub Transport role has similar configuration parameters to the Edge Transport role All email sent by any Exchange user must go through at least 81461.book Page 481 Wednesday, December 12, 2007 4:49 PM Defining Server Configurations Based on Roles 481 one Hub Transport server even if the mail recipient and sender have mailboxes located on the same Mailbox server This means that the Hub Transport role is a critical piece in the Exchange organization, and if it is improperly sized, email-delivery speed can be affected and end users may notice The minimum configuration required is only a single processor core; however, four processor cores are recommended for most Hub Transport implementations, with a maximum of eight recommended Only GB of memory for each processor core is recommend to support email services, but in very high-utilization environments GB per processor can be used if additional Hub Transport servers cannot be deployed When Edge Transport servers are used, disk sizing is fairly easy since only locally bound mail will ever need to be queued Just like with the Edge Transport role, it is necessary to know how much email will need to be queued; this is a function of the number and size of email messages received over a period of time and how long that the queue would need to be sustained Add to that number space for message tracking and protocol logs Disk I/O can also be a factor for a Hub Transport server; however, if the server has enough memory installed the message queue should stay cached in memory The actual number of I/Os required varies greatly from environment to environment Obtaining the actual requirements would require evaluating a production server in your environment Configuring the Mailbox Server Role The Mailbox role provides the database services for mailboxes and public folders This server role is the most important and the most difficult to get configured properly If the Mailbox server is not configured to handle user load, the end users will be affected When end users are affected, it usually translates into help-desk calls and an overall bad end-user perception of the messaging system For a detailed discussion on what goes into determining disk I/O requirements for the Mailbox role, see Chapter 11, “Planning the Exchange Server 2007 Storage Group Deployment.” The minimum memory configuration for a Mailbox server is GB; however, the recommendation is to have an additional to MB for each user mailbox The amount of RAM installed will also limit the number of storage groups that should be configured For every four storage groups, GB of RAM needs to be added The maximum recommendation is 32 GB of RAM since at this point for the increased cost of the more dense RAM DIMMs there are diminishing returns Table 12.3 lists the minimum memory requirements based on the number of storage groups Note that these are just the minimum requirements and that if you follow the “2 GB plus MB per user” rule, you won’t have any problems meeting these requirements 81461.book Page 482 Wednesday, December 12, 2007 4:49 PM 482 Chapter 12 Planning the Exchange Server 2007 Server Role Deployment This table can also be used to determine the number of storage groups that should be created based on the amount of memory your server has configured As an example if you were to have a Mailbox server that needs to support 2,000 user mailboxes with a heavy usage profile, you would need 12 GB of RAM (2 GB + 2000 × MB = 12 GB) If you have 12 GB of memory you can have a maximum of 24 storage groups configured TABLE 12.3 Groups Minimum Amount of Memory Required Based on the Number of Storage Number of Storage Groups Minimum Amount of Memory 1–4 GB 5–8 GB 9–12 GB 13–16 GB 17–20 10 GB 21–24 12 GB 25–28 14 GB 29–32 16 GB 33–36 18 GB 37–40 20 GB 41–44 22 GB 45–48 24 GB 49 or 50 26 GB See Chapter 11 for a detailed discussion on determining disk design for Mailbox server roles 81461.book Page 483 Wednesday, December 12, 2007 4:49 PM Defining Server Configurations Based on Roles 483 When I Was a Kid All I Had Was 640 KB of RAM! You may wonder why so much memory is required to run Exchange Server 2007, when Exchange Server 2003 and earlier were pretty much capped at GB of RAM In the real world does Exchange really need so much memory? We have touched on this a few times in this book; the memory requirement is actually an improvement This has to with Exchange Server 2007 running on a 64-bit operating system This gives the Exchange process a larger amount of memory that it can address Again you may ask, just because you can does it mean that you have to or that you should? You may even say that this is all because of sloppy programming and “code bloat.” We can understand your frustration, as you have to try to justify ordering 32 GB of RAM for your new Exchange server to the CIO of your company You just know he is going to ask why he needs to order four times more memory for this new version than he had to for the previous version Here are some reasoning points to use to convince your CIO to sign on the dotted line for your Exchange Server 2007 project: More Memory, Lower Disk I/O Requirements Adding memory to the Exchange server allows the information store to cache more data in memory, which reduces the number of times it must read and write from disk As we mentioned elsewhere in this book, this increased cache enabled by running on a 64-bit operating system can reduce disk I/O by up to 70 percent If your company is having disk I/O problems running Exchange 2003 servers now you may be able to use the same configuration and still add more users The other possibility is that you can deploy the Exchange Server 2007 servers with direct-attached SAS or SATA disks or even iSCSI systems rather than using an expensive Fibre Channel–attached SAN More Features, Fewer Complaints Adding memory and upgrading processors also adds new features such a messaging records management, content indexing that works (previous versions were rarely used since they slowed down the server too much to be useful), built-in Unified Messaging, and complex transport rules, just to name a few Do some research on what the top 10 problems are with messaging at your company, and map how Exchange Server 2007 addresses those issues Configuring the Unified Messaging Server Role The Unified Messaging role provides a new feature of Exchange Server 2007: a telephone interface called Outlook Voice Access (OVA) This interface allows for storing of voice mail messages in users’ mailboxes as well as the ability for them to use the telephone to access the 81461.book Page 484 Wednesday, December 12, 2007 4:49 PM 484 Chapter 12 Planning the Exchange Server 2007 Server Role Deployment contents of their mailboxes To use Unified Messaging, specialized hardware is required to interface the Private Branch eXchange (PBX) to the Unified Messaging server This hardware is attached to the PBX and communicates with the Exchange Unified Messaging server with Voice over IP (VoIP) The Unified Messaging role is responsible for converting WAV voicemail files to WMA for storage in the mailboxes, which is very processor-intensive This means the minimum number of recommended processors cores for a Unified Messaging server is four; however, adding more than four processor cores is not recommended due to minimal returns The recommended amount of RAM is GB or GB of RAM for each processors core, up to a maximum of GB Other than for the Exchange installation files, little storage is required If you need to support multiple languages with the Unified Messaging server you will need to add a language pack, however, which will consume 500 MB of additional disk space A small amount of additional space will be required for temporary files and protocol logs Configuring Multiple Server Roles As mentioned earlier, multiple server roles can be installed on the same server with some rules The Edge Transport role cannot be installed on a server with any other Exchange role and should also be on a server that is not a member of the same Active Directory forest as the other Exchange servers Only the Mailbox role can run on a cluster node, so there is no way to install any other role when you are using a cluster You can, however, install other roles on a Mailbox server using local continuous replication (LCR) In many scenarios, for small or remote offices it makes sense to combine server roles In a remote office, rather than deploying five servers you may deploy only three: one Mailbox server with LCR and two combined Client Access and Hub Transport servers The basic guidance for multiple role deployments is that processor and memory configuration is additive If you have a Client Access and Hub Transport combined server you would start off with GB of RAM (2 GB + GB base memory configuration) In smaller sites it may even make sense to combine the Client Access, Hub Transport, and Mailbox server roles on a single server If some redundancy is needed, you can use local continuous replication to protect the data and provide the needed Client Access and Hub Transport services Verifying that Dependent Services Meet Requirements After getting the server configuration defined, the dependent services and server role prerequisites need to be met We will now consider the requirements that must be met in Active Directory and the Exchange Organization Then we will discuss the specific server roles and the software requirements that must be met before Exchange can be installed on them Although Exchange has its own requirements, it also requires certain elements from other services Having an improperly configured Active Directory domain or underpowered server 81461.book Page 485 Wednesday, December 12, 2007 4:49 PM Verifying that Dependent Services Meet Requirements 485 domain controllers can cause severe messaging issues The domain must meet some basic requirements, as follows: Active Directory functional level must be Windows 2000 native or higher If cross-forest trust is necessary or if availability information is required across forests, the forest functional level must be set to Windows 2003 native mode Active Directory Schema Master must be Windows Server 2003 with Service Pack or higher A domain controller that is also a global catalog server in each Active Directory site that will have an Exchange server must be Windows Server 2003 Service Pack or higher Domain controllers that are non-English must have the hotfix from Microsoft Knowledge Base article KB919166 (http://support.microsoft.com/kb/919166) or have Windows Server 2003 Service Pack installed If you are installing Exchange Server 2007 into a new Exchange organization it is good to remember that you will not be able to install an Exchange 2003 server at a later date If you require an Exchange 2003 server in the future you will need to install it before installing Exchange Server 2007 If you have previous versions of Exchange installed, notice the following requirements: No Exchange 5.5 or older servers can exist in the Exchange organization All Exchange Server 2000 computers must have Service Pack installed plus the post–Service Pack rollup found in Microsoft’s Knowledge Base article KB870540 (http:// support.microsoft.com/kb/870540) All Exchange Server 2003 computers must have Service Pack installed After all of these requirements have been satisfied the schema and forest preparation can be run When previous versions of Exchange are present the PrepareLegacyExchangePermissions switch must be used when installing the first Exchange server This option maintains permissions required for the Exchange 2000/2003 Recipient Update Service to function properly When this step is complete the forest schema can be updated with the PrepareSchema setup switch This will add the schema attributes to the Active Directory forest Then setup can be run with the PrepareAD switch so that the permission groups are created and permissions are applied Last, if there are multiple domains, setup can be run with the PrepareDomain or the PrepareAllDomains switch This will make sure that the proper groups and permissions are created in other domains in the forest so that Exchange can function properly Now that the schema and directory are prepared, the individual Exchange servers can be prepared for installation Each Exchange server must meet the following requirements before setup can be successful: Microsoft NET Framework Version 2.0 installed Microsoft Management Console (MMC) 3.0 installed Windows PowerShell installed Membership in the same Active Directory forest; applies to all server roles except for Edge Transport Active Directory Application Mode (ADAM) SP1 installed; applies to Edge Transport server role 81461.book Page 486 Wednesday, December 12, 2007 4:49 PM 486 Chapter 12 Planning the Exchange Server 2007 Server Role Deployment If all of the required components are not installed when the Exchange install is run, the installer will prompt you to install them All Exchange server roles besides the Edge Transport role must be a member of the domain It is important that DNS name resolution is working properly for the Exchange servers The servers should also be properly registered in DNS so that other servers will be able to resolve their IP addresses To facilitate domain lookups, the default DNS suffix should be the same as the domain you have joined If the computer’s domain suffix does not match the Active Directory domain that the machine is joined to, the Active Directory domain suffix should be added to the domain search order on the network adapters Requirements for the Client Access Server Role The Client Access server role has some specific software requirements If the requirements are not met, the installation will not be able to complete To successfully install the Client Access server role, you must also install the following components: Internet Information Service (IIS) 6.0, World Wide Web Service Remote procedure call (RPC) over Hypertext Transfer Protocol (HTTP) proxy ASP.NET version 2.0 If you are using Windows Server 2003 R2 or later, all of the aforementioned components can be installed using the Add/Remove Windows Components wizard available in the Control Panel You need to install the RPC over HTTP Proxy only on Client Access servers that will provide Microsoft Outlook Anywhere access Requirements for the Edge Transport Server Role It is important for all server roles to have proper internal DNS name resolution This is more difficult for an Edge Transport server than for other server roles since it is not joined to the domain and is typically located in a perimeter network When using Microsoft terminology, a perimeter network is the same as a demilitarized zone (DMZ) This is a network segment that is exposed to the Internet and has limited to no access to the internal network The networks are typically segmented with a firewall The SMTP protocol is heavily reliant on DNS for delivery of email messages Having DNS configured properly is thus crucial for a successful install of the Edge Transport role To start with, the server must have a DNS suffix defined; otherwise setup will fail This may sound 81461.book Page 487 Wednesday, December 12, 2007 4:49 PM Verifying that Dependent Services Meet Requirements 487 strange; however, the machine’s DNS suffix is usually set when the machine is joined to a domain Since the Edge Transport server should not be part of a domain, it will not by default have a DNS suffix set The server should also be able to resolve the Hub Transport servers that it needs to communicate with directly This can be done in the following ways: Create A records, or host records, for the Hub Transport servers in the external DNS servers that the Edge Transport servers use Modify the Hosts file on the Edge Transport server to include the records for the Hub Transport servers The hosts file is stored in the X:\Windows\System32\Drivers\Etc folder The Hub Transport servers should also be able to resolve the names of the Edge Transport servers This can be accomplished using the same methods as for the Hub Transport servers: Create A records for the Edge Transport servers in the external DNS servers that the Hub Transport servers use Modify the Hosts file on the Hub Transport server to include the records for the Edge Transport servers The hosts file is stored in the X:\Windows\System32\Drivers\Etc folder There are also a few software requirements specific to the Edge Transport role Since the Edge Transport server provides its own SMTP service and no longer relies on the Internet Information Services (IIS) version of SMTP, you cannot have the SMTP service or the NNTP service installed You must, however, install Active Directory Application Mode (ADAM) on the Edge Transport server role No customization is required during the installation of ADAM When the Edge Transport role is installed it will complete the configuration of ADAM Requirements for the Hub Transport Server Role The Hub Transport role has most of its requirement met with the base Exchange requirements However, you cannot have the Internet Information Services (IIS) 6.0 SMTP services or the NNTP service installed That’s because Exchange Server 2007 no longer relies on IIS to provide the base SMTP services, as SMTP has been completely rewritten If the IIS version of SMTP were installed during the installation of the Hub Transport server, binding conflicts would keep the Exchange SMTP service from functioning properly—therefore the Exchange installation requires the service to be removed before installation will continue Requirements for the Mailbox Server Role In addition to the base Exchange requirements, the Mailbox server role requires the installation of a couple of hotfixes that address issues with Windows Server 2003 x64 if Windows Server 2003 Service Pack has not been installed: Hotfix available from Microsoft Knowledge Base Article KB904639 (http://support microsoft.com/kb/904639) Hotfix available from Microsoft Knowledge Base Article KB918980 (http://support microsoft.com/kb/918980) 81461.book Page 488 Wednesday, December 12, 2007 4:49 PM 488 Chapter 12 Planning the Exchange Server 2007 Server Role Deployment The Mailbox server role requires several Windows components from Internet Information Services to be installed (You might think the Mailbox role would not require these since the Client Access role has been removed from the mailbox functions.) Network COM+ access World Wide Web Service Requirements for the Unified Messaging Server Role To successfully install the Unified Messaging server role, the following components must be installed prior to running setup: Microsoft Exchange Speech Engine service (installed automatically if the setup is run from a command prompt) Microsoft Windows Media Encoder Microsoft Windows Media Audio Voice codec Microsoft Core XML Services (MSXML) 6.0 You cannot install the Unified Messaging role on a computer that has Microsoft Speech Server installed since at its core the Unified Messaging role relies on a customized version of Speech Server You must remove any version of Speech Server and is components installed on the server before attempting to install the Unified Messaging role Summary In this chapter you learned that the order of deployment and the configuration of the server roles must be planned properly to have a successful Exchange deployment Always remember the acronym C.E.H.M.U to determine the order in which to deploy the Exchange roles After discussing order, we covered the recommended hardware configurations for each of the server roles and for combined server roles We then covered the Active Directory and Exchange organization requirements, and finished up the chapter talking about the software requirements for each of the Exchange server roles Exam Essentials Know the recommended order for deploying Exchange roles Remember that the recommended order of deployment is Client Access, Edge Transport, Hub Transport, Mailbox, Unified Messaging (C.E.H.M.U.) When you are taking the test you may be asked to validate a plan or to build a plan for deploying the server roles; order will be important for such questions 81461.book Page 489 Wednesday, December 12, 2007 4:49 PM Exam Essentials 489 Know the required and recommended hardware configurations for each Exchange server role Most Exchange roles have specific hardware requirements for deployment Familiarize yourself with the hardware requirements Know the software requirements for each Exchange server role Each of the Exchange roles requires basic components to be installed, such as Windows PowerShell and Microsoft Management Console 3.0 Be aware of these requirements as well as the ones specific to each of the roles Also be aware of the software that cannot be installed on the same server, such as Internet Information Services (IIS) SMTP and NNTP on Hub Transport and Edge Transport servers Know Active Directory requirements Know the Active Directory functional-level requirements along with the operating-system requirements for domain controllers, global catalog servers, and Schema Master servers Be sure you know the rules about the number and placement of these roles as well Understand the Exchange organization requirements Exchange 2000 and higher servers are supported in the same organization as Exchange Server 2007 servers; however, specific patch levels must be attained on the legacy servers 81461.book Page 490 Wednesday, December 12, 2007 4:49 PM 490 Chapter 12 Planning the Exchange Server 2007 Server Role Deployment Review Questions What forest functional level must the forest be in before Exchange Server 2007 is installed where trusts will not be maintained with other forests? A Windows 2000 native B Windows 2000 mixed C Windows 2003 interim D Windows 2003 Which of the following Windows components cannot be installed on a Hub Transport server? (Choose all that apply.) A Internet Information Services (IIS) SMTP B Internet Information Services (IIS) NNTP C RPC/HTTP Proxy D ASP.NET 2.0 When planning a configuration for a Mailbox role for 5,000 heavy-profile users, what would be the minimum recommended amount of memory? A GB B 25 GB C 27 GB D 30 GB When deploying a new site, in which order would you deploy the following server roles? A Unified Messaging B Client Access C Mailbox D Hub Transport Why you need to deploy a Hub Transport server before deploying a Mailbox server? (Choose all that apply.) A Email will not be able to be scanned for viruses B No email will be able to be sent from the Exchange Mailbox server C No email will be able to be received from the Exchange Mailbox server D Users will not be able to access their email with Outlook Web Access Which of the following processor types are supported to run Exchange in production? (Choose all that apply.) A Intel Itanium B Intel Xeon with EM64T C AMD K6 D AMD Opteron with AMD64 81461.book Page 491 Wednesday, December 12, 2007 4:49 PM Review Questions 491 If you need to install an Exchange Server 2003 computer in an environment to support a specific application, when must you install it? A After all of the Exchange Server 2007 computers are deployed B After the Exchange Server 2007 schema has been applied C Before the Exchange Server 20007 schema has been applied D After the first Exchange Server 2007 server is installed Which of the following roles can be installed on a CCR cluster? A Hub Transport B Edge Transport C Client Access D None of the above Diskpart can be used for which two of the following tasks? A Sector-aligning new partitions B Compressing files C Expanding existing partitions D Sector-aligning existing partitions 10 When using Edge Transport servers, which of the following can to be done for the Edge Transport servers to have proper name resolution? (Choose all that apply.) A Add an MX record for the Hub Transport server B Add the names of the Hub Transport servers to the Edge Transport servers’ Host file C Add the names of the Hub Transport servers to the external DNS D Add the names of the Hub Transport servers to the Hub Transport servers’ Hosts file 11 If you have a mixed Exchange 5.5 with Service Pack and Exchange 2000 with Service Pack environment and you want to install Exchange Server 2007, what would you need to before installing the first Exchange 2007 computer? (Choose all that apply.) A Apply a hotfix to the Exchange 5.5 servers B Remove all of the Exchange 5.5 servers C Apply a hotfix to the Exchange 2000 servers D Remove all of the Exchange 2000 servers 12 Which of the following pieces of software cannot be installed on a server before Unified Messaging role is installed? A Internet Information Services (IIS) 6.0 World Wide Web Services B Microsoft Speech Server C Microsoft NET Framework 2.0 D Windows PowerShell 81461.book Page 492 Wednesday, December 12, 2007 4:49 PM 492 Chapter 12 Planning the Exchange Server 2007 Server Role Deployment 13 When you have a Mailbox server with 10 GB of RAM, what is the maximum number of storage groups that you can create on an Exchange Mailbox server running Exchange Server 2007 Enterprise edition? A B 14 C 20 D 25 14 Which of the following objects require disk space on an Edge Transport server? (Choose all that apply.) A Message queues B Message-tracking logs C Protocol logs D Agent logs 15 Which of the following need to be installed prior to installing the Exchange Edge Transport role? (Choose all that apply.) A Internet Information Services (IIS) SMTP B Active Directory Application Mode (ADAM) C Internet Information Services (IIS) BITS D Windows PowerShell 16 Which of the following roles can be installed on a Mailbox server using LCR? (Choose all that apply.) A Hub Transport B Edge Transport C Client Access D Unified Messaging 17 Which of the following Windows components cannot be installed on an Edge Transport server? (Choose all that apply.) A Internet Information Services (IIS) SMTP B Internet Information Services (IIS) NNTP C RPC/HTTP Proxy D ASP.NET 2.0 18 If you are planning on using a specific Client Access server for Outlook Anywhere, which of the following components would you need to install on the server before attempting an install? (Choose all that apply.) A Internet Information Service (IIS) 6.0 World Wide Web Service B RPC over HTTP Proxy C ASP.NET Version 2.0 D Microsoft Office Outlook 2007 ... servers thus will be retained in the transport dumpster 81 461 .book Page 417 Wednesday, December 12, 2007 4:49 PM Chapter 10 Planning a Backup and Recovery Solution for Exchange Server 2007 MICROSOFT. .. any Mailbox server in the Exchange organization and can be used to recover Exchange 2007, Exchange 2003 Service Pack or later, or Exchange 2003 Service Pack or later databases 81 461 .book Page... 444 Wednesday, December 12, 2007 4:49 PM 81 461 .book Page 445 Wednesday, December 12, 2007 4:49 PM Chapter 11 Planning the Exchange Server 2007 Storage Group Deployment MICROSOFT EXAM OBJECTIVE COVERED