We discuss the Edge Transport role further in Chapter 9 . The Hub Transport server role uses Send
Connectors and Receive Connectors for email routing and delivery.
This chapter covers:
??‘ Understanding the core transport architecture implemented by the Hub Transport and
Edge Transport servers.
??‘ Using and configuring the Hub Transport server
??‘ Configuring various types of connectors in Exchange Server 2007
??‘ Using email address policies and accepted domains
Part II: Working with Server Roles
192
The Transport Server Architecture
The core transport architecture was rewritten in Exchange Server 2007 and is very different from
previous versions of Exchange. Those familiar with Exchange Server 2000/2003 might quickly notice
that transport is no longer dependent on Internet Information Server (IIS). In fact, it is required that you
uninstall the SMTP and NNTP services prior to installing Exchange Server 2007 unlike Exchange Server
2000/2003, which required both services to be installed. Additionally, all core components required for
message categorization, routing, and delivery are included in Exchange Transport Service with no
components dependent on IIS. This section briefly reviews the core transport architecture from the
perspective of the Management Shell.
The following Hub Transport ??“ related cmdlets are discussed:
??‘ Get-Queue
??‘ Set-Queue
??‘ Suspend-Queue
??‘ Resume-Queue
??‘ Retry-Queue
??‘ Get-TransportPipeline
??‘ Get-TransportServer
??‘ Set-TransportServer
??‘ Get-TransportConfig
??‘ Set-TransportConfig
??‘ Get-NetworkConnectionInfo
A number of components make up the core transport architecture implemented by both the Hub
Transport server and Edge Transport server roles.
Pages:
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293