文件名称：配置客户端访问服务共存-Exchange2010规划和部署
文件大小：4.86MB
文件格式：PPT
更新时间：2024-05-12 13:23:57
Exchange2010
配置客户端访问服务共存 配置DNS Best Practice: “Split DNS” 为服务器申请相应的证书 安装Exchange 2010客户端访问服务器 将Exchange 2003服务器移出 RPC over HTTP 拓扑 测试所有的客户端访问情景 Purpose: Introduce Overview of Transition Server Roles Time: 3 min Key Points: For clients other than Microsoft Office Outlook® to connect to the user mailboxes and use the single sign-on feature, the clients must be configured to use the Exchange Server 2010 Client Access server as the first point of connection. The Client Access server may then redirect the client to an Exchange Server 2003 front-end server, or it may proxy the client request to an Exchange Server 2003 front-end server. Because you can redirect client requests from the Exchange Server 2010 Client Access server to an Exchange Server 2003 server, you will need to enable Internet access for multiple URLs. Stress the importance of using server certificates that support all of the URLs. Because all clients are connecting to an Exchange Server 2010 Client Access server when the user mailboxes are moved to Exchange Server 2010, you must plan for Client Access server capacity. In previous versions of Exchange Server, the recommended deployment ratio was one Client Access server processor core for every four Mailbox server processor cores. In Exchange Server 2010, the recommended ratio is 3 to 4. If you are transitioning from an Exchange Server 2003 or Exchange Server 2007 organization to Exchange Server 2010 , the first server role you must transition is the Client Access server role. IMPORTANT: When transitioning an Exchange Server 2003 organization, an Exchange Server 2003 front-end server is required to support the transition. For each Exchange Server 2010 Client Access server, you can only configure one Outlook Web Access 2003 Uniform Resource Locator (URL) for redirection. You can accomplish this with a single Exchange Server 2003 front-end server or a load balanced array of Exchange Server 2003 front-end servers. 1. Install Exchange Server 2010 (Beta) Client Access server. 2. Enter the primary external namespace for your virtual directories. 3. Create new Client Access server certificates and deploy to both legacy and Exchange Server 2010 (Beta) Client Access servers if new certificates are needed. Subject Alternate Name (SAN) certificates or existing public certificates currently installed can be imported to the new Client Access server role on the Exchange Server 2010 (Beta) computer. 4. Configure Exchange Server 2010 (Beta) Client Access server to mirror legacy configuration. 5. Configure Client Access server on the Exchange Server 2010 (Beta) computer to have proper externalURLs and Exchange2003URL parameters 5. Create Legacy Fully Qualified Domain Name (FQDN) in Domain Name System (DNS). 6. Create legacy URL rules in reverse proxy (if applicable). 7. Schedule internet protocol client downtime. 8. Change externalURLs on the Exchange Server 2007 Client Access server. Reconfigure the ExternalURLs on the virtual directories on your Exchange Server 2007 Client Access servers to point to the legacy hostname. Set the ExternalURL property on the Exchange Server 2010 (Beta) Client Access servers' virtual directories to your original hostname. If your Client Access server is Internet-facing, set the ExternalURL property on the Outlook Web Access virtual directories by using the Exchange Management Console or the Exchange Management Shell. (You do not need to set externalURLs on non internet facing CAS servers.) For redirection ExternalURL settings for an Internet-facing Client Access server in the usa.contoso.com site, the externalURL setting is https://www.usa.contoso.com/OWA. Reconfigure external DNS and/or reverse proxy by reconfiguring autodiscover and mail.contoso.com namespace to point to Exchange Server 2010 (Beta) servers. *