12/27/2021»»Monday

Remove Microsoft Remote Desktop Connection Mac

12/27/2021

Step 1 – Download the Microsoft Remote Desktop Client. To do this you will first need to download the latest RDP client for Mac on the Mac App Store. Step 2 – Open the Microsoft Remote Desktop Client. Open up the the Remote Desktop client by clicking on the launchpad icon and then Microsoft Remote Desktop. Step 3 – Set up your connection. Click on New.

Microsoft Remote Desktop, a free application from Microsoft, allows you to use a Mac laptop or desktop to connect to and work from a Windows desktop computer that you have RDP access to in your on-campus office or lab. If you aren't sure whether you have RDP access to a certain machine, feel free to check with ECN via our Trouble Report System:

Put simply, Microsoft Remote Desktop from a laptop or a home computer makes it as if you're sitting at the desk in your office using your computer's keyboard and mouse -- even if you're two buildings, two miles, or two continents away.

Microsoft Remote Desktop For Mac

By remotely accessing an ECN-supported desktop computer and refraining from storing your Purdue files locally on your laptop or home computer, your data remains safely stored in your home directory on ECN's network servers -- which receive daily backups.

  • If you have a Windows-based laptop or home computer, Microsoft provides Microsoft Remote Desktop for Windows 7, please see Remote Desktop Connection in Windows 7.The instruction on the page you're reading now focus on the Mac OS X version.

You'll want to follow these instructions on your Mac laptop and/or at-home Mac-- not on the on-campus desktop computer! Before you begin, download and install Microsoft Remote Desktop free via the App Store to your Mac

When connecting from off-campus, please make sure to Purdue's VPN (www.webvpn.purdue.edu) first, as seen in step 1.

Who can use Microsoft Remote Desktop?

A remote-controlled computer can be used by only one person at a time. As such, this service is intended for use only by those who do not share the same office computer with other people. A graduate student may use Microsoft Remote Desktop with the permission of their supervisor.

Connection

Every ECN-supported Windows PC which will be used remotely must be pre-configured by ECN before this service will work. Please contact us in advance; we will provide you with the value that you'll need in step #3 as well.

Connecting to the Desktop Computer in Your Office

