Omar,
If you want to demote all of the WIN2000 Domain Controllers then all you
*should* need to do is to make sure that you have transferred any and all of
the five FSMO Roles to at least one of the WIN2003 Domain Controllers ( I
say 'at least one' because some people like to split them over two....the
two forest-wide roles on one and the three domain-wide roles on another ).
Make sure that at least one of the two WIN2003 Domain Controllers is also a
Global Catalog Server. Probably better if both of them are Global Catalog
Servers.
Make sure that at least one of the two WIN2003 Domain Controllers is also
running DNS. Probably better is both of them are running DNS. Well, this
point is open for debate. If you are running DNS on a Windows Server that
is part of your domain then it probably makes sense that you run Dynamic DNS
( or DDNS or AD-Integrated DNS ). It is possible that you could be running
DNS on a Linux or Unix box....You do not really mention anything about DNS.
Remember, Active Directory needs DNS. Specifically, it needs DNS that
supports both SRV records and Dynamic Updates. BIND 8.2.1 does both....so
you could conceivably be running DNS on a non-Windows platform.
Make sure that your DHCP Server ( again, you do not mention if this is
running on a Windows machine, a *nix machine or some Network Security device
( such as a Firewall ) reflects these changes so that the clients will have
the most up-to-date information included in the IP Lease 'stuff'. If you
are running DHCP on a Windows 2000 Domain Controller then simply 'swap' it
over to one of the WIN2003 Domain Controllers ( I *think* that DHCPExim will
help you with this....you can also do it manually ).
You do not need to worry about the FSMO Role of IM running on a Domain
Controller that is also a GC if there is only one Domain in the tree in the
forest. It is only once you have a second Domain or a second tree that you
need to worry about this. But, if -ALL- of the Domain Controllers in the
entire forest are also GCs then you do not need to worry about it either.
Remember, think about why this is a problem and then what I just suggested
will make sense.
--
Cary W. Shultz
Roanoke, VA 24012
Microsoft Active Directory MVP
http://www.activedirectory-win2000.com
http://www.grouppolicy-win2000.com