Mailbox Server
Mailbox Server holds the Mailbox database and Public folder databases for your organization. It only retains the mailbox and it won’t transfer your mails. Transferring mails between your mailbox servers are handled by Hub Transport servers. The mailbox server role will be introduced only after the installation of Hub Transport Server and Client Access Server Roles. 4 types of high availability options are introduced in Exchange Server 2007, if we are installing Mailbox Server with the High AvailabilityClustering options Like CCR, SCC, or SCR, then no other server roles to be installed with this server role.
LCR – will provide an option to achieve HA at the database level and not at the server level. LCR specifically designed for small business organization, Active Mailbox Databases can be replicated to the passive Mailbox Database on the same server, if the active database goes down, we can activate the passive copy to function as active and if the server goes down, Mailboxes won’t be accessible until the server got rebuild and the mailbox got restored.
CCR – will provide an option to achieve HA at the database level and the server level. CCR will replicate the Active Mailbox Server from one server to Passive Mailbox Database at another Server, Where in, if the active Server goes down, automatic failover will occur and the passive server will function as active.
SCC – will provide HA at the server level only. if the active server goes down, the passive server will begging to function as active by referring the active copy which is accessible for all the servers in SCC. We can have centralized location to place the Mailbox and public folder database and the active server point to the same location. It’s like Clustering option available in Exchange Server 2003. If the SAN goes down, mailbox won’t be accessible.
SCR – will provide HA option at the Site level failure. With SCR there is no need to implement windows failover clustering feature installed to replicate the active database to passive database. Like active and passive mailbox database copy in other HA option, we have Source Database and Target Database in SCR.
Client Access Server
The role that handles client requests for OWA, Outlook Anywhere, ActiveSync, OVA and offline address book distribution. MAPI request from outlook client are directly connected to mailbox database, even though the MAPI clients are directly connected to Mailbox Database to access the mailboxes, MAPI client still depends on client Access Server for Auto Discover and Availability Service. CAS is responsible for any connection to Mailbox Server, when you want the Mailbox Server from outside the Exchange organization CAS is responsible. It’s also responsible for Non MAPI Clients connection.
This role must be installed after the hub transport role and before the mailbox server role. You can install the mailbox server role at the same time as the client access role, but not before.
Hub Transport Server
The Main Purpose of the Hub Transport Server Role is to transfer the mails throughout your exchange environment, this server role is responsible for internal mail flow, it replaces the bridge head servers in Exchange server 2003. This can be used as an edge transport server in Smaller Organization by installing and anti spam agents in Hub Transport Server itself. This must be the first role installed in Exchange 2007. You can install the client access server role and the mailbox server role at the same time as the hub transport role, but not before.
We have two connectors to look at in Hub Transport Server.
Send Connector – Responsible to outbound mail flow, by default, there is no Send Connector created (which means mail flow will not happen externally) to route external mails, we have to create a send connecter based on our requirement.
Receive Connector – Receive connector is responsible to receive inbound emails. By default the external mails are not received internally until the anonymous authentication is enabled
Unified Messaging Server
Functions as the interface point for the VOIP gateway or IP-PBX phone system. Allows user mailbox to be the single point of storage and access for voice mail and fax messages, in addition to their normal email.
Edge Transport Server
The Edge Transport Server Role is to transfer mails from inside of your organization to the outside world. It should be implemented at the edge of the network (perimeter Network). Main purpose is to prevent your exchange server from all kinds of Attack. Must have ports 25 (SMTP) and 50636 (LDAPS) open from it to the hub transport server on the internal LAN. Port 25 is to send mail in. Port 50636 is to replicate the Exchange information that it needs, such as changes to users’ safe and blocked senders lists.
Edge Synchronization –Since the Edge Transport Server is sitting at the edge of the network and to have to communication between the Hub Transport Server, we are having edge synchronization. It is the process to update the ADAM in the Edge Transport Server
Address Rewriting – Its additional feature which is used to rename the email address from internal users. This option will provide an uniformity in the SMTP address if we are having lot of domains and if company wish to have the external SMTP
Mailbox Server holds the Mailbox database and Public folder databases for your organization. It only retains the mailbox and it won’t transfer your mails. Transferring mails between your mailbox servers are handled by Hub Transport servers. The mailbox server role will be introduced only after the installation of Hub Transport Server and Client Access Server Roles. 4 types of high availability options are introduced in Exchange Server 2007, if we are installing Mailbox Server with the High AvailabilityClustering options Like CCR, SCC, or SCR, then no other server roles to be installed with this server role.
LCR – will provide an option to achieve HA at the database level and not at the server level. LCR specifically designed for small business organization, Active Mailbox Databases can be replicated to the passive Mailbox Database on the same server, if the active database goes down, we can activate the passive copy to function as active and if the server goes down, Mailboxes won’t be accessible until the server got rebuild and the mailbox got restored.
CCR – will provide an option to achieve HA at the database level and the server level. CCR will replicate the Active Mailbox Server from one server to Passive Mailbox Database at another Server, Where in, if the active Server goes down, automatic failover will occur and the passive server will function as active.
SCC – will provide HA at the server level only. if the active server goes down, the passive server will begging to function as active by referring the active copy which is accessible for all the servers in SCC. We can have centralized location to place the Mailbox and public folder database and the active server point to the same location. It’s like Clustering option available in Exchange Server 2003. If the SAN goes down, mailbox won’t be accessible.
SCR – will provide HA option at the Site level failure. With SCR there is no need to implement windows failover clustering feature installed to replicate the active database to passive database. Like active and passive mailbox database copy in other HA option, we have Source Database and Target Database in SCR.
Client Access Server
The role that handles client requests for OWA, Outlook Anywhere, ActiveSync, OVA and offline address book distribution. MAPI request from outlook client are directly connected to mailbox database, even though the MAPI clients are directly connected to Mailbox Database to access the mailboxes, MAPI client still depends on client Access Server for Auto Discover and Availability Service. CAS is responsible for any connection to Mailbox Server, when you want the Mailbox Server from outside the Exchange organization CAS is responsible. It’s also responsible for Non MAPI Clients connection.
This role must be installed after the hub transport role and before the mailbox server role. You can install the mailbox server role at the same time as the client access role, but not before.
Hub Transport Server
The Main Purpose of the Hub Transport Server Role is to transfer the mails throughout your exchange environment, this server role is responsible for internal mail flow, it replaces the bridge head servers in Exchange server 2003. This can be used as an edge transport server in Smaller Organization by installing and anti spam agents in Hub Transport Server itself. This must be the first role installed in Exchange 2007. You can install the client access server role and the mailbox server role at the same time as the hub transport role, but not before.
We have two connectors to look at in Hub Transport Server.
Send Connector – Responsible to outbound mail flow, by default, there is no Send Connector created (which means mail flow will not happen externally) to route external mails, we have to create a send connecter based on our requirement.
Receive Connector – Receive connector is responsible to receive inbound emails. By default the external mails are not received internally until the anonymous authentication is enabled
Unified Messaging Server
Functions as the interface point for the VOIP gateway or IP-PBX phone system. Allows user mailbox to be the single point of storage and access for voice mail and fax messages, in addition to their normal email.
Edge Transport Server
The Edge Transport Server Role is to transfer mails from inside of your organization to the outside world. It should be implemented at the edge of the network (perimeter Network). Main purpose is to prevent your exchange server from all kinds of Attack. Must have ports 25 (SMTP) and 50636 (LDAPS) open from it to the hub transport server on the internal LAN. Port 25 is to send mail in. Port 50636 is to replicate the Exchange information that it needs, such as changes to users’ safe and blocked senders lists.
Edge Synchronization –Since the Edge Transport Server is sitting at the edge of the network and to have to communication between the Hub Transport Server, we are having edge synchronization. It is the process to update the ADAM in the Edge Transport Server
Address Rewriting – Its additional feature which is used to rename the email address from internal users. This option will provide an uniformity in the SMTP address if we are having lot of domains and if company wish to have the external SMTP
No comments:
Post a Comment