1. Connect to Purdue's Virtual Private Network. When using a computer off-campus, this step is required. Establish a connection to Purdue's Virtual Private Network (https://webvpn.purdue.edu). For a description of this service, please see ITaP's VPN 'Getting Started' page.

2. Launch the Microsoft Remote Desktop application from your Applications folder. The appropriate icon can be seen below:

3. Once the application opens up, you'll need to add your specific machine to the 'My Desktops' list. To do so, click on New. A new dialog will appear. Fill it out as seen below-- making sure to substitute '128.46.xxx.yyy' with the actual IP address of your machine, 'username' for your Purdue Career Account user name, and 'Password' for your account password. Please note though that you will need to type either 'boilerad' or 'ecn'before your user name in order to successfully authenticate to your machine.

NOTE: If using the ECN RemoteAvailability website, please instead use the computer hostname INSTEAD of the IP. you can do this by appending .boilerad.purdue.edu to the selected PC name from a green box.

IMPORTANT

If your computername begins with x- you will use 'boilerad' prior to your username.

If your computername DOES NOT begin with x- you will use 'ecn' prior to your username.

Again, if you do not know your computer's IP, feel free to check with ECN via our Trouble Report System. Once you enter all of the necessary information, click the red circle in the top right corner of the dialog to close it out and save your configuration. You should now see 'Office PC' in your list under 'My Desktops.' Feel free to change the 'Connection name' of your configuration to anything you like. More specific names can be helpful when you need to set up connections to multiple machines on campus.

4. When you double click on your newly created RDP connection ('Office PC'), the following 'Verify Certificate' prompt may appear.

If it does, simply choose 'Continue.' Your Windows screen should then appear to you.

5. When you're ready to disconnect from your Windows machine, you may end the session in one of these ways:

- Click on the Start menu and select 'Disconnect.' This will end the remote session but leave files and programs open and running on your office PC.

- Click on the round red button at the top-left corner of the window. This will end the remote session but leave files and programs open and running on your office PC. If you do not see the Microsoft Remote Desktop application menu bar with the red button, simply hover your mouse at the top of your screen until it appears.

- Click on the Start menu and select 'Log off.' This will close all open files and programs on your office PC and also end the remote session.

Last modified: 2020/03/25 17:42:52.793499 GMT-4 by michael.p.harrington.1
Created: 2008/07/31 10:21:59.307000 GMT-4 by john.a.omalley.1.

Categories

  • Knowledge Base > OS > Mac > OS X
  • Knowledge Base > ECN > RDP
  • Knowledge Base > Software > RemoteDesktop
  • Knowledge Base > OS > Mac

Search

Type in a few keywords describing what information you are looking for in the text box below.

Admin Options: Edit this Document
-->

Use these steps when a Remote Desktop client can't connect to a remote desktop but doesn't provide messages or other symptoms that would help identify the cause.

Check the status of the RDP protocol

Microsoft Remote Desktop For Mac Download

Check the status of the RDP protocol on a local computer

To check and change the status of the RDP protocol on a local computer, see How to enable Remote Desktop.

Note

If the remote desktop options are not available, see Check whether a Group Policy Object is blocking RDP.

Check the status of the RDP protocol on a remote computer

Important

Follow this section's instructions carefully. Serious problems can occur if the registry is modified incorrectly. Before you starty modifying the registry, back up the registry so you can restore it in case something goes wrong.

To check and change the status of the RDP protocol on a remote computer, use a network registry connection:

  1. First, go to the Start menu, then select Run. In the text box that appears, enter regedt32.
  2. In the Registry Editor, select File, then select Connect Network Registry.
  3. In the Select Computer dialog box, enter the name of the remote computer, select Check Names, and then select OK.
  4. Navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal Server.
    • If the value of the fDenyTSConnections key is 0, then RDP is enabled.
    • If the value of the fDenyTSConnections key is 1, then RDP is disabled.
  5. To enable RDP, change the value of fDenyTSConnections from 1 to 0.

Check whether a Group Policy Object (GPO) is blocking RDP on a local computer

Remove Microsoft Remote Desktop Connection Mac

If you can't turn on RDP in the user interface or the value of fDenyTSConnections reverts to 1 after you've changed it, a GPO may be overriding the computer-level settings.

To check the group policy configuration on a local computer, open a Command Prompt window as an administrator, and enter the following command:

After this command finishes, open gpresult.html. In Computer ConfigurationAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostConnections, find the Allow users to connect remotely by using Remote Desktop Services policy.

  • If the setting for this policy is Enabled, Group Policy is not blocking RDP connections.

  • If the setting for this policy is Disabled, check Winning GPO. This is the GPO that is blocking RDP connections.

Check whether a GPO is blocking RDP on a remote computer

To check the Group Policy configuration on a remote computer, the command is almost the same as for a local computer:

The file that this command produces (gpresult-<computer name>.html) uses the same information format as the local computer version (gpresult.html) uses.

Modifying a blocking GPO

Remove Microsoft Remote Desktop Connection Mac App

You can modify these settings in the Group Policy Object Editor (GPE) and Group Policy Management Console (GPM). For more information about how to use Group Policy, see Advanced Group Policy Management.

To modify the blocking policy, use one of the following methods:

  • In GPE, access the appropriate level of GPO (such as local or domain), and navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections > Allow users to connect remotely by using Remote Desktop Services.
    1. Set the policy to either Enabled or Not configured.
    2. On the affected computers, open a command prompt window as an administrator, and run the gpupdate /force command.
  • In GPM, navigate to the organizational unit (OU) in which the blocking policy is applied to the affected computers and delete the policy from the OU.

Check the status of the RDP services

On both the local (client) computer and the remote (target) computer, the following services should be running:

  • Remote Desktop Services (TermService)
  • Remote Desktop Services UserMode Port Redirector (UmRdpService)

You can use the Services MMC snap-in to manage the services locally or remotely. You can also use PowerShell to manage the services locally or remotely (if the remote computer is configured to accept remote PowerShell cmdlets).

On either computer, if one or both services are not running, start them.

Remove Microsoft Remote Desktop Connection Mac To Windows

Note

If you start the Remote Desktop Services service, click Yes to automatically restart the Remote Desktop Services UserMode Port Redirector service.

Check that the RDP listener is functioning

Important

Follow this section's instructions carefully. Serious problems can occur if the registry is modified incorrectly. Before you starty modifying the registry, back up the registry so you can restore it in case something goes wrong.

Check the status of the RDP listener

For this procedure, use a PowerShell instance that has administrative permissions. For a local computer, you can also use a command prompt that has administrative permissions. However, this procedure uses PowerShell because the same cmdlets work both locally and remotely.

Remote Desktop Connection

  1. To connect to a remote computer, run the following cmdlet:

  2. Enter qwinsta.

  3. If the list includes rdp-tcp with a status of Listen, the RDP listener is working. Proceed to Check the RDP listener port. Otherwise, continue at step 4.

  4. Export the RDP listener configuration from a working computer.

    1. Sign in to a computer that has the same operating system version as the affected computer has, and access that computer's registry (for example, by using Registry Editor).
    2. Navigate to the following registry entry:
      HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerWinStationsRDP-Tcp
    3. Export the entry to a .reg file. For example, in Registry Editor, right-click the entry, select Export, and then enter a filename for the exported settings.
    4. Copy the exported .reg file to the affected computer.
  5. To import the RDP listener configuration, open a PowerShell window that has administrative permissions on the affected computer (or open the PowerShell window and connect to the affected computer remotely).

    1. To back up the existing registry entry, enter the following cmdlet:

    2. To remove the existing registry entry, enter the following cmdlets:

    3. To import the new registry entry and then restart the service, enter the following cmdlets:

      Replace <filename> with the name of the exported .reg file.

  6. Test the configuration by trying the remote desktop connection again. If you still can't connect, restart the affected computer.

  7. If you still can't connect, check the status of the RDP self-signed certificate.

Check the status of the RDP self-signed certificate

  1. If you still can't connect, open the Certificates MMC snap-in. When you are prompted to select the certificate store to manage, select Computer account, and then select the affected computer.
  2. In the Certificates folder under Remote Desktop, delete the RDP self-signed certificate.
  3. On the affected computer, restart the Remote Desktop Services service.
  4. Refresh the Certificates snap-in.
  5. If the RDP self-signed certificate has not been recreated, check the permissions of the MachineKeys folder.

Check the permissions of the MachineKeys folder

Remove Microsoft Remote Desktop Connection Mac Download

  1. On the affected computer, open Explorer, and then navigate to C:ProgramDataMicrosoftCryptoRSA.
  2. Right-click MachineKeys, select Properties, select Security, and then select Advanced.
  3. Make sure that the following permissions are configured:
    • BuiltinAdministrators: Full control
    • Everyone: Read, Write

Check the RDP listener port

On both the local (client) computer and the remote (target) computer, the RDP listener should be listening on port 3389. No other applications should be using this port.

Important

Follow this section's instructions carefully. Serious problems can occur if the registry is modified incorrectly. Before you starty modifying the registry, back up the registry so you can restore it in case something goes wrong.

To check or change the RDP port, use the Registry Editor:

  1. Go to the Start menu, select Run, then enter regedt32 into the text box that appears.
    • To connect to a remote computer, select File, and then select Connect Network Registry.
    • In the Select Computer dialog box, enter the name of the remote computer, select Check Names, and then select OK.
  2. Open the registry and navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerWinStations<listener>.
  3. If PortNumber has a value other than 3389, change it to 3389.

    Important

    You can operate Remote Desktop services using another port. However, we don't recommend you do this. This article doesn't cover how to troubleshoot that type of configuration.

  4. After you change the port number, restart the Remote Desktop Services service.

Check that another application isn't trying to use the same port

Remove Microsoft Remote Desktop Connection Mac Pro

For this procedure, use a PowerShell instance that has administrative permissions. For a local computer, you can also use a command prompt that has administrative permissions. However, this procedure uses PowerShell because the same cmdlets work locally and remotely.

  1. Open a PowerShell window. To connect to a remote computer, enter Enter-PSSession -ComputerName <computer name>.

  2. Enter the following command:

  3. Look for an entry for TCP port 3389 (or the assigned RDP port) with a status of Listening.

    Note

    The process identifier (PID) for the process or service using that port appears under the PID column.

  4. To determine which application is using port 3389 (or the assigned RDP port), enter the following command:

  5. Look for an entry for the PID number that is associated with the port (from the netstat output). The services or processes that are associated with that PID appear on the right column.

  6. If an application or service other than Remote Desktop Services (TermServ.exe) is using the port, you can resolve the conflict by using one of the following methods:

    • Configure the other application or service to use a different port (recommended).
    • Uninstall the other application or service.
    • Configure RDP to use a different port, and then restart the Remote Desktop Services service (not recommended).

Check whether a firewall is blocking the RDP port

Use the psping tool to test whether you can reach the affected computer by using port 3389.

  1. Go to a different computer that isn't affected and download psping from https://live.sysinternals.com/psping.exe.

  2. Open a command prompt window as an administrator, change to the directory in which you installed psping, and then enter the following command:

  3. Check the output of the psping command for results such as the following:

    • Connecting to <computer IP>: The remote computer is reachable.
    • (0% loss): All attempts to connect succeeded.
    • The remote computer refused the network connection: The remote computer is not reachable.
    • (100% loss): All attempts to connect failed.
  4. Run psping on multiple computers to test their ability to connect to the affected computer.

  5. Note whether the affected computer blocks connections from all other computers, some other computers, or only one other computer.

  6. Recommended next steps:

    • Engage your network administrators to verify that the network allows RDP traffic to the affected computer.
    • Investigate the configurations of any firewalls between the source computers and the affected computer (including Windows Firewall on the affected computer) to determine whether a firewall is blocking the RDP port.