First I would like to start this post by emphasizing a recently article that was published at Tales from the Edge, that explains how to configure Exchange Sync with Forefront TMG 2010, here it is the link for it: http://technet.microsoft.com/en-us/library/ee513174.aspx. Also I want to remind you about the supported scenarios with Forefront TMG 2010 and Exchange 2007 Edge role, mainly the support matrix below:
The * on this table says:
Recently a blog post was published by the Exchange team saying that they reconsidered and are planning to support Windows Server 2008 (SP2). To read more about it please follow this link: http://msexchangeteam.com/archive/2009/11/04/453026.aspx
There is a newer update on that, which is the one below:
“…we will be adding support for Exchange 2007 on the Windows Server 2008 R2 platform. While we had hoped to add this application/operating system combination quickly, unfortunately adding this support requires code changes to setup in Exchange 2007. Therefore, our vehicle for adding this support will be via a third Service Pack for Exchange 2007 in the second half of calendar year 2010.”
In other words: If you want to deploy Exchange 2007 Edge role on Forefront TMG 2010 you will need to:
If you already installed Forefront TMG 2010 on Windows Server 2008 R2 and want to install Exchange Edge role to enable EMail Protection feature your current supported options are:
Sr Security Support Escalation Engineer
Microsoft CSS Forefront Edge Team
Microsoft Forefront Edge Test Team
is this a typo?
"•Wait for Exchange 2007 SP3 to come out so you can install Exchange 2003 Edge Role on Windows Server 2008 R2"
What is the Exchange Server 2003 Edge role?
I know only the Exchange Server 2003 FrontEnd and BackEnd Server role
regards Marc Grote
Yes Marc, it was a typo. :)
Thanks for catching that, it's fixed now.
I tried TMG 2010 with Exchange 2010 edge. without SP. the TMG service was stop working and failed during boot and blocked domain was fill of external domain names and i had to diable this filter. is there any fix or update about this issue in SP1?