Windows Server
We have a big issue with our domain.
Last weekend we had a building power down at our main site which is also our primary DC.
To get certain services running we had to fail certain servers over to DR. Our Domain controllers were two of those servers.
PDC
London
Kent
DRDC
Surrey
Hampshire
After the power down we failed back our PDC’s. Initially there were some issues but our services came back to normal after a few reboots.
Today we’ve gone in to look at DNS and the trusts and it seems some domain controllers aren’t communicating with each other. Some are seeing different servers as the PDC.
ASKER
I have asked the client.
Is this something to do with FSMO roles?
Is this something to do with FSMO roles?
What was done with FSMO roles?
It will help to know what happened. Did DCs get turned on at the DC site? Were backups/replicas restored at DR? Were FSMO roles seized?
Note: Don't ever seize FSMO roles unless the original DC is permanently unavailable. If you seize a FSMO role, the original DC that had the role can NEVER be brought back online safely. It needs to be wiped out and forcibly deleted from the domain.
It will help to know what happened. Did DCs get turned on at the DC site? Were backups/replicas restored at DR? Were FSMO roles seized?
Note: Don't ever seize FSMO roles unless the original DC is permanently unavailable. If you seize a FSMO role, the original DC that had the role can NEVER be brought back online safely. It needs to be wiped out and forcibly deleted from the domain.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
how do you have this setup?
there are certain things like application servers that, when being replicated to DR, can failover and be usable
domain controllers don't quite function that way
knowing how things are setup will help
do these domain controllers replicate with each other between the sites?