Hi Gordan, Thank you for providing us the opportunity to assist you. I can imagine the inconvenience you are experiencing and will certainly help you in the right direction to fix the issue. Are all the device drivers updated specifically network drivers? As per the issue description you are facing issue in using Remote desktop connection feature on your computers. There might be a chance that some Remote desktop connection (RDC) settings get corrupted or the services responsible for the connection are not running. To get started, we need to make sure a few things are setup properly, otherwise you will pull you hair out trying to figure out why Remote Desktop is not working.
Alt+Home—Pressing the Alt+Home keyboard combination with Remote Desktop displays the Start menu on the remote system. The Start menu gives you quick access to the different programs installed on the remote system. This key combination is the same as pressing the Windows key on your local desktop. I had the same problem using microsoft remote desktop on a mac with OSX Yosemite. My symbol keys did not work correctly, for example the became Mac that was running the RD client, and under keyboard I noticed that my input source was set to Canadian English. I added US English, deleted Canadian English, and restarted the remote desktop session.
On the Windows 10 machine you want to remote desktop into, you need to make sure the user account has a password. You also need to make sure your account is an administrator account on the system. You have to make sure the firewall on Windows 10 allows remote desktop to the machine.
You have to enable remote desktop in the System settings. I will go through each of these steps so that you can see exactly what needs to be done in order to properly get remote desktop working. First, make sure you set a password for your administrator account. Once you have done that, go to Control Panel By pressing Windows key + X and selecting Control panel and click on Windows Firewall. Click on Allow an app or feature through Windows Firewall and then you will scroll down until you see Remote Desktop. Make sure the box is checked.
Make sure it’s only enabled for the Private network, you don’t want anyone in the world being able to remotely connect to your computer! Once you have done that, we can go to Control Panel and click on System. Then click on Remote Settings at the top left. Now check the Allow remote connections to this computer box. Note that there is another option called Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended).
![Microsoft remote desktop download Microsoft remote desktop download](/uploads/1/2/5/4/125492155/204129867.png)
If you enable that, you will need to make sure you are running a remote desktop client version 6 of higher. You can check whether your version of remote desktop supports Network Level Authentication by opening remote desktop on the client machine (the computer you’ll be using to conned to Windows 8) and clicking on the icon at the top left and click on About. If your version of Remote Desktop Connections supports it, it will say Network Level Authentication supported. Now open remote desktop connection, type in the computer name and click Connect.
That’s pretty much it! If you have issue, try disabling Network Level Authentication and see if you can connect.
Remember, as long as you have a password for the admin account, allow remote desktop through the firewall and enable remote desktop in system settings, you should be able to remote desktop into Windows 8 without a problem. If issue still persists, I would suggest you to v erify these services and check if they are started, in services list or not. DCOM Server Process Launcher. RPC Endpoint Mapper. Remote Procedure Call (RPC). Security Accounts Manager.
Server If they are not started, start them and check. Follow the steps below to check the status.
Press Windows key + R to open run box, type “ services.msc” in the run box and press enter. Scroll down and check for the above mentioned services. Double click each of the services and start them if they are not started. Additional Information: I would suggest you to go through the links and articles mentioned below and hope you will be able to get the answer of your query and more information about remote desktop. To connect to a remote computer, that computer must be turned on, it must have a network connection, Remote Desktop must be enabled, you must have network access to the remote computer (this could be through the Internet), and you must have permission to connect. For permission to connect, you must be on the list of users. Before you start a connection, it's a good idea to look up the name of the computer you're connecting to and to make sure Remote Desktop connections are allowed through its firewall.
Note: The images and screen shot added is for Windows 8/8.1 but steps hold good for Windows 10 too. Hope the information provided is helpful. Do let us know if you have any queries related to Windows, we will be happy to assist you.
This is pretty frustrating especially if you are coming from the RDP app packaged with MS Office for the Mac, which honored Cmd+C and Cmd+V. I use an app called KeyRemap4MacBook (to make 'Cmd' appear as 'Ctrl' only to RDP. After installing it, start it up and -.
on the 'Change Key' tab, go down to the 'For Applications' section. 'Enable at only Remote Desktop Connection Client' sub-section.
Check 'Command + XCVSZWF to Ctrl + XCVSZWF'. Check 'Command keys to lazy command keys' Now when you use the new RDP app, you can continue to use Cmd instead of Ctrl. This is pretty frustrating especially if you are coming from the RDP app packaged with MS Office for the Mac, which honored Cmd+C and Cmd+V. I use an app called KeyRemap4MacBook (to make 'Cmd' appear as 'Ctrl' only to RDP. After installing it, start it up and -. on the 'Change Key' tab, go down to the 'For Applications' section.
'Enable at only Remote Desktop Connection Client' sub-section. Check 'Command + XCVSZWF to Ctrl + XCVSZWF'. Check 'Command keys to lazy command keys' Now when you use the new RDP app, you can continue to use Cmd instead of Ctrl. ' This is by design and we cannot change it.' This design is ignorant of how Macs actually work.
For shortcuts, the Command key on a Mac is equivalent to the Control key on a PC. For example, on a Mac, Cmd+C/Cmd+V are the shortcuts for copy/paste.
This convention follows for just about every shortcut you can imagine. So hopefully Microsoft can understand that this makes it incredibly frustrating for Mac users. Simply switching Cmd and Ctrl keys would be fine. Or better, let users create their own mappings, which was actually possible in the older version of RDC Mac. I would not have installed the new version had I known about this ahead of time. Does Microsoft offer any workaround for this? Jeremy Wu: This really does need to be corrected.
At least add a setting to allow users to toggle the key or add some basic mapping config. I rage everytime I connect to our windows servers from my mac and have to use the clipboard. 'This is by design and we cannot change it.' Of course you can change it.
I'm a software engineer and we change things all the time to make our product easier for our customers to use. We don't tell them to just suck it up and take whatever we give them. I would hope everything your engineering team does is 'by design'.
Whether its a good design or not is a whole other story. That's why customer feedback like this is so important. Instead of just shutting this issue down, why not send this to the dev team for consideration?