部署和配置微软Exchange 2007服务器角色.ppt

* Slide Objective: To highlight key aspects of deploying the Client Access server role in Exchange Server 2007. Instructor Notes: Let’s turn our attention now to deploying the Client Access server role. Given that the Client Access server role supports client application such as OWA and EAS, protocols including POP3 and IMAP4, and AutoDiscover and Web services, there are key deployment considerations as highlighted on this slide. * * * Slide Objective: To review some key points in deploying the Client Access server role for Exchange Server 2007. Instructor Notes: There are more considerations for deploying the Client Access server role including: There is more load on the Client Access server than on the Mailbox server. Exchange Server 200x Back End servers in an existing Exchange organization should be transitioned to Exchange Server 2007 before the Back End servers are transitioned. When a completely new Exchange organization for Exchange Server 2007 is created, existing Exchange Server 200x Back End servers should be migrated before the Back End servers are migrated. Client Access servers should not be deployed in the Perimeter Network (known by military oriented organizations as the “DMZ”). * * * Slide Objective: To describe the post installation activities of deploying of the Client Access server role. Instructor Notes: After you install the Client Access server role on Exchange Server 2007, perform the following activities: Verify your Exchange 2007 installation. You should review the setup logs, verify the folder structure of Exchange files, verify the tools installed, and check that the required Exchange services are started. For more information about verifying your installation. Secure the Client Access server by using the Security Configuration Wizard (SCW). Use it to minimize the attack surface by disabling Windows functionality that is not required for the server roles. There is an SCW template for each of the server roles. By u