This forces you to re-enable RDP connections and select the users who are allowed to RDP to the server.
When joining a domain you're changing the server's identity and so Windows disables RDP connections (the radio buttons under the Remote Desktop section on the Remote tab of System Properties) due to the fact that the server has moved into a new neighborhood, if you will (a gated community) and is now potentially accessible by a new "universe" of users. I can't say with 100% certainty but I think this is normal.
Could this be some kind of domain-wide default policy that shuts down RDP on any domain clients? Or perhaps it has to do with the fact that Server B is virtual? What could be the reason for this? The domain is brandnew and I did not change any of the default settings. But the problem reoccurred just the same. I restored an older backup of Server B and switched off the firewall before adding the server to my domain. So far everything seemed to work smoothlyĪfter rebooting, I could not open an RDP connection to Server B anymore: I entered my domain admin credentials, was welcomed to the domain and asked to reboot the server. So I RDP'd into Server B and changed the system settings so that Server B is part of that domain. One Server A is a domain controller, Server B should simply be added to the domain controlled by Server A.
I have two dedicated with Windows 2008 R2 servers which I am using for Web hosting.