windows server 2016 remote desktop services user vs. device

#WINDOWS SERVER 2016 REMOTE DESKTOP SERVICES USER VS. DEVICE PASSWORD#
#WINDOWS SERVER 2016 REMOTE DESKTOP SERVICES USER VS. DEVICE PC#
#WINDOWS SERVER 2016 REMOTE DESKTOP SERVICES USER VS. DEVICE LICENSE#

Set client connection encryption level: Enabled.

Require user authentication for remote connections by using Network Level Authentication: Enabled.

Require secure RPC communication: Enabled.

#WINDOWS SERVER 2016 REMOTE DESKTOP SERVICES USER VS. DEVICE PASSWORD#

Always prompt for password upon connection: Enabled.

Windows Components/Remote Desktop Services/Remote Desktop Session Host/Security.

Allow users to connect remotely by using Remote Desktop Services: Enabled.

Windows Components/Remote Desktop Services/Remote Desktop Session Host/Connections.

Remote Host Allows delegation of non-exportable credentials: Enabled.

Windows Defender Firewall: Defined Inbound Port Exceptions: 3389:TCP::enabled:Remote Desktop Connections.

Windows Defender Firewall: Allow Local Port Exceptions: Enabled.

Network/Network Connections/Windows Defender Firewall/Domain Profile:.

Computer Settings > Policies > Administrative Templates.

What I think are all the relevant settings from gpresult follow:

#WINDOWS SERVER 2016 REMOTE DESKTOP SERVICES USER VS. DEVICE PC#

The domain-joined target PC (RDP server) has many GPO's applied. GPO Settings and Event Logs, on the RDP Server Is there a way I can enable non-Windows clients to connect to domain-joined Windows PCs by remote desktop, without making NTLM authentication exceptions for each target PC? Kerberos doesn't seem available for the Mac RDP Client, is there another authentication mechanism that is supported? If I try and remote into the same PC from a Windows PC, using the native Windows Remote Desktop client, I don't get this error, and can connect fine. If this keeps happening, contact your network administrator

When I try and start a Remote Desktop session from a Mac to a Windows domain-joined PC, using Microsoft's latest Remote Desktop Client (v10.3.9 currently), I'll often receive the error in the following screenshot. You can use the Remote Desktop Licensing Manager to track and generate reports on RDS Per User CALs.This has been bugging me for quite a while (and no amount of internet searching has amounted to a decent solution), so I'm hoping someone can offer some sage advice.

#WINDOWS SERVER 2016 REMOTE DESKTOP SERVICES USER VS. DEVICE LICENSE#

To ensure you are in compliance with the Remote Destkop Services license terms, track the number of RDS Per User CALs used in your organization and be sure to have a enough Per User CALs installed on the license server for all of your users. 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. The license server issues licenses from the available CAL pool or the Over-Used CAL pool. 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 second time that device connects, as long as the license server is activated and there are available CALs, the license server issues a permanent RDS Per Device CAL. When you use the Per Device model, a temporary license is issued the first time a device connects to the RD Session Host.

The following table outlines the differences between the two types of CALs:ĬALs are physically assigned to each device.ĬALs are assigned to a user in Active Directory.ĬALs can be tracked regardless of Active Directory membership.ĬALs cannot be tracked within a workgroup.ĬALs can be overallocated (in breach of the Remote Desktop licensing agreement).

Windows server 2016 remote desktop services user vs. device