Rollup 2 for Forefront Unified Access Gateway 2010 Service Pack 4 is available for download


downloadWe have recently released Rollup 2 for Forefront UAG 2010 Service Pack 4

UAG 2010 Service Pack 4 Rollup 2 is available as a hotfix download from Microsoft Support as an update to UAG 2010 Service Pack 4.

This update contains 4 new changes for UAG 2010 Service Pack 4. For details, please visit KB 3060650: Description of Rollup 2 for Forefront Unified Access Gateway 2010 Service Pack 4

Please download the Forefront Unified Access Gateway (UAG) 2010 Service Pack 4 Rollup package and learn more about UAG 2010 SP4 by visiting our TechNet Library.

 

Thank you,

The Forefront UAG Product Team

 

Get the latest System Center news on Facebook and Twitter:

The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/ 
The Forefront TMG blog: http://blogs.technet.com/b/isablog/ 
The Application Proxy blog: http://blogs.technet.com/b/applicationproxyblog/
The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ 

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

Comments (23)

  1. Will there be support for Windows 10 clients? Please share any modifications necessary to allow UAG to work with Windows 10. Thanks.

  2. Anonymous says:

    208 Microsoft Team blogs searched, 42 blogs have new articles. 120 new articles found searching from

  3. Bill Smith says:

    I am also very interested in if there will be any way to use Windows 10 Clients with UAG

  4. Andy says:

    I would also like to know if there is a way to make UAG work with Windows 10 as this will be essential

  5. Kevin Vancraybex says:

    This workaround will make IE 11 in Windows 10 function with UAG:

    – open web.config in Program FilesMicrosoft Forefront Unified Access GatewayvonInternalSite
    – add following lines of code:

    – save web.config and copy it to all array members

  6. Kevin Vancraybex says:

    <DetectionExpression Name="Windows10" Expression=’UserAgent Contains "windows nt 10.0"’ DefaultValue="false" />
    <DetectionExpression Name="WindowsNewerThan2000" Expression=’UserAgent Contains "windows nt 5.1" OR UserAgent Contains "windows nt 5.2" OR Vista OR Windows7 OR Windows8 OR Windows8_1 OR Windows10′ DefaultValue="false" /%gt

    < = <
    > = >

  7. Kevin Vancraybex says:

    <DetectionExpression Name="Windows10" Expression=’UserAgent Contains "windows nt 10.0"’ DefaultValue="false" />
    <DetectionExpression Name="WindowsNewerThan2000" Expression=’UserAgent Contains "windows nt 5.1" OR UserAgent Contains "windows nt 5.2" OR Vista OR Windows7 OR Windows8 OR Windows8_1 OR Windows10′ DefaultValue="false" />

    It’s not easy to get a code snippet right in this blog. 😉

  8. Anyone to confirm the fix Kevin is listing? And this is the same story when Win 8 arrived.

  9. Anyone to confirm the fix Kevin is listing? And this is the same story when Win 8 arrived.

  10. Kevin Vancraybex says:

    Thomas: we are using this solution succesfully, I hope it also helps you out. The first line of code is not yet present in web.config, the second is. The only addition in this line is OR Windows10, so UAG sees Windows 10 as "newer than 2000".

    1. Steve says:

      Do you need to restart the UAG servers after making the change to web.config?

  11. Hi Kevin.

    The solution works. Thanks.

  12. LeeO says:

    Thank you Kevin – Works perfectly!

  13. Sylvain Douillard says:

    Hi,
    Is it necessary to apply Rollup 2 for Forefront Unified Access Gateway 2010 Service Pack 4 in order to make UAG work with Windows 10 ?
    Or is it possible to solve issue only with Kevin’s workaround ?
    Thanks.

  14. Scott Jacobs says:

    I would also like to know if SP4 RU2 is a requirement, I have updated my web.config files on SP4 RU1 but still showing firewall not detected.

  15. Yuriy says:

    Hi, i’ve managed to get workaround working with RU1, where i can see all published apps, however i’m not able to use any RemoteApp applications, and i’m pretty sure it’s because RDS active X plugin is not being loaded. Anyone knows how to get it loaded?
    Thanks

  16. Matt H says:

    I’ve added the line and edited the other as advised above. It still wouldn’t allow the RemoteApp applications, however if you run the gateway through Internet Explorer (type Internet Explorer into the search box next to the start button) rather than the
    Win 10 inbuilt edge browser it all worked fine for me.

  17. manu says:

    @Kevin: Thanks it works

  18. Sylvain Douillard says:

    Hi,
    I have applied SP4 RU2 and Kevin’s workaround.
    @ Kevin : thanks a lot ! It works for me (portal access and RDS session)
    However, it does work only for Windows 10 migrated after activex installation.
    For a Windows 10 connecting for the first time on the portal, activex installation is not prompted.
    Asking to Microsoft about that…

  19. Rainier Amara [MSFT] says:

    Adding this to the InetrnalSiteweb.config simply allows for UAG to identify W10 clients as W10, but has no bearing on the ability to install the client components on W10 clients. Anything that depends on the CCs, such as endpoint checking for AV, PFW,
    or updates, plus also the socket forwarding capabilities, and more, are not possible for W10.

    RDS apps on the other hand, do not require the UAG CC’s, but rather the standard MSRDP Active-X control. The reason why you do not see them if connecting from a W10 client, is that they are only offered to post Windows 2000 clients, and where the browser in
    use is IE.

    Note. This applies to RDS apps that are published using RDG on UAG, so Remote Apps, Predefined, and User defined, but not the other two legacy apps.

    Windows 10 and WAP/CWAP is the future…

  20. IN says:

    are the characters in the web.config case sensitive?
    If we added the lines, all other (older) clients, can’t access the rdp-sessions, too…

  21. A says:

    I assume we are still waiting for a workaround regarding being prompted for active X on win 10 using UAG for first time.

  22. jamie says:

    Anyone noticed high memory utilization on the UAG server after installing this roll up?

Skip to main content