Q: Are there extended the benefits of using a domain controller in a small office (14-20 users) on its establishment as a group?
We currently have a Windows 2K server (Small Business Server) set up as a domain controller, but all the PCs are set up in a sort of working environment you can not log onto the domain. We do not have a domain name, Do not perform an Internet service, not a mail server and no users are allowed internet access.
What are the pros and cons of using a domain controller?
What are the pros and cons of using a group on a domain logon?
Best Answer: 1. C
2. D
3. B
4. B
5. B
6. ABCE
7. A
8. D
9. C
10. B
11. B
Re:are you familure with another server environment other then windows? I've learned that linux + samba == good times.
Re:guy I would purchase these books mastering windows 2000 server or mastering windows server 2003 both are by Mark Minasi.
Re:Active Directory (Domain++). Microsoft says you must use it. Err, should. Resistance is futile. Do things The Microsoft Way or it might not always work.
Re:The question to ask is: Do you have business critical documents scattered across various user PC's?
When I first walked into the job, yes. They had everything on their own PC's. I've since changed it to all reside on the server that gets backed up nightly to tape.
I'm not so familiar with Windows Server environments. I'm willing to learn though. And if they are willing to pay me to learn it makes it that much more attractive…
Re:I'd say lots depends on if you want to learn how to administer a domain. If you don't know what you're doing your going to have a lot of headaches.
Re:Originally posted by: guy
I'd go to the domain model. It's nice to have a centralized logon and resource management system. Better: right now it's probably rigged so that everyone saves important business info on their local machines that aren't backed up regularly. If you move to AD, you can set it so that everyone's My Documents folder, application data folder, and desktop point to the server. Makes it fairly simple to insure that important data is stored on the server where it can be backed up every night.
Also makes it easier to add a user to existing resources (assuming you don't have network usage open to "full access for anyone who plugs into an ethernet jack"), or make a new printer avalable, or whatever.
I would agree. It's alot easier to control who has access to what in a domain model.
The question to ask is: Do you have business critical documents scattered across various user PC's?
If you answer yes, then you would find the domain model easier to manage for all the reasons that guy mentioned. Plus many more too numerous to mention.
Re:I'd go to the domain model. It's nice to have a centralized logon and resource management system. Better: right now it's probably rigged so that everyone saves important business info on their local machines that aren't backed up regularly. If you move to AD, you can set it so that everyone's My Documents folder, application data folder, and desktop point to the server. Makes it fairly simple to insure that important data is stored on the server where it can be backed up every night.
Also makes it easier to add a user to existing resources (assuming you don't have network usage open to "full access for anyone who plugs into an ethernet jack"), or make a new printer avalable, or whatever.
Re:Pro – Enhanced security, you get to control a lot more…
Con – Have to know what you're doing, may be more difficult for you to administer at times…
With only 14-20 computers I'd say just stick with the workgroup network that you have now…you don't really need to setup a domain for the size of your network and what you use it for…
just my $0.02
0 Comments.