I would move them all to one good server.
In enormous environments, it is sometimes recommended to spread them about.
But I can't really see any benefits to doing this.
Also i was wondering what each of these control. (When my pdc goes down
...no one can login to the network...is there something set wrong?)
Only the PDCe directly affects the users. The enterprise roles are very
infrequently used, and only then for very specific purposes. The RID role
is needed, and you will notice it's missing after a while; although only if
you make lots of new security principles. The Infrastructure role, in your
environment, is not used. It is only used in multi-domain environments
where not all DCs are GCs.
Unless you have mainly legacy clients, I suspect that your PDC problem is
actually a DNS problem. All internal clients should point to more than one
internal DNS server (usually DCs). You should also have a minimum of two
GCs and at least one per site. In your environment (single domain) I would
make all DCs GCs.
Here's a couple of article's I've written that may help out. These also
point to a bunch of MS KBs:
--
http://www.msresource.net/content/view/13/46/ (info on FSMO roles)
--
http://www.msresource.net/content/view/14/46/ (info on the GC/ IM issue)
--
http://www.msresource.net/content/view/28/47/ (move FSMO roles)
--
http://www.msresource.net/content/view/25/47/ (configure a GC)
--
Paul Williams
http://www.msresource.net/
http://forums.msresource.net/
I have a PDC that has all the roles in a single domain (rid,
pdc,infrastruc).
I fear my pdc is getting along in age and i want to transfer these rolse
off
it so if it dies...i dont have a hassel. Is it better to move them all to
one stable server? or can i spread them out to different servers. I have 4
dc's (3 win2k, 1 win2k3). Also i was wondering what each of these control.
(When my pdc goes down ...no one can login to the network...is there
something set wrong?)
Thanks