Fixing Windows 8.1 access in UAG 2010 can cause Error 500

In my tweets or searching the Internet you might have learned that UAG 2010 SP3 will detect Windows 8.1 clients as mobile devices.
The not supported solution presented by Risual forgets to notify you that you need to make the change in both the InternalSite web.config as well as in the PortalHomePage web.config. This is documented in the official TechNet article on how to modify the DetectionExpression.
However, they both fail to tell you that the modifications you make in the web.config files might cause your UAG 2010 to start showing IIS Error 500.
The reason is obvious if your a programmer but maybe not if your a typical IT-pro.
When following the guide from Risual for example and adding the line <DetectionExpression Name="IE11" Expression='UserAgent Contains "mozilla" AND UserAgent Contains "rv:11"' DefaultValue="false" /> you have to remember to add that line BEFORE you refer to it in a line like <DetectionExpression Name="Mobile" Expression='!IE11 AND (MobileDevice OR WindowsCE)' DefaultValue="false" />

2 Replies to “Fixing Windows 8.1 access in UAG 2010 can cause Error 500”

  1. Aviv Hassidim

    Hi Kent !

    I have edit the web.config file in this path: C:Program FilesMicrosoft Forefront Unified Access GatewayvonInternalSite
    and I got this error : HTTP Error 500.19 – Internal Server Error.The requested page cannot be accessed because the related configuration data for the page is invalid.

    I have chacked that the line
    is BEFORE the line

    Is it working for someone?


    Aviv Hassidim

    • Kent Nordström Post author

      It’s working but you need to be very careful about small typos… Easy to make misstakes.


Leave a Reply

Your email address will not be published. Required fields are marked *