Advantages of a Domain Server?!

osaddictosaddict London, UK
edited October 2006 in Science & Tech
As some of you may well know, I am in the process of updating a network, thats very out of date- yet works pretty much fine!...

Clearly everyone plumps for a domain server... however, I am struggling to see the advantages for out situation, based on the cost...

For:
Anti-virus updates can be centrally deployed (But they auto update with no dialogue boxes every 3hrs anyway)
Windows update patches centrall deployed (But again- these can be auto installed)

Against
20 machines which need to be converted from xp home to xp pro-
The expense of the above, both in terms of ££ and time!

The pro's mentioned on wiki, http://en.wikipedia.org/wiki/Windows_Server_domain also don't seem to be that beneficial to us...

I can't help but think I am totally missing something obvious that must be an advantage of the domain setup!!

Comments

  • primesuspectprimesuspect Beepin n' Boopin Detroit, MI Icrontian
    edited September 2006
    Forget that other crap - the numero uno reason is in time savings.

    people will only have to authenticate once - each time they log in. Printers can be shared, folders can be shared, etc with minimal effort, and it "just works" for everyone. You can define policies, etc.

    With 20 people, you need a domain. The time savings will pay for it.
  • ShortyShorty Manchester, UK Icrontian
    edited September 2006
    Totally centralised configuration and management!

    You have 20 users who use 20 different machines. Each user must have credentials created on each machine. In a domain, the users account/credentials is stored on the domain controller rather than on each PC. Any user can use any machine with the same username, password, printer mappings, shared drive mappings.. internet settings..

    Domain uses DNS for machine name resolution. No more guessing with network broadcasts for machine names. Much more efficent for network traffic. This also means you can run multiple segmented networks to lower network traffic. DNS works across these segments, netbios broadcasts do not.

    You can create simple or complex login & logoff scripts for users that are loaded when someone logs in. Mapping drives, printer access rights, security rights and automated backups when users logoff to the server for nightly backups. Setup home folders (traditionally H: drives) with redirection.

    Lock PCs down to what the adminstrators want users to use, using group policy.. you can personalise to suit a specific user groups needs.

    There is so much a domain can do for even a tiny company of just 5-10 employees. The above is just an example!

    Domain/Active Directory is not just for big enterprises.
  • ShortyShorty Manchester, UK Icrontian
    edited September 2006
    Prime beat me to it. Damn gurus ;D
  • osaddictosaddict London, UK
    edited September 2006
    Yeah, see from what you guys have said, I am still struggling to see an advantage from our pov- atm we do not connect to a domain server- yet to access the mapped drives, the printer etc you only have to log on once- thats it- you only have to log on again if you reboot or something...

    As for workstation backups- only outlook pst files need to be backed up really- anything on an individual users pc will not be (or at least should not be!) work related!

    If this post seems a little odd- I am trying to persuade someone else that we should go for a domain server!, atm my arguements don't stack up too well compared to the cost!
  • zero-counterzero-counter Linux Lubber San Antonio Member
    edited October 2006
    osaddict wrote:
    Yeah, see from what you guys have said, I am still struggling to see an advantage from our pov- atm we do not connect to a domain server- yet to access the mapped drives, the printer etc you only have to log on once- thats it- you only have to log on again if you reboot or something...

    As for workstation backups- only outlook pst files need to be backed up really- anything on an individual users pc will not be (or at least should not be!) work related!

    If this post seems a little odd- I am trying to persuade someone else that we should go for a domain server!, atm my arguements don't stack up too well compared to the cost!
    You may be looking into the wrong kind of server then. Any non M$ server product will have a maximum allowable cocurrent connections. If you go the domain route, it will be the 20 licenses with the OS. GPOs are the sh1t though, and help minimize the added stress of some components of PC management. But Samba is really starting to look good about now...

    Ubuntu's Samba implementation is working just fine for our 10 workstation call center.
Sign In or Register to comment.