RDS prompting for dual credentials on RDWEB

I’ve followed through this thread in detail.  We still cannot open published remoteapps.  At one point early on, we were able to – that was when we were using a self-signed certificate with only the internal server name.  Now we are trying to take it public and having troubles.

Starting the app fails when we get a new authentication dialog after clicking Connect on the rdp launcher. For example:

Notice that the remote computer (green oval) used to have our internal server name but this was fixed with the Set-RDPublishedName cmdlet.

But this still gets followed by:

Notice (red ellipse) that it’s trying to authenticate against the server’s internal name.  When I browse directly to the internal server from inside the network it’s presenting the public certificate.  This certificate is issued by a publically trusted authority, so it’s likely failing because of the name mismatch.  I cannot get past this dialog box by any means and so we do not have access.

The way I read this thread, I would have thought the Set-RDPublishedName cmdlet would have taken care of this, but it didn’t fully.  When I look at Deployment Properties -> RD Web Access, the URL for the web access server is still showing the internal URL.  This is where I think it’s going bad.

I’m wondering if I missed something.  I’ve seen the HA mode suggestions, but feel that is an egregious non-reversible work-around and would rather not go that route until 1. I’ve exhausted all the options and 2. Am sure that this would resolve our final roadblock.

Our deployment is Server 2012 Standard R2, and we used the simple deployment option, so everything is on a single server.  The certificate is a single name certificate for the public name and works fine when authenticating against the public name.  Please help. We are a non-profit and don’t have access to high end support resources.

Thanks,

Karim