User Profile
briantaintor
Former Employee
Joined 7 years ago
User Widgets
Recent Discussions
Windows Virtual Desktop web client to end support for Internet Explorer
Beginning 30 September 2021, the Windows Virtual Desktop web client will no longer support Internet Explorer 11. Beginning 30 September 2021, the Windows Virtual Desktop web client will no longer support Internet Explorer 11. We recommend that you transition to using the Microsoft Edge browser instead of Internet Explorer 11. See the full list of supported browsers. Why is this change happening? Customers have been using Internet Explorer 11 since 2013. Since then, new browsers like Microsoft Edge have enabled better and more innovative online experiences. Windows Virtual Desktop users can benefit from this change because Microsoft Edge offers better web client performance, more advanced features like file transfer and microphone redirection, and greater security. Microsoft Edge delivers frequent security updates to help keep your organization protected. You can find the full list of Microsoft apps and services to end support for Internet Explorer 11. In addition, Internet Explorer 11 desktop application will be out of support on 15 June 2022. How does this affect me? Starting 30 September 2021, you'll be unable to access the Windows Virtual Desktop web client on Internet Explorer 11. We'll continue to support the web client on Microsoft Edge, Safari, Google Chrome, and Firefox. You can also connect to your Windows Virtual Desktop environment with the Windows Desktop client on Windows 10, Windows 10 IoT Enterprise, and Windows 7. If you rely on Internet Explorer 11 for legacy apps, you can use Internet Explorer mode on Microsoft Edge. You can standardize on one browser and seamlessly access the best web client experience in one tab while accessing a business-critical legacy Internet Explorer 11 app in another tab. More information If you're using Internet Explorer 11 to access the web client, support options are available to help transition to Microsoft Edge. Check out the Internet Explorer 11 lifecycle announcements for more information.Re: RDS Web Client RemoteApp Default Language always en-US
ChrisH0701 there is a bug with the web client where we send a default keyboard layout (ENG US) when initiating the connection. We are actively working to resolve this issue and will push an update to the client as soon as possible. We will have a more definitive ETA soon. In the meantime, keyboard input should work as expected as the client sends Unicode input by default. Until this fix makes it to production, the proofing language, etc. will be an issue.[Resolved] WVD web client connection errors in Google Chrome and Microsoft Edge (Chromium)
UPDATE: This issue has been resolved in Production. A fix for pre-production environments will roll out with normal service updates. A number of users have reported issues connecting to the WVD web client using both Microsoft Edge (Chromium) and Google Chrome. The February release of the new Chromium 80 engine - used by both Edge and Chrome - included changes SameSite cookie classification. More information can be found on the Chromium blog and Chromium developer guidance. We are working on rolling out a fix to production. In the interim, please use the following workarounds to continue using the web client: Use Mozilla Firefox In your Microsoft Edge (Edge://flags) or Google Chrome (Chrome://flags) browser, disable both the SameSite by default cookies and Cookies without SameSite must be secure flags. Please note the warning presented: "By enabling these features, you could lose browser data or compromise your security or privacy. Enabled features apply to all users of this browser." We will post an update on this thread when a fix is available in production.How to test Windows Virtual Desktop clients
We have received a number of questions from users regarding how to test Windows Virtual Desktop from our HTML5, Windows, macOS, iOS and Android clients. Here's how: HTML5: aka.ms/wvdweb Windows: Download the Windows client here and refer to this documentation. iOS (Beta): On your iOS device, visit aka.ms/rdiosbeta and follow the instructions. macOS: Download the macOS client from the App Store. Android: Download the Android client here and refer to this documentation. For more information about Windows Virtual Desktop: aka.ms/wvd For more information about the Remote Desktop Clients: aka.ms/rdclientsRe: How do I signup for the iOS beta of the Windows Virtual Desktop client?
Paul Shadwell the full feed url is https://rdweb.wvd.microsoft.com/api/feeddiscovery/webfeeddiscovery.aspx There are options to setup email discovery for a user-specific or group-wide email address. Additionally, feed autocomplete for the iOS client will be functional in the near future, meaning you won't have to enter this full url. CheersRe: How do I signup for the iOS beta of the Windows Virtual Desktop client?
Paul Shadwell all of the steps required to setup and connect to the iOS Beta client are included in the same documentation found at aka.ms/rdiosbeta. 1. On your iOS device, visit https://aka.ms/rdiosbeta 2. Download the Apple TestFlight app from the iOS App Store 3. Head back to the page from Step 1 (above) on your browser and select select Start Testing under the label Step 2 Join the Beta. 4. Accept the invitation on the TestFlight page you are redirect to and install the Beta client. 5. Open the Beta client and add your remote resource feed just as you would on other clients.Re: Thin client support
fbcarvalho01 you can connect to Windows Virtual Desktop from thin clients using the HTML5 client. Currently, we do not have a native client for thin clients (i.e., Linux or Windows) but we are investigating this for the future. What thin client(s) in particular are you interested in using? Is there a particular thin operating system you would like to us? And/or a particular device type?Re: Trouble with the MAC and IOS apps on Windows Virtual Desktop
Oliver-76 To add your remote resource feed on the iOS client use the following feed url: https://rdweb.wvd.microsoft.com/api/feeddiscovery/webfeeddiscovery.aspx If you continue to run into issues, please reply to this post to let me know.
