Exchange 2010 Transport Architecture Diagrams Available for Download

The Exchange 2010 transport server role architecture diagrams are now available for download. The Hub Transport Role Architecture diagram can help you understand the different transport components involved in processing and routing messages, the different transport agents that act upon messages and the events on which they are triggered, and visualize the mail flow.

The Hub Transport Extensibility diagram can help you understand how different transport agents process a message in the Exchange 2010 transport pipeline.

Both diagrams can be downloaded from Microsoft Exchange Server 2010 Transport Server Role Architecture Diagrams.

Note that Exchange 2010 includes internal or built-in transport agents which are not visible when you use the Get-TransportAgent or Get-TransportPipeline cmdlets. The list includes transport agents that implement Information Rights Management (IRM) functionality- the RMS Protocol Decryption agent, Journal Report Decryption agent, RMS Encryption agent, and Prelicensing agent, as well as the Journaling agent. To learn more about transport agents, see Understanding Transport Agents in Exchange 2010 documentation.

Exchange 2010 Database Availability Groups

I found a post at Henrik Walther Blog over at MSExchange.org that talk about DAG. http://blogs.msexchange.org/walther/2009/04/18/exchange-2010-database-availability-groups/

It is one of the most interesting new features in Exchange 2010. Here is a list of the new DAG functionality from the blog. 

  • The new Database Availability Group (DAG) HA/site resilience feature replaces CCR/SCR/LCR
  • Also note that SCC has been deprecated/cut with Exchange 2010
  • DAG built on the functionality we know from CCR and SCR, that is it still uses asynchronous log shipping and replay etc
  • An interesting thing about DAGs is that you’re no longer required to form a cluster before you install the MBX server role
  • The limited cluster features that are used by DAGs (primarily cluster heartbeat and quorum) are configured automatically when adding the first MBX server to the DAG and thereby more or less invisible to the administrator
  • With DAG you can have up to 16 copies of a Mailbox database
  • In addition, you can also have other Exchange 2010 server roles such as HT and CAS installed on the MBX server which is member of a DAG
  • Also, you can have DAG members located on different subnets and in separate AD sites

This image over at MSExchange.org describes very well the most important changes in the EMS for administrators regarding DAG.

How to Install Exchange Server 2010 Beta

This is a link to Scott Schnoll’s weblog where he goes through a step by step guide to install Exchange 2010 Beta. It is an interesting read and I followed his steps when installing the beta in my own lab environment. Click this link to visit the guide. I found a few gotchas in Brian Ricks’s blog

After installing it myself i have some gotchas and experience

  • The beta does not support coexistence with  older Exchange versions, not even Exchange 2007. So when i tried to install it in my lab environment the readiness check stopped me and I ended up creating a new domain for the Exchange beta
  • Got the  “The WinRM client cannot process the request”. This is because the wrong version of WinRM was installed. Download WinRM 2.0 CTP3 here

New Features in Exchange 2010

dd203064_exchange_logo_gifen-us2cmsdn_101

There is some new features in Exchange 2010 and the ones that I am most excited about is Database Availability Groups (DAG) and the new features in Outlook Web Access. Elan Shudnow have created a more comprehensive list of new features, check it out here

See Webcasts here http://msexchangeteam.com/archive/2009/05/26/451465.aspx