Which is still worth it if you have kids or other family members and
need a way to centrally control the machines.
The other thing with Home at least, is that you have NO ACCESS to the
security tabs to be selective about who can use a given folder or resource,
Ben Ruset wrote:
For home use you would not need to worry about any of this stuff. It's
more business level stuff where user accounts and whatnot are stored on
a central server, and each PC "joins" itself to the "domain" (the server
or a group of servers) to get access to the central user database,
resources on the server, etc.
dsinc wrote:
Okay. What does not being able to "join" a WinNT domain or Win2K/2K3
directory mean to me? This sounds like big enterprise level stuff;
like, "[EMAIL PROTECTED]" and a whole lot of other hw
structure than I use at present.
Sorry for the dweeb question, but this stuff seems to moving ahead
faster than I can comprehend anymore.
At 10:30 08/04/2005 -0400, you wrote:
You can not join a Windows NT domain or Windows 2000/2003 directory.
It will work just fine as a node on a home LAN.
dsinc wrote:
What does *Cannot join a domain... really mean? Like it cannot be a
node on a home LAN or something?
Thanks.
Best,
Duncan
This email scanned for Viruses and Spam by ZCloud.net
- Re: [H] speaking of OS's warpmedia
-
