As the title states. I kinda like the way it is setup at work and was wondering if it is worthwile to do it at home when I build a new server.
What advantages does it have over a workgroup?
What are you trying to accomplish by having a home domain? Keep in mind that, legally, you need to purchase a Windows Server OS and have a dedicated computer/server always on.
As the title states. I kinda like the way it is setup at work and was wondering if it is worthwile to do it at home when I build a new server.
What advantages does it have over a workgroup?
magichands said:That is flat out wrong.
You can run a domain as long as you have a server that can host the domain. It could be a server out in the AWS cloud or it could be a server run locally. The OS Server choice doesn't matter as long as it is able to act as a DNS Server.
Is running Microsoft software (for most people) easier? Sure. But it is in no way the cheapest solution. You could easily run CentOS with Bind.
Now, if the idea is administrate the Domain within the home then most would want to use Windows unless they are Linux/Unix savvy.
That is flat out wrong.
You can run a domain as long as you have a server that can host the domain. It could be a server out in the AWS cloud or it could be a server run locally. The OS Server choice doesn't matter as long as it is able to act as a DNS Server.
Is running Microsoft software (for most people) easier? Sure. But it is in no way the cheapest solution. You could easily run CentOS with Bind.
Now, if the idea is administrate the Domain within the home then most would want to use Windows unless they are Linux/Unix savvy.
What are you trying to accomplish by having a home domain? Keep in mind that, legally, you need to purchase a Windows Server OS and have a dedicated computer/server always on.
I guess it's good practice if you're preparing yourself for MCITP. I did that a couple years ago to get a better feel for Hyper-V, Windows Server, the new group policy options, and a few other things. I subscribe to TechNet, so I was able to install all of it for testing.
as a tech student i get loads of ms software for free, so i did the same thing. ive played with group policies, sharepoint and a few other things. i have a couple of VMs on esxi running server 2008.
as it stands i keep a DC running; when my daughter is out of order i disable her account (because...hey, i got pro versions of windows, too)
if you have to pay extra for things though...i wouldnt bother. its not generally worth it, and i only do it because i had stuff running for labs anyway
FTW..nice, Ill have to remember that!, guess you could use a proxy and internet access times as well!
FTW..nice, Ill have to remember that!, guess you could use a proxy and internet access times as well!
As the title states. I kinda like the way it is setup at work and was wondering if it is worthwile to do it at home when I build a new server.
What advantages does it have over a workgroup?
A domain will give you fine grained controls over User access. You can setup user accounts, passwords (password policies), limited access on file shares, and Group Policy to customize your desktop. For 2-5 users... its really much easier to just manage them on independently. Spending $2g on Windows Server, and running dedicated hardware is probably not cost effective for most users. You'll also need Windows Professional or higher, so expect to pay another $75+ for each machine to upgrade from Home.
tl;dr The main advantage over a work group would centralized user account control, and Group Policy for desktop customization/control.
Its a good way to learn if you wish to become a Windows Network Administrator however.
Nah. Unless you're running a LOT of computers I don't see it being worth it. Licensing is expensive. Plus if your AD controller goes down you can't authenticate to the domains (you can likely log in under cached credentials but it still would cause issues)
Only reason is if you want to play around and learn, but I certainly wouldn't do it as a licensed thing for my main rigs.