Forum Discussion
rbergertd
Mar 23, 2019Copper Contributor
Invalid connection file - Any ideas how to get past this?
Hey all, I've been chipping away at getting a WVD proof of concept going, and I'm at the point where I have a successful deployment, and I think I am ALMOST all the way there. I have a demo tenan...
stevenzelenko
Mar 23, 2019Copper Contributor
rbergertd Yeah. Since this is so new, it's hard to troubleshoot and I'm just going by past things I know. Question, I had issues earlier where I could not log into the HTML5 until I made the user a tenant creator in Azure AD for WVD. But the RDS app worked fine. Quirky but it's only day 2!
rbergertd
Mar 23, 2019Copper Contributor
stevenzelenko Thanks for the rec. I did check the tenant multiple times and I *think* everything is provisioned. Does this look okay to you? It's so odd, but I'm happy to end the night on a win with at least figuring out HTML5 is working. :)
- stevenzelenkoMar 23, 2019Copper Contributor
rbergertd That is how mine looks. The HTML5 integration is fantastic. I would check your WVD application users in Azure AD and maybe put your test user as a tenant creator. I had to do that for all my synced test users to get it to work flawlessly. It doesn't sound right but it works. And I got MFA working too. Cool stuff this.
- rbergertdMar 23, 2019Copper Contributor
stevenzelenko Yea, I had tried that - no dice unfortunately. I still get that file error. Ugh!
- rbergertdMar 24, 2019Copper Contributor
stevenzelenko Just a little more info, I just checked the status of my RDS Session host and it all looks good. I am convinced this has gotta be something on the client end. I tried forcefully removing the .RDP files that the client creates in AppData and letting it recreate them, but it's still giving me the same error so who knows. The thing that is a bummer, is what I am working on, I really need the native RDP experience and don't want to even start testing it with the HTML5 piece. :(