FSMO seized - failed server online - what now?
Posted on 2006-06-20
I have a very simple network with about 10 workstations (windows xp) and 2 domain controllers (windows 2000).
Roughly 3 weeks ago the primary domain controller was having serious stability issues and I was unable to get it to boot for a successfull transfer of FSMO roles. As users were unable to login I seized the FSMO roles on secondary DC and operations resumed as normal.
Now I have the unstable server back online how do I inform this server that it is no longer pdc master. When trying to access the Operations Masters tab through active directory I am unable to use the "change roles" as it is unable to contact the current FSMO. Im assuming it still thinks it is the current FSMO but it has been stripped away.
Is there a way to manually fix it through NTDSutil?
Do I have to reinstall windows again?
The unstable server is also the Exchange server (go figure?) and the re-installation of this one would be tricky?
Would I be better off requesting a server upgrade (it is a bit underpowered for an exchange server) and migrate the current exchange 2000 to a windows 2003/exchange 2003 enviornment?