I ran into this issue several times now. After installing a new Forefront Threat Management Gateway (TMG) 2010 when the TMG Console is started the first time it fails with the following error:
An error has occurred in the script on this page.
Error: invalid argument
URL:file:///C:/Program%20Files/Microsoft%20/Forefront%20Threat%20 Management %20Gateway/UI_HTMLs/Generic.htm?guid=%7B43E06AFC-729B-8BC2-33A9E35BB12D%7D
Do you want to continue running scripts on this page?
This is a small bug in HTML interface code. To solve it, navigate to the C:\Program Files\Microsoft Forefront Threat Management Gateway\UI_HTMLs\TabsHandler\ directory and open the TabsHandler.htc file.
There are 3 lines containing “paddingTop” causing this issue. Find the lines and disable them by adding // at the beginning of the line.
Save the file and the console opens as expected.
In my previous post I discussed Exchange 2010 load balancing principles briefly (I need to leave some additional stuff for my MEC presentation) and how to setup a Kemp LoadMaster in a single-arm configuration. In this 2nd (and final) blog post I’ll show you how to configure Virtual Services for OWA 2010 and MAPI (Outlook clients).
Create a new Virtual Service for OWA
To create a new Virtual Service expand the Virtual Services and click Add New to open the wizard and fill in the necessary options like the IP Address of the new virtual service, the accompanying port number and give the service a nickname. In the Use Template option you can select a predefined template for the service. The advantage of using a template is of course that all options are filled in by Kemp, optimized specifically for the LoadMaster. Since we’re creating an OWA service select the Exchange HTTPS Offloaded template and click the Add this Virtual Service button.
In this example the Client Access Servers are configured with SSL offloading. The clients connect to the LoadMaster using SSL, the LoadMaster in turn connects just on port 80. For more information on how to configure SSL offloading in Exchange Server 2010 please check this blog post: http://www.jaapwesselius.com/2012/06/10/ssl-offloading-with-powershell/
Figure 1. Select a preconfigured template to use when creating a new Virtual Service.
Continue reading Load balancing Exchange 2010 (part II)
During TechEd 2010 in Berlin Ross Smith IV from Microsoft suddenly announced that Microsoft recommends using a hardware load balancer for Exchange Server 2010 instead of using Windows Network Load Balancing. You can check the presentation online on Channel9: http://channel9.msdn.com/Events/TechEd/Europe/2010/UNC311.
NLB has some known issues when it comes to Exchange Server 2010 like scalability issues, lack of service awareness, a full reconnect of all clients when adding or removing a new NLB member and only the option of Source IP for persistence.
Continue reading Load balancing Exchange 2010 (Part I)
One of the major changes in 2013 is the new architecture. Exchange 2013 only has two server roles:
- Client Access Server role;
- Mailbox Server role;
The other server roles that were available in Exchange 2007 and Exchange 2010 still exist, but are now known as Services. The Client Access Server (CAS15) consists of the Client Access Front-End (café) and the Front-End Transport (FET). The Mailbox Server role consists of the Mailbox Service, Unified Messaging Service, Client Access service (ambiguous naming I’m afraid) and the Hub Transport Services. The only exception is the Edge Transport Server role. When Exchange 2013 goes to RTM there won’t be an Edge Transport Server, this will be released with SP1 of Exchange 2013.
Continue reading Exchange 2013 Front-End Back-End
When migrating one Exchange organization to another organization you have to do quite some work. The traditional methods include a lot of scripting, or a 3rd party tool like Quest or BinaryTree to migrate one Exchange environment to another.
Migrationwiz is a product that can perform the migration from the cloud, they offer E-mail migrations as a service. This migration can be from any messaging platform to any messaging platform, but for this blog I’ll focus on a migration from one Exchange platform to another Exchange platform (in different datacenters).
Continue reading Migrationwiz – Exchange migration in the cloud