Search results

This fix worked for me as well. See Knowledgebase Article 125592

We were experiencing the problem with VDI-published remote desktops prompting for passwords in the HTML5 client and the NLA user getting locked in AD, and it seems to be resolved in RAS 19 build 23476.

We are running RAS 19, latest build as of this post. We are publishing remote PCs using a Remote PC Static Pool Provider in the VDI component of the farm. Users connect remotely via gateways authenticated with Azure AD, and that all works fine. Users can get to their assigned desktops and work...

Ok, figured out my own problem. I used the app federation metadata url to import the configuration for the IdP in the RAS console. It did not import the certificate correctly, so I went back and exported the certificate from Azure AD for the SAML enterprise app I created, and then imported that...

I have setup the enterprise application in Azure AD for SAML authentication, and configured the Enrollment server, the enrollment service user, the nla user, and the SAML connection in the RAS console. Everything seems to check out, but when my user tries to authenticate to the Secure Gateway, I...