Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 575
  • Last Modified:

Exchange 2013 Server Roles

If I understand Exchange 2013 has removed the HUB server role.
Now I am not sure if the functionality of the HUB server is included in Mailbox server or in CAS server.

I mean when an email goes out or comes in to the Mailbox server what path it will take.

in Exchange 2010, all emails going out and coming in go through HUB server.
 CAS server is used just to connect throughout it to read email.

Any explanation will be very much appreciated.

Thank you
0
jskfan
Asked:
jskfan
4 Solutions
 
Krishna PatilCommented:
Services of hub transport are splitted into CAS and MBX

1. FrontEnd Transport service - This service runs on all Client Access servers and acts as a stateless proxy
2.Transport service - This service runs on all Mailbox servers and is virtually identical to the Hub Transport server role in previous versions of Exchange
3.Mailbox Transport - This service runs on all Mailbox servers and consists of two separate services:

a. Mailbox Transport Submission service .
b. Mailbox Transport Delivery service.
0
 
AishIT ManagerCommented:
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
jskfanAuthor Commented:
If I understand CAS Front End gets involved only if emails are sent to the outside organization or received from outside organization.

I would like to have an Exchange 2013 Expert puts a  Correct diagram like this(This Diagram Can be wrong:)

External Email to Internal :

CAS -->Transport Service-->Mailbox Transport Service-->Mailbox Transport Delivery-->user mailbox

Internal Email to External:
user mailbox-->Mailbox Transport Submission-->Mailbox Transport Service-->Transport Service-->CAS

Internal email to internal(form User1 to User2):
user1 mailbox--Mailbox Transport Submission--Mailbox Transport Service-->Transport Service-->Mailbox Transport Delivery--Mailbox Transport Service---Mailbox Transport Submission-->User2 mailbox


 A Digram like that might Help….



Thank you
0
 
NenadicCommented:
jskfan,


Microsoft Exchange Server 2013 Architecture covers the details of message flow in 2013. It also describes the differences to previous versions.
http://blogs.technet.com/b/exchange/archive/2013/01/23/exchange-2013-server-role-architecture.aspx

Kind regards,
0
 
jskfanAuthor Commented:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/planning-architecture/exchange-2013-mail-flow-part1.html


I checked the link above that has more details about the mail flow, however I noticed that either when you send or receive emails they all go through submission and delivery queues…something I was not sure about
0
 
jskfanAuthor Commented:
and it is not clear about the Pickup Directory and replay Directory, which component will put the email in either or both the mentioned directories?

Also on the diagram I see SMTP Send and SMTP Receive , Are they Send / Receive Connectors ?
0
 
NenadicCommented:
jskfan,

Would this help perhaps?
http://technet.microsoft.com/en-us/library/bb124230(v=exchg.150).aspx

SMTP Send is used by Send Connectors, but is also used by the transport service for internal mail flow (within a Site and between Sites)
The same is true for SMTP Receive.
They are both components of the Transport service and are in certain cases exposed as configurable Send and Receive Connectors.

Regards,
Nenadic
0
 
jskfanAuthor Commented:
Thank you
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Tackle projects and never again get stuck behind a technical roadblock.
Join Now