Windows 10: Windows Server TSS repurposed as a DC

A Terminal Services Server at the main office has been repurposed as a Domain Controller at a branch office.I removed the TSS service and installed DHCP, DNS, and AD, and all is well, but I can't manage it via Remote Desktop Connection.How do I fix that?

:)

 

Trust Relationship between Server and DC Fails

I am having problems establishing a trust relationship between a server and a DC.

Here are the things I have tried(that I can rememeber):

• Unjoining and rejoining the Domain
• Running: netdom reset 'computername' /domain:abc /userO:xxx /passwordO:*
• Running Test-ComputerSecureChannel -Repair -Verbose
• Resetting the password of the computer from the DC
• After all of these, Test-ComputerSecureChannel still returns false

Many of the error messages I get revolve around 'Access is Denied'. However, all of these commands are run from elevated PowerShell, as a domain administrator, with the netdom command run on both the local machine and the DC. The local machine is running
Server 2012 and the DC is Server 2016. Any thoughts would be appreciated.

 

Server 2012

IF you want to try seizing the FSMO roles to see if it will help, here is a quick guide (this should be done on the DC you want to keep):

https://blogs.technet.microsoft.com...ation-master-roles-in-windows-server-2012-r2/

Knowing that this is a DC now I'm really convinced that something is wrong with the AD account for this particular server. It's possible that the promotion to a DC didn't work correctly leaving you with a sort of broken DC.

A reboot is always worth a shot; has that been tried Ahhzz? If it has, then the next step would be to demote this DC and rejoin it to the domain. Once rejoined you can run DCPromo again. Microsoft best practice is to have at least 2 DCs for redundancy.

 

Server 2012

Also don't forget to reset the account in AD Users and Computers to avoid any SID issues.