Mapped drives versus Server model

[marsha]

I am now curious about the difference in the way two different systems work.
One is a network system where one computer shares a folder with data that
any user can change. That folder on the one computer is mapped to the other
users. I basically understand this workgroup model.

But what I don't understand is a domain model with the data computer using
server software. I have never used such a system. First, let's say we are
talking
about Windows Server 2003 or whatever is the most popular server software.

That is the operating system for that computer isn't it?
How does the server provide the data to the users in a more reliable way
than a networked system?

Thanks for any understanding on this. I'm obviously a newbie with this but
very
curious. Thanks again. And thanks for bearing with me on this slightly off
topic
question.

 

[Kurt]

The answer is that it really works the same way. The main difference (there
are a lot, but...) is how permissions are assigned to that share. In a
workgroup environment, all computers sharing a resource to users on other
computers must have user accounts that exactly match the way those users
logon to their workstations. If a user changes a password, that password
change must be replicated on every computer that shares something that
particular user requires access to. In a domain environment, permissions are
controlled at the domain level, not the local computer. So any resource that
is shared to "domain users" will immediately become available to anyone who
logs into the domain. By the same token, users can be easily organized into
groups, so permissions for a whole group of users can be assigned all at
once via the group. With lots of computers and users, it's the only way to
fly. The second biggest difference is in the ability to apply your network
policies (rights to change network settings, install software, change
internet explorer setings, etc) to users and computers using group policy.

....kurt

 

[marsha]

The answer is that it really works the same way. The main difference (there
are a lot, but...) is how permissions are assigned to that share. In a
workgroup environment, all computers sharing a resource to users on other
computers must have user accounts that exactly match the way those users
logon to their workstations. If a user changes a password, that password
change must be replicated on every computer that shares something that
particular user requires access to. In a domain environment, permissions are
controlled at the domain level, not the local computer. So any resource that
is shared to "domain users" will immediately become available to anyone who
logs into the domain. By the same token, users can be easily organized into
groups, so permissions for a whole group of users can be assigned all at
once via the group. With lots of computers and users, it's the only way to
fly. The second biggest difference is in the ability to apply your network
policies (rights to change network settings, install software, change
internet explorer setings, etc) to users and computers using group policy.

Super info!!! Does "domain" automatically imply using server software or
is domain setup possible independent of server software. I have seen the
option
to setup a domain or a workgroup many times. So I am curious.
Thanks!!!!!!!!

 

[Kurt]

A Windows domain requires Windows server software, and be very careful to
compare features before you choose one. You can set up an NT4-style domain
using Linux, but if you're not familiar with Linux, be prepared for a
struggle. Although a Samba domain running under Linux looks like a Windows
domain to the clients, the server management is much different with none of
the point-and-click tools used to manage a real NT4 domain. It's something
you'd need to read up on - there are many good books - before you attempt to
set up a domain.

....kurt

 

[marsha]

A Windows domain requires Windows server software, and be very careful to
compare features before you choose one. You can set up an NT4-style domain
using Linux, but if you're not familiar with Linux, be prepared for a
struggle. Although a Samba domain running under Linux looks like a Windows
domain to the clients, the server management is much different with none of
the point-and-click tools used to manage a real NT4 domain. It's something
you'd need to read up on - there are many good books - before you attempt to
set up a domain.

We will definitely go with MS windows. But is Windows 2003 server the
obvious
choice since we are going with windows? I have heard of MS SQL Server
Desktop
engine and I am wondering if that would be a better choice but that is only
asked out
of a tremendous amount of ignorance. What do you think about that
as a
possible choice???

Kurt, thanks so much for your help. It has been really wonderful.

 

[Kurt]

SQL desktop is a limited user SQL server, not a server OS. It will allow you
to create SQL database applications with a limited number of users (you'd
have to check on the number - or someone will probably post it). I have been
following your other thread and found that you are using XP Home computers,
which is a serious no-no for professional environments. I probably have
mentioned it before, but XP home will not participate in a domain. Even so,
if you require more than 10 simultaneous connections to a server, a server
OS (with the number of licenses you need) will solve that problem. If you
are unfamiliar with Windows domains, see about certifying as an MCSE or an
MCSA. It will arm you with the knowledge you need to set things up right.

....kurt

 

[marsha]

SQL desktop is a limited user SQL server, not a server OS. It will allow you
to create SQL database applications with a limited number of users (you'd
have to check on the number - or someone will probably post it). I have been
following your other thread and found that you are using XP Home computers,
which is a serious no-no for professional environments. I probably have
mentioned it before, but XP home will not participate in a domain. Even so,
if you require more than 10 simultaneous connections to a server, a server
OS (with the number of licenses you need) will solve that problem. If you
are unfamiliar with Windows domains, see about certifying as an MCSE or an
MCSA. It will arm you with the knowledge you need to set things up right.

Thanks Kurt,
I'm planning on doing that if I live long enough. lol

Will w2k OS participate in a domain?? One of our user machines is already
xp pro,
two are w2k, and two are xp home.

Thanks again!!!

 

[Kurt]

Yes, W2K pro and XP Pro (actually, even Windows 98 in a limited fashion)
will all participate. W2K and XP Pro will join the domain and you can
distribute group policy, push software, etc. Win 98 will authenticate users
via a domain controller, although you cannot distribute any group policy. If
you have 98 in a Server2003 domain, you must use WINS, and I would suggest
you install the latest "Directory Services Client" (dsclient) for W98.

....kurt