Description of the Rollup 1 hotfix package for Unified Access Gateway 2010 Update 1

This article has been archived. It is offered "as is" and will no longer be updated.
Microsoft has released the Rollup 1 hotfix package for Microsoft Forefront Unified Access Gateway (UAG) 2010 Update 1. This article contains the following information about the rollup package:
  • Issues that this update fixes
  • How to obtain this update
  • Prerequisites for installing this update
ProductUpdate nameBuild
Unified Access Gateway 2010UAG-KB981932-V4.0.1152.110-ENU.msp1152.110

Note This update can be applied to the UAG server that is running UAG 2010 Update 1. For more information about UAG 2010 Update 1, visit the following Microsoft Web site:

Issues that are fixed in this update

This update fixes the following issues that were not previously documented in a Microsoft Knowledge Base article.

Issue 1

When you click the Admin->FileAccess user interface in the Forefront Threat Management Gateway console, you receive the following message:
To configure the File Access application, and to enable end-users to access internal resources, NETBIOS traffic to the Forefront UAG server must be enabled on the Forefront TMG server. Do you want to enable it now?
Then, the following ports are opened when you click OK:
  • NetBios Name Service (UDP 137)
  • NetBios Datagram (UDP 138)
Note When you click OK, the two ports are opened. However, it can take some time for Forefront Threat Management Gateway (TMG) server to synchronize with the new rule. Therefore, you may receive the "Unable to enumerate domains" error message even after you click OK. This behavior may occur until TMG is synchronized.

To check TMG synchronization, locate Monitoring node and then click Configuration node and make sure that there is green check box for the TMG servers. When TMG is synchronized, you may have to reopen the FileAccess management window.

Issue 2

You access the contacts page of Microsoft Dynamics CRM 4 through UAG 2010. However, you see a page that contains a middle IFRAME tag and shows the following error message:
You have attempted to access a restricted URL
This error occurs because the client requests the “<signature>/MicrosoftCMR/activities/email/null” URL. The default RuleSet does not support this behavior. Setting the application to evaluate but do not enforce lets the client access this URL. However, a 404 error message is returned if the URL does not exist on the server.

Issue 3

You run the Add Application Wizard in the Forefront UAG Management console to configure Microsoft Exchange Server 2003 Outlook Web Access (OWA), which has the RPC over HTTP feature enabled. However, you cannot complete the Add Application Wizard that defines the Exchange service.

When you configure the Exchange 2003 OWA feature, the ActiveSync feature, or the RPC over HTTP feature, you receive the following message for the public hostnames of the mail server and for the public hostnames for the Autodiscover name:
The Autodiscover service does the following: Automatically configures user profile settings for clients running Microsoft Office Outlook 2007 or Outlook 2010, as well as supported mobile phones. Phones running Windows Mobile 6.1 or a later version are supported. If your phone isn't a Windows Mobile phone, check your mobile phone documentation to see if it's supported.
The logic behind the template recognizes that the Autodiscover feature is not an available option in Exchange Server 2003. Additionally, you cannot disable only the Autodiscover component in the Add Application Wizard.

Note Exchange 2003 does not support the Autodiscover feature. For more information about the Autodiscover feature, visit the following Microsoft TechNet Web site: Understanding the Autodiscover service

Issue 4

You access a UAG 2010 server by using the Mozilla Firefox browser on a Windows operating system. However, endpoint detection fails when one or more custom detection scripts are defined by the UAG administrator.

Note You cannot run UAG 2010 endpoint components on this computer because the script signature cannot be verified. The user experience may vary when different users access an organization's site. These variations depend on the security policies of the organization.

Update information

An update is now available from Microsoft. However, the update is intended to correct only the issues that this article describes. Apply the update only to systems that are experiencing these specific issues.

To resolve these issues, contact Microsoft Customer Support Services to obtain the update. For a complete list of Microsoft Customer Support Services telephone numbers and for information about support costs, visit the following Microsoft Support Web site:Note In special cases, the charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.


To install this rollup package, you must have UAG 2010 Update 1 installed.

Restart requirement

You do not have to restart the computer after you apply this rollup package. You should activate UAG after you install the rollup package.

Removal information

To remove this update, use one of the following methods:
  • Log on as a built-in administrator, and then uninstall the update by using the Programs and Features item in Control Panel.
  • At a command prompt, type the following command, and then press ENTER:
    msiexec.exe /uninstall {258D2A6E-0E39-47AC-B690-87FB20275336} /package {9B0CE58E-C122-4CB4-80C1-514D4162C07C}
    Note The command line should be elevated for the second uninstall method. Uninstalling Unified Access Gateway 2010 Update 1 automatically uninstalls the Rollup 1 hotfix package for Unified Access Gateway 2010 Update 1.

Hotfix replacement information

This hotfix does not replace any other hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
File nameFile versionDateTimeFile size
Agent_win_helper.jarNot applicable21-April-20105:411,286,015
WhlFiltSecureRemote_HTTP.xmlNot applicable21-April-20105:4077,404
WhlFiltSecureRemote_HTTPS.xmlNot applicable21-April-20105:4079,540
WhlInstallAndDetect.incNot applicable21-April-20105:414,476
Detection.jsNot applicable21-April-20109:0314,591
WizardDefaultParam.iniNot applicable21-April-20105:4055,274
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Article ID: 981932 - Last Review: 12/12/2015 04:00:12 - Revision: 2.0

Microsoft Forefront Unified Access Gateway 2010

  • kbnosurvey kbarchive atdownload kbsurveynew kbhotfixrollup kbfix kbexpertiseinter kbqfe KB981932