New Domain Controller
Posted on 2010-11-27
Ok, I had a domain Controller fail. The Hard drive died, and the server was so old. So no raid was configured. We have a VPN connection between 3 locations, one other location has a DC as well. So I was able to join the new server to the domain and then seize the roles from the old server to the new one. I ran metadata cleanup, and removed the old server from all locations. I went onto my Exchange server pointed it to the new DC, changed the RUS as well to the new DC.
Everything is sooooooo slow, I rebooted my Exchange Server half hour ago and it is still booting back up. It is stuck at applying computer settings. The new server is dual processor, 8 gigs of RAM. You would think it was a p4!!!! What ever the problem is seems to be slowing down the server as well, I clicked on start and run. It took over 30 seconds to come up.
The only thing I'm not sure about is that under sites and services, the new server also holding the fsmo roles, and global catalog. has a connection to the other dc in the second location for replication. I am not sure if that is right, I dont think so. I could be wrong, I tried to delete it but it recreated itself again. The connection is called Automatically generated.
I ran netdiag, and DCdiag with no errors. DNS looks fine too. I am not sure what the problem is, everything looks good. This is not the first time I have done this, and everything went smoothly. I have never had an issue like this before, with a replaced failed DC.