E2K7 10 Architecture for Interoperability.ppt

Slide Objective: This slide shows a sample architecture for medium sized organisations. Instructor Notes: For smaller sites all roles can be co-located for a single server deployment. As multiple servers are required this is one option for architecture. Mailbox Servers, Hub Transport Client Access Server Roles – Can be co-located, but only the Mailbox Server Role can be installed on a cluster. The mailbox servers can use LCR in this configuration for redundancy, but not CCR or SCC because they are co-located with Hub Transport CAS roles which are not compatible with clustering (TBC) Transport servers provide automatic redundancy within the same site. The Hub Transport Server Role which is co-located on the same server as the Mailbox Server Role will be preferred for that Mailbox Server Role, but if a failover were to occur then the other HT in the site will be utilized. The CAS role will also be preferred for the Mailbox Server Role where it is co-located. For external publishing in this scenario, ISA 2006 with ISA load balancing should be used to provide a single namespace and redundancy between the CAS servers, while maintaining affinity for Push notifications. Edge Servers - are optional, but recommended for mail cleansing (anti-virus, anti-spam, compliance policy application, etc) in the DMZ. The Edge servers can be deployed at any stage, as they don’t require Exchange 2007. Edge cannot be co-located. Is optional independent. Information about scaling mid sized organisations, etc... Exchange 2003 Front-End servers will be replaced by Exchange 2007 Client Access Servers in functionality. Clients will experience the level of functionality determined by their backend server. More details to come. * Slide Objective: This slide does a quick drill down into transitioning from Linkstate Instructor Notes; Routing changes recap By now you’re aware of the basics of E2K7 routing: ? No more routing groups (except for legacy purposes) ?