Tag: TMG

FAQ: OWA directory redirection in TMG

We will perform the following steps if we want our users not to have to write the /owa directory in Exchange, if we are using Microsoft Forefront Threat Management Gateway (TMG) 2010. 1º Create the rule to allow OWA to https://correo.midominio.com/owa (HTTP://www.bujarra.com/?p=4862). 2º Copy & Paste that rule into the TMG. Rename it and give it a correct name. 3º Edit it, from your properties: – On the “Action” put 'Deny'’ and redirect http to 'https://correo.midominio.com/owa'. – On the “Paths” delete all paths and create one with the following settings: External path: <same as internal> Internal path: /

Migrating ISA Server 2006 to Microsoft TMG 2010

Those of us who need to upgrade or migrate our previous ISA environments to the new Microsoft product, called Forefront TMG we will need to perform a migration by import/export configuration, since Forefront TMG only works under 64bit systems or Windows 2008 SP2 or R2 and we will not be able to upgrade it from an earlier version of ISA Server, be ISA 2004 or ISA 2006 (since they run on x86). We will also have to manually export the certificates along with their private key to the TMG, since this process simply migrates the configuration.

Installing and configuring Microsoft Forefront TMG for secure OWA access

In this document, we'll look at one of the most common installations when deploying a Microsoft Exchange Server installation 2010 e ensure your connectivity from the outside through OWA access (or the necessary services) via a TMG host on the DMZ network. We will perform the installation of Microsoft Forefront TMG (Threat Management Gateway) An old ISA Server on a DMZ computer that will only be connected via HTTPS from the Internet, and the server will only connect to the Exchange server with the HUB role (or CAS array).