I have an Exchange 2010 server set up on a Windows 2008 R2 server, that is also set up as a domain controller, but the Exchange side will not recognize itself as an Domain Controller or Global Catalog server.
Now I am aware that it is unsupported, and generally a bad idea, to have Exchange installed on a DC. I am not the one who set this up, and changing this set up is currently not an option. I do know that they can work when set up this way though, and am lost as to what is preventing it from working. I am hoping I am missing something simple.
To lay out the network, There are two servers:
A Windows 2003 SBS premise server that was the original DC and currently holds the FSMO roles. This server also used to be their Exchange server before the 2010 server was added to the network.
The Windows 2008 R2 server is at a separate location connected with a point-to-point private line. It was added as a second DC with GC and runs Exchange 2010.
These servers are on the same local subnet across the private line.
The 2003 Premise server has begun having some stability issues, and it quickly became clear that the Exchange server was unable to function when it was down. Looking deeper into the problem, I found that Exchange was only seeing the Premise server for Domain Controllers and Global Catalog under Server Configuration properties.
I manually checked all DNS settings and do not see anything missing for the Exchange server in the records. I found everything I expected to, and there were no records for the 2003 server that were not there for the Exchange server.
I am able to move the FSMO roles to the Exchange server successfully. This doesn't change anything on the exchange side. An interesting error that occurs, about two days after moving the FSMO roles the 2003 SBS server shuts down. SBCore detects a second 2003 SBS domain controller in the network and shuts the server down due to EULA conflicts. I have tested and confirmed that moving the FSMO roles cause this. Not sure if it is related, but is definitely odd to me.
I've tried setting the "Configuration Domain Controller" manually to point to the Exchange server, which sticks but does not help anything. I've tried using the Exchange Management Shell to manually set Static Domain Controllers
and Preferred Domain Controllers
Both seem to work if I do a Get-ADServerSettings, but do not change in the EMC. If I reboot the server, everything is cleared and back showing just the 2003 DC once it is back up.
It is quite possible that something was not configured correctly when this DC was added to the Windows 2003 SBS domain, but I do not know where else to look. I am hoping the fact that it is an SBS domain doesn't make impossible. I would very much appreciate anything that may point me in the right direction.