![]() My gut tells me it is something related to the insider build of Windows and not the company that is hosting the application, because it is working fine on all the machines running the currently released version of windows and it is showing this behavior in 2 machines I have running the insider build. Right clicking (trying to call a right click command) also is not working in this scenario. It is hard to describe the behavior, but when other windows are open on our host machine (Edge, Teams, MS Office, etc.) and when a user has multiple screens (remote app only using one), when we call for something to happen in the remote app (like run a report), the remote app appears to freeze, and the only way to get it to refresh, is by clicking on one of the other programs that are open on our host machine (on the task bar) and then back to the remote app. We have a remote app installed on our desktop that is connected to an application we use hosted by someone else. Please feel free to contact us if there is any update on your test.Hello, running 1803 (build 17134.1) and have been running into a "Remote App" behavior problem for a while (not sure what version it started on). You can test to upgrade the windows of remote desktop. I didnt try the effect of the other settings in Windows 11 display settings: Remember windows position and minimize windows. After that I am able to work with multiple displays local and remote as on Windows 10. Mark the same display as primary as in the NVIDIA Control Panel. Then the microphone fails to be redirected to the remote desktop. Go to Windows 11 > display settings multiple displays. Since the version of laptop is higher than the remote desktop, then the remote desktop may have lower driver version, which cannot drive the laptop's microphone. Local Computer Policy->Computer Configuration->Administrative Templates->Windows Components->Remote Desktop Connection Client->RemoteFX USB Device Redirection-> Allow RDP redirection of other supported RemoteFX USB devices from this computer.Īs you described, the issue also maybe caused by the windows version. To make sure the remote computer is online, open a command prompt and ping to it. Navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop. Then try connecting again by computer name. Testing Easy Print with an RDP connection. Please ensure below two policies are enabled or not configured.Īllow audio and video playback redirectionĪnd on the laptop, please enable below policy. Open a command prompt and type ipconfig /flushdns. Local Computer Policy->Computer Configuration->Administrative Templates->Windows Components->Remote Desktop Session Host->Device and Resource Redirection You could first check the group policy setting on the remote PC I'm not sure if the issue is related to the version being one behind on the desktop(I will try to get at least one upgraded to test this weekend).Īny insights you can provide is appreciated. Laptop (Win 10 1909) remoting into a Desktop (Win 10 1903) Laptop (Win 10 1903) remoting into a Desktop (Win 10 1809) I have had the same issue with 2 other laptops/desktops (I not tried remoting into a VM to test that aspect) The local (laptop) speakers and mic work fine on the remote machine as desired. With the same laptop and same settings as above I can remote into a VM (Win 10 1909) and I see remote audio is selected as output and remote audio is selected as input. On the remote desktop, in Windows 10 settings, I see the remote audio is selected as output, but it has no input devices found. Remote Desktop connection settings: Play on this computer, record from this computer are both checked. The microphone is an integrated mic in my laptop. I am trying to pull in the microphone from a local machine (Win 10 1909) to a remote machine (a physical desktop-Win 10 1903).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |