Windows Server Web Application Proxy – updated Remote Desktop Gateway publishing documentation available


 

We’re pleased to let you know that we’ve just published updated documentation for publishing Remote Desktop Gateway with Windows Server Web Application Proxy which you can find here -  https://technet.microsoft.com/en-US/library/dn765486(WS.11).aspx

We have covered the 2 key scenarios of pass through authentication and pre-authentication without SSO in the updated docs. Remote Desktop Gateway publishing has a number of complexities which we’ll dive into in a subsequent blog, talk about some of the constraints we have around SSO and discuss further deployment options.

If you have any specific questions please add a comment below and we’ll try to include what we can in the follow-up blog.

Thanks,

Ian Parramore, Senior Escalation Engineer, Application Proxy support team

Comments (1)

  1. Alexander says:

    Thanks for update, Ian

    Maybe it’s not right to post it here, but I really cannot find info about this error nowhere, so I hope you give me some clues.

    I have Sharepoint 2010, Sharepoint 2013, SharePoint Online and Exchnage 2010 published through WAP with ADFS. All seems to work well, except I constantly receiving event 13006 for OWA

    Connection to the backend server failed. Error: (0x80072ef1).

    Details:
    Transaction ID: {ee73837c-ce2a-0000-e79e-7bee2aced001}
    Session ID: {ee73837c-ce2a-0000-3549-7bee2aced001}
    Published Application Name: OWA
    Published Application ID: b2b168cc-c7c9-302f-90b6-d2f6cd9c7770
    Published Application External URL:
    https://mail.avestragroup.com/owa/
    Published Backend URL: https://outlook.pditgroup.net/owa/
    User: s.andrey@avestragroup.com
    User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; Trident/7.0; rv:11.0) like Gecko
    Device ID:
    Token State: NotFound
    Cookie State: OK
    Client Request URL:
    https://mail.avestragroup.com/owa/ev.owa?UA=0&oeh=1&ns=PendingRequest&ev=PendingNotificationRequest&canary=DETsKBSNvkeizwhTpWy7rcyp4XnootIIZJHCBLO96j20jddlLkC6lt7FrKnYdHn1mmqPYhrvc1s.
    Backend Request URL:
    https://outlook.pditgroup.net/owa/ev.owa?UA=0&oeh=1&ns=PendingRequest&ev=PendingNotificationRequest&canary=DETsKBSNvkeizwhTpWy7rcyp4XnootIIZJHCBLO96j20jddlLkC6lt7FrKnYdHn1mmqPYhrvc1s.
    Preauthentication Flow: PreAuthBrowser
    Backend Server Authentication Mode: WIA
    State Machine State: FEBodyWriting
    Response Code to Client: 200
    Response Message to Client: OK
    Client Certificate Issuer:

    In spite of the error OWA seems to work though users tell me sometimes that OWA freezes and won’t let them send email of add attachment. There is no errors on Exchnage CAS servers.

    Request URL can be different of what I posted before. For example:

    Client Request URL:
    https://mail.avestragroup.com/owa/ev.owa?UA=0&oeh=1&ns=PendingRequest&ev=PendingNotificationRequest&canary=2EYlucVqF0OAXb_oE5sSLdJIG2jeotIIxRpoT3mG32ZqlfoFtbjjQiC1S2M1u2GDWfcKbKhEKeE.
    Backend Request URL:
    https://outlook.pditgroup.net/owa/ev.owa?UA=0&oeh=1&ns=PendingRequest&ev=PendingNotificationRequest&canary=2EYlucVqF0OAXb_oE5sSLdJIG2jeotIIxRpoT3mG32ZqlfoFtbjjQiC1S2M1u2GDWfcKbKhEKeE.

Skip to main content