While working on a support case recently, i came across this issue wherein we were trying to publish an application and there was a warning message generated in the web monitor logs about "POST without Content-Type not Allowed" while accessing it from a client machine.
Microsoft announced the release of Update 2. It seems that Microsoft has finally admitted that there were few limitations in the product regarding 64bit clients and with update 2 they have tried to get them fixed. You may download the update 2 from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=9dcccebc-accb-4229-901a-792cc66791de which also describes the changes in update 2.
After a long wait finally someone is putting together something on UAG. A Microsoft employee named Ben Ari is writing a book on Microsoft Forefront UAG. It’s pretty interesting to me because I have worked with Ben Ari on few technical issues both inside and outside Microsoft.
Open the Microsoft Threat Management Console and right click on the Firewall Policy and select "Non-web Server Protocol Publishing Rule". A new server publishing rule wizard will appear. Give a name for the publishing rule and click next.
When you install an update for Microsoft Forefront UAG, it does not appear under the Windows control panel > Add/Remove programs. So, If you have to remove it for some reason then how do you remove an update? Well, UAG has an in-built script to remove the previously installed updates. The script is located at
Microsoft UAG 2010 can be integrated with Windows NAP (Network Access Protection) to make sure that the computers comply with the IT policies before user’s login into the UAG portal. Windows Network Access Protection is part of Windows 2008 and 2008 R2 servers. No extra hardware or licensing is required to implement Microsoft NAP in an environment.
A client that is trying to access an SSL enabled application on a backend server (e.g. Exchange) that is published through the Forefront UAG portal gets an error, specifically:
“An unknown error occurred while processing the certificate. Contact the site administrator”.
