Archived from groups: microsoft.public.win2000.active_directory (More info?)
I've got a dead DC which is the FSMO, still 'running' but I can't ping it
nor access it in any way. I've got two other DCs and have, of course been
getting replication errors as neither can communicate with the 'dead'
server. I've set both the other DCs to have Global Catalogs (rebooted,
proper records show up in DNS). To add to the mix I'm also getting 5719 -
no dc for domain - from Netlogon (this appears to be intermittent, no logon
problems noticed).
So the plan is to seize the FSMO roles using Ntdsutil but there's a couple
of questions:
1. in KB255204 it says do not put the Infrastructure role on a DC which has
the GC; however the TechNet 'Managing Domain Controllers document says that
the Infra role is 'insignificant' if all the DCs are GC servers because 'GCs
replicate the updated info regardless of the domain to which they belong',
it also says 'if the forest has only 1 domain the dc that hosts the Infra
role is not needed'
I have only 1 domain so does the above mean I can seize the Infra role with
impunity or does it mean I don't need an Infra role at all unless I'm adding
more domains? What will be the impact of putting the I role onto a GC
server in my scenario?
2. once the seizure is done do I use 'ntdsutil /metadata cleanup' to get
rid of info in the AD which references the dead server? If not how do I
get rid of the info or is it just a matter of turning the 'dead' machine off
and going away?
3. once the seizure is done and the old server out of the way will my
replication and netlogon msgs disappear?
sorry if I sound a bit thick but I don't want to spend my weeked creating a
new AD!
thanks for any help
I've got a dead DC which is the FSMO, still 'running' but I can't ping it
nor access it in any way. I've got two other DCs and have, of course been
getting replication errors as neither can communicate with the 'dead'
server. I've set both the other DCs to have Global Catalogs (rebooted,
proper records show up in DNS). To add to the mix I'm also getting 5719 -
no dc for domain - from Netlogon (this appears to be intermittent, no logon
problems noticed).
So the plan is to seize the FSMO roles using Ntdsutil but there's a couple
of questions:
1. in KB255204 it says do not put the Infrastructure role on a DC which has
the GC; however the TechNet 'Managing Domain Controllers document says that
the Infra role is 'insignificant' if all the DCs are GC servers because 'GCs
replicate the updated info regardless of the domain to which they belong',
it also says 'if the forest has only 1 domain the dc that hosts the Infra
role is not needed'
I have only 1 domain so does the above mean I can seize the Infra role with
impunity or does it mean I don't need an Infra role at all unless I'm adding
more domains? What will be the impact of putting the I role onto a GC
server in my scenario?
2. once the seizure is done do I use 'ntdsutil /metadata cleanup' to get
rid of info in the AD which references the dead server? If not how do I
get rid of the info or is it just a matter of turning the 'dead' machine off
and going away?
3. once the seizure is done and the old server out of the way will my
replication and netlogon msgs disappear?
sorry if I sound a bit thick but I don't want to spend my weeked creating a
new AD!
thanks for any help
Facebook
Twitter
Instagram