unified GAL, or as a resource forest topology with an Exchange forest and one or more user account forests (see ). In these cases, Microsoft recommends contacting Microsoft Consulting Services or a certified Microsoft partner to consult on the design. Record the number of Exchange Server instances in A-3 in Appendix A. The remaining tasks and steps in the guide should be repeated for each instance of Exchange Server identified in this task. Task 2: Determine the Active Directory Host Forest, Site, and Domain In this task, determine which Active Directory forest, site, and domain will be used to host this instance of Exchange Server 2010. Exchange Server has no specific requirements relative to forest, site, or domain locations. This decision will inform subsequent decisions relative to domain controller placement. Record this in Table A-4 in Appendix A. Step Summary In this step, the number of messaging server instances was determined, on the business requirements identified in Step 1. Also, the Active Directory domains that will host the messaging system were determined. The information gathered in this step was recorded in Tables A-3 and A-4 in Appendix A and will be used in subsequent steps to design the remaining server infrastructure. Additional Reading Planning Active Directory (Exchange Server 2010 SP1): FIM 2010 Technical Overview: Infrastructure Planning and Design for Active Directory Domain Services: Deploy Multiple Forest Topologies: Step 3: Design the Mailbox Server Infrastructure In the previous step, the number of messaging server instances was determined based on the business requirements identified in Step 1. Also, the Active Directory forest, site, and domains that will host this instance of Exchange Server 2010 were determined. In this step, the Mailbox server role instances are designed. Mailbox servers store all Exchange mailboxes, which hold email messages, calendar items, contacts, and so on. The tasks to be performed in this step are: Determine role placement. Plan for capacity. Plan for performance. Plan for fault tolerance.
unified GAL, or as a resource forest topology with an Exchange forest and one or more user account forests (see ). In these cases, Microsoft recommends contacting Microsoft Consulting Services or a certified Microsoft partner to consult on the design. Record the number of Exchange Server instances in A-3 in Appendix A. The remaining tasks and steps in the guide should be repeated for each instance of Exchange Server identified in this task. Task 2: Determine the Active Directory Host Forest, Site, and Domain In this task, determine which Active Directory forest, site, and domain will be used to host this instance of Exchange Server 2010. Exchange Server has no specific requirements relative to forest, site, or domain locations. This decision will inform subsequent decisions relative to domain controller placement. Record this in Table A-4 in Appendix A. Step Summary In this step, the number of messaging server instances was determined, on the business requirements identified in Step 1. Also, the Active Directory domains that will host the messaging system were determined. The information gathered in this step was recorded in Tables A-3 and A-4 in Appendix A and will be used in subsequent steps to design the remaining server infrastructure. Additional Reading Planning Active Directory (Exchange Server 2010 SP1): FIM 2010 Technical Overview: Infrastructure Planning and Design for Active Directory Domain Services: Deploy Multiple Forest Topologies: Step 3: Design the Mailbox Server Infrastructure In the previous step, the number of messaging server instances was determined based on the business requirements identified in Step 1. Also, the Active Directory forest, site, and domains that will host this instance of Exchange Server 2010 were determined. In this step, the Mailbox server role instances are designed. Mailbox servers store all Exchange mailboxes, which hold email messages, calendar items, contacts, and so on. The tasks to be performed in this step are: Determine role placement. Plan for capacity. Plan for performance. Plan for fault tolerance.
ipd-exchange-server-2010-version-1-1.docx