FSMO

  • Thread starter Thread starter Bill
  • Start date Start date
B

Bill

I want to replace the 2000 server I have with a new 2000 server then remove
the old server completely. This was a peer to peer network that has been
upgraded to a domain configuration. I think I have completed the FSMO
seize/transfer. How can I verify this and what other steps do I need to
complete before removing the old server.?
 
Bill said:
I want to replace the 2000 server I have with a new 2000 server then remove
the old server completely. This was a peer to peer network that has been
upgraded to a domain configuration. I think I have completed the FSMO
seize/transfer. How can I verify this and what other steps do I need to
complete before removing the old server.?

Insure that DNS, GC, and the five FSMO roles (in a single domain
forest there are exactly 5) are on the remaining DC.

(And don't use the SEIZE function as a general rule -- always
use TRANSFER unless you know the issues.)

Just turn off the other server for a bit -- check things out.

Bring it back online when satisfied and then DCPromo the
departing DC.
[/QUOTE]
 
In
Bill said:
I want to replace the 2000 server I have with a new 2000
server then remove the old server completely. This was a
peer to peer network that has been upgraded to a domain
configuration. I think I have completed the FSMO
seize/transfer. How can I verify this and what other
steps do I need to complete before removing the old
server.?

There are five FSMO roles, the easiest of these to identify are the RID,
Infrastructure, and PDC role, they are found in the AD Users & Computers
console.
There is also the domain naming master in the AD Domains & Trusts console
and the Schema Master in the Schema snap-in.
These roles will be transferred to another DC when you demote the DC that
holds them.
The only role that must be manually transferred is not one of the FSMO
roles, it is the Global Catalog, this must be manually added or removed in
the AD Site & Services console. This is also the only role that can be held
by more than one DC, but at least one DC in the forest must be a Global
Catalog, I recommend a Global Catalog at each location. Make sure the Global
Catalog has replicated before you demote a DC holding the Global Catalog,
this can be verified by running dcdiag /v /e.
 
Back
Top