Why don't you try a third-party remote control software like AnyViewer? It's really easy to operate. You can have access to another computer as long as the two computers are connected to the Internet. There's no need to set up anything. I think it's the best Windows RDP alternative.
Took me a while to check how to copy-paste from Windows into a Mac via Google Remote Desktop.
Open the Session options via the arrow, select Configure key mappings and map:
There is another solution - edit .rdp file with notepad. Try changing "screen mode id:i" parameter to 2. Additionally you can try to experiment with "winposstr" parameter. Look in paragraph "Calculating the Values for winposstr".
Also you can try to setup rdp-connection from scratch. It can help, for example, if you have created ...
It is possible if you cursor is on the taskbar. So if you want to switch to host computer from remote using nothing but keyboard, first move your cursor to the taskbar (enable mouse cursor movement using keys), and then press Alt+Tab, the remote desktop client will now be just another window that can be switched away from.
One option is looking in call software settings. There's usually an option to pick which audio input source to use, and your laptop microphone can sometimes be available as a virtual device you can choose, depending on which remote access technology you use and what kind of call software you have.
However, this is unlikely to be a good solution, because of ...
Windows 10 is just for single client usage at a time.
As soon as a second user tries to connect with the same OR other credentials the other one will automatically disconnect. Otherwise terminalservers would be a misconception of microsoft since they are not special anymore.
There's another thread that discusses answers in addition to the display and bitmap troubleshooting options you mention (Windows 10 Remote Desktop Connects with Black Screen then Disconnects).
Ranges from downloading RDC Manager ,(https://docs.microsoft.com/en-us/sysinternals/downloads/rdcman) to pressing or triggering (if a VM) CTRL+ALT+DEL to bring up the ...
Try connecting to the remote server first, and importing the module there:
Enter-PSSession -Computername 'RD-Server01'
You can install the RemoteDesktop module on your local machine too:
Get-WindowsCapability -Online -Name Rsat.RemoteDesktop.Services.Tools* | Add-WindowsCapability -Online
For any bug-related issues on Microsoft Remote Desktop for Mac, install the beta app [you can run release & beta side by side]
Downloadable from https://install.appcenter.ms/orgs/rdmacios-k2vy/apps/microsoft-remote-desktop-for-mac/distribution_groups/all-users-of-microsoft-remote-desktop-for-mac
It includes a good bug reporter & what's more ...
The problem is xrdp service init script does not detach stdout before returning and once wsl.exe exits, it closes all pipes which terminates the script.
Straightforward *nix tool for this problem is nohup, but it redirects output to file.
>wsl nohup sudo service xrdp start
nohup: ignoring input and appending output to 'nohup.out'
Somewhat weird ...
Powershell is just a local shell. To make a change in a remote system you need to be able to access it first, which means you need to be able to login...
I would personally just call the customer, tell him about the funny little mishap that requires you to login before you can change your password to login, have a ha-ha together and ask him to please reset ...
First off, what you are proposing - as stated - is foolhardy. Exposing your computer to the wider Internet way is foolhardy.
The missing bit requires modifications on the router. In addition to handling the mapping (im being deliverately vague - if you dont know enough to do this you should not be following some guy on the Internet), consider firewalling rdp ...
I realized I never came back to this. In the end rebooting both systems resolved the issue. Audio pass through worked in both directions using a headset connected to my desktop. Should have tried a reboot before much earlier in the troubleshooting process.
thank you for your help. I reached out to them and they told me what I needed to do. I had to setup a subnet router in my work machine. The documentation is misleading in that it tells you that you can only setup a subnet on linux, but I was curious and I look at the CLI and the option was there. The specific command you have to run is tailscale up --...
Try with the resolution slider as shown in the screen shot:
I used my small screen Laptop (1366x768) and set the slider to full screen (farthest right) and was able to see the remote screen in a larger resolution (1920x1280).
I tried all the above mentioned tips but none resolved my remote sound issue.
What did resolve it was going to the settings->system->sound on the client PC, scrolling down to "Advanced sound options" and selecting "App volume device preferences" and lone behold the "RDP app" volume was set at zero. Once increased to 100 ...