Rdp For Mac Terminal Server



LogMeIn for Mac is a the best remote desktop app for Mac users of all abilities. RDP vs Terminal Services. Having the ability to access your data and applications wherever you are is one feature that has helped not only the travel veteran but even the common PC user. With remote connectivity, there are two known terms; terminal services and RDP or Remote Desktop Protocol.

You can use a Remote Desktop Protocol client to connect to a Windows Terminal Server or a Windows PC with Remote Access enabled.

The recommended client software is Microsoft Remote Desktop client. You can find it on App Store, or following the dedicated icon on Mac Self-Service which will forward you to the appropriate App Store page.

CERNTS - the CERN Public Terminal Server Cluster

At CERN, the Remote Desktop Services provide a public Terminal Cluster called CERNTS.CERN.CH, where many standard applications are available. To connect, you need to specify the CERN credentials of your primary account - please remember to specify the domain 'CERN'.

Rdp For Mac Terminal Server Ip

If your credentials are rejected, please check that your account is registered for this service at https://account.cern.ch/account/Services/MyServices.aspx.

After you installed the Microsoft Remote Desktop client simply launch it.
​Click on the 'New' icon on top left and fill in informations as on screenshot.

Storing your CERN password within the client configuration is NOT recommended.
​Let this fields empty and simply fill in the logon screen when displayed.

Rdp For Mac Terminal Server Settings

Once configured, simply double click on 'CERNTS' entry and connect using your CERN credentials.

-->ServerRdp For Mac Terminal Server

This article describes how to remove Terminal Server licenses from a Remote Desktop Protocol (RDP) client.

Original product version: Windows 10 - all editions, Windows Server 2012 R2
Original KB number: 187614

Summary

If an unlicensed client connects to a Terminal Server for the first time, the Terminal Server issues the client a temporary Terminal Server Client Access License (CAL) token. After the user has logged into the session, the Terminal Server instructs the License Server to mark the issued temporary Terminal Server CAL token as being validated. The next time the client connects, an attempt is made to upgrade the validated temporary Terminal Server CAL token to a full Terminal Server CAL token. If no license tokens are available, the temporary Terminal Server CAL token will continue to function for 90 days. The license is stored in the client's registry.

32-bit RDP clients store their license under the key HKEY_LOCAL_MACHINESoftwareMicrosoftMSLicensing.

Important

Rdp

This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, see How to back up and restore the registry in Windows.

Clean RDP client's license cache

To clean the client's license cache, just delete this key and its subkeys. The next time the client connects to the server, it will obtain another license.

Mac

For 16-bit RDP clients, run regedit /v. Then delete the keys under SoftwareMicrosoftMSLicensing to clean the client's license cache. You can also delete the BIN files from WindowsSystemRegdata.

The RDP client for Macintosh stores the license in a file on the local computer in the folder hierarchy under /users/Shared/Microsoft/RDC Crucial Server Information/. To clean the Macintosh client's license cache, delete the contents of this folder. The client will try to obtain a new license from the server the next time that it connects.

If you delete the HKEY_LOCAL_MACHINESoftwareMicrosoftMSLicensing subkey on a client that is running Windows Vista or a later version, later attempts to connect to a Terminal Server may fail. Also, you receive the following error message:

An Error occurred in the Licensing Protocol

Rdp For Mac Terminal Server Configuration

To resolve this problem, right-click the Remote Desktop Connection shortcut, and then click Run as Administrator. By default, the remote desktop connection runs as a user with the lowest user permissions. By default, a restricted user does not have permission to write registry entries to HKEY_LOCAL_MACHINE. Therefore, attempts to rewrite the MSLicensing key fail. Starting Remote Desktop Connection with administrative credentials provides the permissions that are necessary to write the needed registry keys.

Rdp App For Mac

Did this fix the problem

Rdp Server Settings

Check whether the problem is fixed. If the problem is fixed, you are finished with this section. If the problem is not fixed, you can contact support.