Link to home
Start Free TrialLog in
Avatar of sseifer
sseiferFlag for United States of America

asked on

Best Practice for FSMO Roles, DNS, DHCP

More or less looking for advice/opinions.

We have a server that we pretty much can't rely on as it BSODs with "registry errors" upon any login attempt at the console or through RDP.  Other than that it functions, but that just isn't sitting right.  This server happens to have all 5 FSMO roles, DHCP for our main office and is our Primary DNS.  Which are all still functioning and manageable through snap-ins, RSET, etc.

It's a 2008 R2 box and we are just a single domain/forest.  So I know I'm good to transfer all FSMO roles to another 2008 R2 DC.  But what is everyone thoughts for DHCP and DNS?  This just seems like an example of why you wouldn't want all this stuff on one box when you have the option of spreading them out.  And any trouble with having any of these roles virtualized?  Thanks for the thoughts.

-Scott
ASKER CERTIFIED SOLUTION
Avatar of Mike Kline
Mike Kline
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of sseifer

ASKER

Thanks all.  Exactly what I was looking for.