These are the "everyday" boxes that users see regularly the domain controllers are best left rubber-stamping user credentials across the domain. This is the model that Windows would like you have, and you really, really, should have at least two domain controllers for each domain.īuy the beefer boxes for those services that are used most - databases, email, file & print, etc. Heck, if at all possible, get a cheap yet server-grade box, probably a department-level box, and put your DC services on that then get a twin of that box, and put DC services on that as well. If you can afford it, put the domain controller on a separate box. Doing "all in one" boxes is a function of evil budgets set forth by keepers-of-the-pursestrings that don't understand the price they'll pay. But there are performance issues, security issues, and even the potential for incompatibilities between services. If you have very few users (say under 25-50), or you are squeezed by budget constraints and you need to make this an "all in one" box, you could get away with doing so. But there's a downside to this, a price to pay in the form of degraded functionality on that box. I guess the question is: do you want to? Sure, you can turn your domain controller into a file and print server, or a SQL Server box, or any number of other functions. "You can even cut a tin can with it, but you wouldn't want to!" - Mr. Is it OK to use servers filling other roles as domain controllers?.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |