'The system cannot determine if the license server is member of TSLS Group on Active Directory Domain Servers (AD DS) because AD DS cannot be contacted'. One error that has also manifested recently though it doesn't seem to stop authentications is under the RD Licensing Manager is shows the following under 'Review': This access denied message only appears if the secure channel is pointing to the new 2016 domain controller. This is how the Access Denied message looks: R2 Terminal Servers also do not show failures corresponding to the Access Denied message in the System, Application or Security log. I've been working with the DC admins but they have not found errors on the new domain controller corresponding to the Access Denied messages that occur on the 2012 R2 Terminal Servers (when the secure channel is pointing to our new WS 2016 DC).

To specify the domain controller you want to be on (in our case we want to switch to back to a 2012 R2 domain controller), the command is: What we do know is that if we decide to start upgrading to new 2016 Terminal Servers we will have to purchase new 2016 RDS Cals (not sure if we are budgeted for that.)įor those interested, you can find out the domain controller you are using by running the following elevated PowerShell command (this assumes the command is run remotely as you might be locked out due to the RDP access denied error): We are having problems finding documentation on this. Is the problem that Windows 2016 Domain Controllers are not compatible with 2012 R2 Remote Desktop Services servers? Is there a misconfiguration with the new 2016 domain controllers or can an adjustment be made with the 2012 Terminal Servers? We can workaround the problem by sending an command telling the terminal server to use one of the older 2012 R2 domainĬontrollers instead. Generally the 'Access Denied' error occurs when a terminal servers starts to use one of the newly added 2016 domain controllers.

Since then our users are getting intermittent 'Access Denied' errors when they try to RDP to these terminal servers. So we have a few 2012 R2 Terminal Servers at my company that were working fine until we started the process of replacing our Domain Controllers with new Windows 2016 Servers.

Windows terminal server 2012