FSMO roles should be separated across DCs in the domain?

[PiqueABoo]

Seconded.. and don't forget DHCP or any boxes with static DNS server entries that might be pointing to the original DC.

[HodgeHi]

Ok great thanks. I have backed up the dhcp db and will restore it onto the second server just before it goes down. This will be the first time i have moved a dhcp from one machine to the other.

 

The DNS entries on the main server as far as i know are all dynamic. How can i tell if they are manually entered ones?

 

The entries are also a bit messed up since there are entries on there from the previous domain structure (before i got here) which is one of the reasons why i am rebuilding it. Plus there are a lot of things that have been implemented and i'm not sure whether we need these.

A fresh start is what i feel is needed.

[HodgeHi]

Hello all,

 

I have been looking at restoring active directory through a non-authoratitive point and have run into a problem. I am testing this through 2 VMs in parallels on a MBP. I have backed up the system state and then down the primary DC after i have transferred the roles (i have not made the second DC a GC though) and re-installed Server 2003.

 

Now i did not re-add the server to the domain as i read that it can be done on a stand-alone server on the technet site.

 

So i continued to enter the directory restore mode and restored the system state, but when it asked to restart the machine all that happens is when the server should get to the server loading screen it just restarts.

 

I have caught a glimpse of a blue screen once but it was so fast that i never got to read it.

 

What could be the problem?

[sidewinder]

Multiple GCs on one physical local network will cause large amounts of unnescessary traffic as the GCs keep synchronizing. You may need more GCs in a large org with many exchange servers. One GC for every 4 Exchange servers.

 

I know this was an old discussion but Ive just been reading on Technet about GC's and came across this link

 

http://technet2.microsoft.com/WindowsServer/en/library/0e4d2466-68e8-40d8-8c72-099f8bc259ff1033.mspx?mfr=true

 

The first paragraph says:

"Global catalog placement requires planning except if you have a single-domain forest. In a single-domain forest, configure all domain controllers as global catalog servers. Because every domain controller stores the only domain directory partition in the forest, configuring each domain controller as a global catalog server does not require any additional disk space usage, CPU usage, or replication traffic. In a single-domain forest, all domain controllers act as "virtual global catalog servers" in that they can all respond to any authentication or service request. This special condition for single-domain forests is by design"

 

So it seems multiple GC's shouldnt create any additional traffic

Anyone else heard this advice before?