Archive for the ‘TMG 2010’ Category

Problems authenticating to ActiveSync? Don’t be an Admin then!

July 16, 2011 Leave a comment


Recently had the following error when testing ActiveSync (via after the IT manager said their Android device wouldn’t work Sad smile )


A HTTP 403 forbidden response was recieved. The response appears to have come from IIS7


I did a bit of digging and found out something I did not know – if you are a member of any BUILTIN Administrative group in Active Directory then you cannot utilised ActiveSync!! (This is due to the “Inherit permissions” removing as you are a member of a “Protected Group” from what I could gather).


Oh well, time to remind people that they should not be using Domain Administrative accounts for day-to-day access!!! Winking smile


Errors running testexchangeconnectivity on Autodiscover

July 16, 2011 Leave a comment


If you get the following error;




Ensure that the “” public name is added to the TMG rule that has the /Autodiscover/ Path – IT DOESNT GET ADDED BY DEFAULT! ;



Customising the Login page for TMG Outlook Web Application 2010

July 16, 2011 2 comments

To customise the Login page (say, removing the “DOMAIN\” part of the username prompt) edit the “strings.txt” found in ;


C:\Program Files\Microsoft Forefront Threat Management Gateway\Templates\CookieAuthTemplates\Exchange\HTML


Look for the string;


L_UserName_Text="User name:"


And change it to be what’s required (the above has the DOMAIN\ already removed).


Any of these strings can be changed.


To force changes to take effect, restart the TMG Firewall Service Smile


Happy TMG’ing Winking smile

TMG, UAG, DirectAccess, Unicast NLB and VMware… phew!

April 18, 2011 2 comments


A Customer of mine utilise ESX 4.1 to host their UAG and DirectAccess solution.


VMware KB article 1006778 ( dictates that for a Unicast NLB to function within VMware, the following statements must be true;

  • Need two machines running Windows Server 2003 or later
  • Each machine needs to have at least one network card and at least one fixed IP address
  • Two adapters in each machine is recommended for best performance
  • One adaptor mapped to the real IP Address (Microsoft calls this the Dedicated IP) and one mapped to the ‘virtual’ IP Address (Microsoft calls this the Cluster IP)
  • One benefit of unicast mode is that it works out of the box with all routers and switches (since each network card only has one MAC address)
  • In unicast mode, since all hosts in the cluster all have the same MAC and IP address, they do not have the ability to communicate with each other via their NLB network card
  • A second network card is required for communication between the servers

As UAG Direct Access requires an internal and external NLB there are, by default, no none-NLB interfaces. This is contrary to the requirements set by VMware, so we must define a tertiary NIC just for NLB and TMG array communication.

This has been applied as per the following diagram;


Each UAG server has had the tertiary NIC defined as can be seen above. These are configured with a private IP range.

This should be enough to make Unicast NLB work Smile If not, drop me a line as I have some further steps I put in (that I don’t think are required)


UPDATE: After speaking with Microsoft on something entirely different it has come to light that the above solution, although workable, is fully NOT SUPPORTED by Microsoft. In short the only supported solution for Microsoft is to have both UAG servers on the same VMware host (in which scenario you don’t require the Intra-Array link). Note that this is also the case currently for Multicast scenarios (which supposedly is supported generally and still waiting for a Technet update)

Categories: Microsoft, TMG 2010, UAG 2010


January 11, 2010 Leave a comment

Handy collection of ISA tools (2000-TMG), including a WPAD test script and a TMG Conficker-Block script…

Categories: ISA, TMG 2010, UAG 2010