Workgroups you have to administer each PC.. they're not as secured.. they work independent but can see each other on a network. It's like hooking 2 PCs up at home.
Now a domain.. oh how I wish my idiot boss would understand that we need one.
I have 1200+ computers at work and I'm on a workgroup, meaning I need to administer EACH PC..
With a domain, I can administer all those PCs from the Server (DC = Domain Controller, most likely the Server).
I can create login scripts so when a user logs in, commands run to update software, remove software, make system changes, slap them in the face, etc.
PCs log into a DC/Server on a domain. That machine controls what that PC & user is able to do. You can restrict access, you can make them administrators. A domain gives you more control over all your PCs from 1 computer.
With a domain, you can walk up to any computer (in most cases unless restricted) and log in as yourself. So you could walk up to computer A, log in as Joe with password "whatever" then you could walk up to another computer and log in with that stuff. You don't have to have a local account set up on the PC. It's all stored on the server. If I didn't want you to log in, I could disable your account and you wouldn't be able to log in anymore.
A workgroup each user that wants to log into the PC has to have a user account set up on the PC, or a general one for everyone to log in. With a domain, you create the account once on the Server/DC and they can log into any PC attached to the domain.
A domain is a centralled administer computer network. All PCs are connected to a DC/Server which is basically God of all the computers. You can do anything and everything from the server to the PCs attached.
A workgroup is good if you have a handful of computers, don't really need to share files that much, and all PCs are in the same location. With a domain, you can specify a Network Drive to share everything and you can redirect everyone's.. My Documents folder lets say, to F:\Shared Folder.. now F: would be connecting to the Server, so everyone's files would be on the server, instead of on the local PC.
You can use a workgroup the same way as a domain, but the domain removes the huge amount of administration needed to maintain computers.
If you have 10 computers in a workgroup and you wanted to change people's passwords, you'd have to go to each computer. On a domain, you'd make a simple change and everyone would have to change their password.
Sorry for such a long post.. I'm venting.. I have to deal with 47 locations, 1200+ PCs on a workgroup. It's such a pain.
On the bright side I wrote a nice little batch file, tossed it on a CD with an autorun file.. it pops up with 4 options - Install Standard Programs, Install Standard and Technical programs, Install Technical Programs, or Exit.
By selecting one via an associated number (1-4) it'll go through and silently install the software.. I repackaged all software into an MSI format using Wise Package Studio..
Now if I was on a domain, I'd put this stuff on the server and when the user logs in, I'd have it automatically run at that point and never worry about it. But being in a workgroup, I need to install everything manually on each PC.
BAH.
It even has a easy webconfig that looks similar to most home routers (it could even be your home router). I'm using it on a via epia computer right now at my house for a router, webserv, email serv, etc and it works like a champ. The best part is you dont have to know jack about linux to use it and get the benifits of linux, lol.
Facebook
Twitter
Instagram