GUID

[Guest]

Hi guys,

I have a quick question here. I did an active directory replication monitor
on my network and I got the following result.

he server TAFISDC001 knows about the following FSMO roles:
--------------------------------------------------------------------------
Schema FSMO: Servers\F:3a380e4f-7418-42d2-9d71-b03108a1c907
Domain Naming FSMO: Servers\F:3a380e4f-7418-42d2-9d71-b03108a1c907
Infrastructure FSMO: Datacenter\servername
Primary Domain Controller FSMO: Datacenter\servername
RID Pool FSMO: Datacenter\servername

Notice the Schema FSMO and Domain Naming FSMO server names are different
from the remaining three. Any idea what
"Servers\F:3a380e4f-7418-42d2-9d71-b03108a1c907" refers to?

Would it be safe to transfer/seize these two roles to a live DC?

Thank you in advance for ur attention and input.

 

[Paul Williams [MVP]]

Try transferring the roles using the GUI or NETDOM. Don't seize them.

If that fails, and the server that they were on is offline, get it back
online. If you can't get it back online, seize the roles and follow the
steps in kb216498 to remove the dead DC.

 

[chriss3 [MVP]]

Seems like you had leave the Schema and Domain Naming Master FSMOs on DCs
that are dead/removed from the directory, You should seize the roles to
another DC. The seize process is designed that way, it try to find the roles
and go with a move first before it try a seizure.

 

[chriss3 [MVP]]

Doing seizure will first try to move the role, if the transfer fails, the
role will be seized

 

[Paul Williams [MVP]]

Yes, valid point. However, I recommended transferring the role first for a
reason. If that failed the OP should then see why it failed and try and
resolve this issue first. There could be a number of mundane reasons why
this fails, and seizing the roles because of that is too drastic in my
opinion. If the server is offline, he should try getting it back online.
If you can DR the server you should. Seizing and cleaning up should be a
last resort unless you have dedicated DCs - which most people do not.

If the box is dead then all of this is irrelevant, and the roles need to be
seized and kb216498 followed. However, it is best to approach things with
an element of caution in my opinion.

 

[Guest]

Thanks for your attention

In DNS server, I have discovered the GUID is actually "servername"..
but in a different location which is Servers\servername [ instead of
Datacentre\servername]. is that the reason we dun have servers in AD sites
and services and the DNS server is not able to translate the GUID back to
hostname?

If I proceed to transfer the roles using ntdsutil or GUI it said RPC server
is not available. I had transferred PDC emulator, infrastructure and RID
without a problem.

Please help..