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 controllers 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |