Microsoft Remote Desktop 10 For Mac License Issue Is Preventing Windows 7; Microsoft Remote Desktop 10 For Mac License Issue Is Preventing 10; Timbuktu is a discontinued remote control software product originally developed by WOS Datasystems. Remote control software allows a user to control another computer across the local network or the Internet, viewing its screen and using its keyboard. How to Remote Desktop Windows 10 Home? The following steps will allow remote access to your Windows 10 Home computer remotely though the network. Download RDP Wrapper Library from here. The specific filename is RDPWInst-v1.6.2.msi for automatic installation. Or you can also download the zip file RDPWrap-v1.6.2.zip for manual installation. The microsoft remote desktop client for the mac works perfectly. Absolutely no scaling issue at all everything looks great on a 13' macbook with a retina display. Good job Satya we know you like supporting other platforms better than your own.

-->

Applies to: Windows Server (Semi-Annual Channel), Windows Server 2019, Windows Server 2016

Each user and device that connects to a Remote Desktop Session host needs a client access license (CAL). You use RD Licensing to install, issue, and track RDS CALs.

When a user or a device connects to an RD Session Host server, the RD Session Host server determines if an RDS CAL is needed. The RD Session Host server then requests an RDS CAL from the Remote Desktop license server. If an appropriate RDS CAL is available from a license server, the RDS CAL is issued to the client, and the client is able to connect to the RD Session Host server and from there to the desktop or apps they're trying to use.

There is a licensing grace period of 180 Days during which no license server is required. Once the grace period ends, clients must have a valid RDS CAL issued by a license server before they can log on to an RD Session Host server.

Use the following information to learn about how client access licensing works in Remote Desktop Services and to deploy and manage your licenses:

  • License your RDS deployment with client access licenses (CALs)

Understanding the RDS CAL model

Microsoft Remote Desktop 10 For Mac License Issue Is Preventing

There are two types of RDS CALs:

  • RDS Per Device CALs
  • RDS Per User CALs

The following table outlines the differences between the two types of CALs:

Per DevicePer User
RDS CALs are physically assigned to each device.RDS CALs are assigned to a user in Active Directory.
RDS CALs are tracked by the license server.RDS CALs are tracked by the license server.
RDS CALs can be tracked regardless of Active Directory membership.RDS CALs cannot be tracked within a workgroup.
You can revoke up to 20% of RDS CALs.You cannot revoke any RDS CALs.
Temporary RDS CALs are valid for 52–89 days.Temporary RDS CALs are not available.
RDS CALs cannot be overallocated.RDS CALs can be overallocated (in breach of the Remote Desktop licensing agreement).

When you use the Per Device model, a temporary license is issued the first time a device connects to the RD Session Host. The second time that device connects, as long as the license server is activated and there are available RDS CALs, the license server issues a permanent RDS Per Device CAL.

When you use the Per User model, licensing is not enforced and each user is granted a license to connect to an RD Session Host from any number of devices. The license server issues licenses from the available RDS CAL pool or the Over-Used RDS CAL pool. It's your responsibility to ensure that all of your users have a valid license and zero Over-Used CALs—otherwise, you're in violation of the Remote Desktop Services license terms.

Microsoft Remote Desktop 10 For Mac License Issue Is Preventing

An example of where one would use the Per Device model would be in an environment where there are two or more shifts using the same computers to access the RD Session Host(s). The Per User model would be best for environments where users have their own dedicated Windows device to access the RD Session Host(s).

To ensure you are in compliance with the Remote Desktop Services license terms, track the number of RDS Per User CALs used in your organization and be sure to have enough RDS Per User CALs installed on the license server for all of your users.

You can use the Remote Desktop Licensing Manager to track and generate reports on RDS Per User CALs.

RDS CAL version compatibility

The RDS CAL for your users or devices must be compatible with the version of Windows Server that the user or device is connecting to. You can't use RDS CALs for earlier versions to access later versions of Windows Server, but you can use later versions of RDS CALs to access earlier versions of Windows Server. For example, an RDS 2016 CAL or higher is required to connect to a Windows Server 2016 RD Session Host, while an RDS 2012 CAL or higher is required to connect to a Windows Server 2012 R2 RD Session Host.

The following table shows which RDS CAL and RD Session Host versions are compatible with each other.

RDS 2008 R2 and earlier CALRDS 2012 CALRDS 2016 CALRDS 2019 CAL
2008, 2008 R2 session hostYesYesYesYes
2012 session hostNoYesYesYes
2012 R2 session hostNoYesYesYes
2016 session hostNoNoYesYes
2019 session hostNoNoNoYes

You must install your RDS CAL on a compatible RD license server. Any RDS license server can host licenses from all previous versions of Remote Desktop Services and the current version of Remote Desktop Services. For example, a Windows Server 2016 RDS license server can host licenses from all previous versions of RDS, while a Windows Server 2012 R2 RDS license server can only host licenses up to Windows Server 2012 R2.

The following table shows which RDS CAL and license server versions are compatible with each other.

RDS 2008 R2 and earlier CALRDS 2012 CALRDS 2016 CALRDS 2019 CAL
2008, 2008 R2 license serverYesNoNoNo
2012 license serverYesYesNoNo
2012 R2 license serverYesYesNoNo
2016 license serverYesYesYesNo
2019 license serverYesYesYesYes
Microsoft Remote Desktop 10 For Mac License Issue Is Preventing

Microsoft RDP Client Error on Mac

When connecting using Microsoft Remote Desktop from a Mac to a remote PC, you might experience the following error:

There are no Client Access Licenses available for the target remote computer (code LicenseNoLicense(258))

Most IT departments knows how to fix this; for Windows. This involves deleting registry keys, but you don't have them on a Mac. Instead, you need to clear out some cache files on the file system by performing the following steps:

Microsoft

Microsoft Remote Desktop 10 For Mac License Issue Is Preventing Mac

License
  1. Open Terminal
  2. Enter (or copy and paste this) cd ~/Library/Containers/com.microsoft.rdc.mac/Data/Library/Application Support/Microsoft Remote Desktop/
  3. List the directory using the li command. You should now see all folders.
  4. Delete all folders except for logs and printerconfig. Do this by copying each folder name (in a GUID format) and using the following delete command:
    rm -r -f [directoryname]
    For example:
    rm -r -f {b58e9e06-2ea5-4ed6-944c-d52dd8cf58fb}

Microsoft Remote Desktop 10 For Mac License Issue Is Preventing Windows 10

Hope this helps others with the same issue!