Embedding remote desktop web client in IFrame
Hi, we are currently working on a custom solution for a customer that builds upon Virtual Desktop. We have built a "cloud hub" website where the user manages everything from their profile, storage, viewing costs and dashboards. The customer would like to embed the Azure Virtual Desktop web client inside this website (i.e. not opening a new browser window/tab). Is this possible today? I tried creating a simple test.html with only an iframe tag and the page (as shown below). See attached image for result: <iframe width="560" height="315" src="https://rdweb.wvd.microsoft.com/arm/webclient/index.html" frameborder="0" allowfullscreen></iframe>
RDS 2019 HTML 5 keyboard shortcuts
Hi everyone, We have implemented HTML5 with Azure application to allow users to connect from home to our RDS servers. It works great, however a couple of issues we found: keyboard shortcuts such as ALT+TAB (ALT+PageUP) not working (Or I need to change something somewhere) When publishing remote app to user it removes the remote desktop option. Icons are not display correctly... the user sees broken image icon Sometimes when clicking on an icon it won't work and a page refresh is required which results in another login page. When changing language (using ALT+SHIFT), the RDS is not using the language configured in the session. It uses the language from the local computer. We would like to use HTML5 as it is more secure than the the RDP protocol. If there are any resolutions to what I wrote it would be amazing. Rahamim.
RD Client Android Fail...
Serious question, why is RD Client for Android the worst RD client? It does not work with Samsung DEX, sure it runs and connects, but fails at basic usability, like recognizing the actual screen size when windowed. Also, dosn't resize properly. Pretty basic stuff, nothing remotely new here. The Citrix and VM Ware clients just work, and work well. Microsoft and Samsung have a partnership in the phone space which makes this even more absurd. So, what's the deal? Laziness, incompetence, just don't care anymore? Will this ever be fixed? This makes me worry about every other product.
Wrong scaling when using web WVD in full screen mode
Hello everyone, I'm using RVD services. If I connect to a machine using Remote Desktop app, everything works like a charm. However, if I use this link (with Firefox, Chrome or Edge) and turn Full screen on, it won't scale correctly and will show a vertical scroll. Is there a way to avoid this? Best regards.
WVD Remote Desktop Client doesn't show provisioned tenant and hostpool
WVD Remote Desktop Client fails to show the created tenant and hostpool. But the HP shows available in powershell. SessionHostName : fshp-0.azureproduction.onmicrosoft.com TenantName : fstenant TenantGroupName : Default Tenant Group HostPoolName : fshostpool AllowNewSession : True Sessions : 0 LastHeartBeat : 3/27/2020 2:25:51 AM AgentVersion : 1.0.1288.2700 AssignedUser : OsVersion : 10.0.18363 SxSStackVersion : rdp-sxs191213001 Status : Available UpdateState : Succeeded LastUpdateTime : 3/27/2020 2:26:19 AM UpdateErrorMessage : Tried creating multiple tenants and hostpools. HP Deployments was successful but fails to show up in the client. It looks like your system administrator hasn’t set up any resources for user@domain.com yet. Please choose a different account or try again. If you believe you have received this message in error, please contact your system administrator.
Solutions for WVD client not connecting
I, and it seems many others, have had issues connecting to windows virtual desktop after provisioning seemed successful. This manifests with the web client giving errors after opening port, or with the desktop client saying something went wrong and a vague explanation. Turns out there are a few rules that must be followed that aren’t mentioned anywhere I looked. 1) the user you are logging in with must be from the local AD or from the AADDS ... NOT an AzureAD user. It must be synced but it must originate from local AD. It must be a domain user. You won’t see what the issue it, but it will fail. Your domain controller does the sign in Authentication, but it’s initiated through azure, so it must be synced and visible in azure but actually created in domain. AzureAD users won’t sync back to the domain so that’s why it needs to be created in domain. Remember to add the domain user to the app group via add-rdsappgroupuser as well. 2) you can’t be logged into windows with a different Microsoft account for the desktop client. The new client apparently looks at the windows accounts, and you will see there is no way to change accounts from the desktop client. This is very annoying. Since it’s tied together if you are logged into a personal Microsoft account or one not from your local AD that’s not been added to the appgroup, it will fail. I was testing accounts but I was logged into windows with my personal Microsoft account and it always gave errors. I logged out, and into the local computer account , and the desktop client worked fine. I figured this out because after I removed the additional testing accounts from windows users I got a Login screen but then it still failed with the same “something went wrong” error. This led me to think it might be getting confused because I could have multiple work accounts on computer and the client never asked which to use. Instead of a VM issue it’s just the client isn’t smart enough to ask which account you want to use even after login. Item 3 also led to to realize that it’s getting confused with accounts. 3) use incognito to test web client. Even though I logged out of azure portal, out of my own Microsoft account, etc, the web client kept failing to connect. BUT if I ran incognito it connected. This told me the app isn’t able to distinguish the account I needed to use. Again, my personal account still had a trace somewhere in the browser and this kept causing issues. WVD kept trying to use an account that’s not part of my WVD setup, hence failure. Try incognito. I hope these items help you out. None of these were made clear and I beat my head for 3 days re-launching WVD VMs and tenants. Turns out the setup was fine the whole time. It’s the WVD clients that suck. The desktop client must have a way to login a user and NOT pull from windows. Or at least give the user a clear error that explain what account it’s trying to log in with. Just telling me what account it tried to used on either the desktop client or webclient would have identified this in an instant. The diagnostics log weren’t clear enough either. Ultimately Please just separated the sign ins. Not everyone wants to use SSO, especially a remote worked on their personal laptop that’s not domain joined, or joined to a different domain. Hope this helped some people out.
