Thank you for the feedback. Multi-monitor support is definitely a feature we’d like to support in the future. It may take a little while as we’ll need to make changes to the core UWA platform.
Similar to mRemoteNG, the ability to store the connections in a exportable/importable xml configuration file54 votes
Thank you for the feedback. This is something we’d like to add in a future update.
Allow the app to save all of it's settings, connections, and accounts to your Microsoft account to take across all devices.120 votes
This is something we’d like to enable by allowing users to sign in to the app so we can roam their information between devices.
In the standard Remote Desktop Connection software you can move files between the remote and local computers easily. Provide a file copy mechanism for doing this in the new client.344 votes
Definitely a feature we’d like to add at some point. Copy/Paste of text is now available after it was added in the last update. File copy is more restrictive due to the sandbox the app runs in but we do plan on looking for a way to support this.
Now that Xbox One uses Windows 10 OS, can you bring the Remote Desktop App to Xbox One?64 votes
Thank you for the suggestion. We’ll see if this gains traction over time.
I like storing my credentials on my mobile devices. This can however be a security risk. Can you please add a PIN or Password protection option for the app?32 votes
Thank you for the feedback. This is something we’ll be investigating to minimize the risk of saving the credentials.
.\Administrator can be different on different computers, need to be able to save multiple copies of the same credentials.17 votes
There is a solution in place today for this although we know we need to make this more intuitive.
If two PCs have the same username like administrator, they can be saved by prepending the username with the machine name instead of just a dot. PC1\administrator and PC2\administrator.
Would love to hear your thoughts on this approach versus having to add an additional field for the nickname.
Ability to use the remote screen application vertical12 votes
This is something we plan to support in the future. I’ll update this when we have additional information.
Frequently I need to remote into machines which are "sleeping" and I need to use a Wake on Lan tool to wake them, wait, and connect using remote desktop. I would like to see Remote deskop beeing able to send a magic packet and keep trying to reconnect for a couple of minutes until the remote machine is ready.45 votes
New Windows 10 verison doesn't allow Smart Card as a sign in option. Need smart card to log in to work PC.
I used to log in through a gateway. When prompted for Username/Password, I was able to choose Virtual Smart Card as login option instead.
Now, there is no other login option besides username and password.
I can't log into my work PC without smartcard capability. This ruined the Modern App for me and I now have to go back to the Desktop app.8 votes
This is something we aim to support in a future release.
Each remote session should go into its own virtual desktop on the local machine. This would allow a very clean representation of the remote in the local working environment.43 votes
Definitely an interesting idea and something we’ll investigate.
LOVE THE NEW UPDATES BUT IT KEEP SAYING CONNECTION WAS INTERRUPTED MMMMM SO ANNOYING AS IT STUCK ON RECONNECTING
LOVE THE NEW UPDATES BUT IT KEEP SAYING CONNECTION WAS INTERRUPTED MMMMM SO ANNOYING AS IT STUCK ON RECONNECTING1 vote
It would be good to be able to interact with 2 or more servers at the same time, by interacting with the thumbnails and have the mouse move freely between them. Drag and drop between thumbnails would also be nice, similar to mouse without borders.11 votes
Interesting idea. Let’s see if it gain popularity.
Allow the stipulation of specific ports (i.e. 127.0.0.2:734)
When using Putty we enter 127.0.0.2:734 using Remote Desktop Connection Manager and it works well. However when using Remote desktop (metro style) it fails to connect. Using Windows 10 Enterprise Edition1 vote
Should work today. Investigating.
The delay to show the app chrome should be longer. It is too easy to close the remote session if I just want to close an app on the remote.
The delay to show the app chrome should be longer. It is too easy to close the remote session if I just want to close an app on the remote.6 votes
Thank you for the feedback. Definitely something we’ve noticed. We are looking into how we could best address this.
Right now each time you connect the checkbox for "store user name and password" is checked. Meaning each time you connect you have to unselect this option.
I would like to have the option of turing this feature off by default.1 vote
Hi Brett, can you let me know which client you are using so we can better help.
Support nonstandard ports. When I type localhost:5990 into mstsc, my ssh-forwarded RDP works. Remote Desktop Preview ignores it and fails.
To connect to particular remote machines behind firewalls and whatnot, I use SSH with TCP port forwarding with mstsc with no problem. I can type localhost:5990 and successfully connect. However, Remote Desktop Preview seems to ignore the port I specified and asks me if the remote computer is on or not.1 vote
Hi Nathan, it looks like the issue might be more with “localhost” than the port as the preview supports specifying the port already the same way as MSTSC with :port. I’m trying to understand the scenario where you need to use localhost. Mind replying to the email with more details?
- Don't see your idea?