Re: workgroup vs domain
- From: "Danny Sanders" <DSanders@xxxxxxxxxxxxxxx>
- Date: Mon, 11 Jun 2007 10:38:15 -0600
With an AD domain, would students be able to log on to a lab computer
under limited user and still access the file server?
By default when you create a user on a Domain controller they are "limited"
users. The are not administrators of the domain or the local computer they
are logging on to. You would grant them proper access to the shared folders
on the server.
Would they do
this with or without entering a user and password to connect to the
server?
They would log onto their local computer with a username and password and
access the shared folders on the server without the need to enter a username
and password.
My idea for the lab is this: a student can sit at any computer in the
lab, log-on as a limited user on that computer, access their files on
a shared folder on the server and continue their work. Each computer
already has the applications installed locally on its' HD. Then, save
their work in the shared folder on the file server, come back the next
day and do the same again from a different computer. Possible? What
Win 2k3 server components would be needed? I just need to be pointed
in the right direction regarding all the Win 2k3 server components.
There are so many. AD dominan server + DNS + ???
Look into roaming profiles.
hth
DDS
<arodri3@xxxxxxxxx> wrote in message
news:1181378765.711650.224950@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jun 8, 11:18 am, "Danny Sanders" <DSand...@xxxxxxxxxxxxxxx> wrote:
In my scenario, would a domain server be best or would workgroup be
all I need?
Domain is the way to go. But don't take this lightly. If you've never
setup
a domain before a production environment is not the place to learn.
What other questions do I need to ask myself before I continue
networking?
Not meaning any dis-respect, but you might think about hiring a
consultant
to come out and setup the domain. Depending on how much money is
involved,
he could come in and setup the domain on the server and show you how to
join
the client computers to the domain. Or if money is not a problem he can
do
the entire setup and then hand the keys to you.
If a consultant is out of the question I would suggest you take some time
and do some reading up on setting up an AD domain. You can setup a "lab"
of
3 cobbled together computers for this. Doing this in a lab first will
give
you a chance to get familiar with domains and if everything goes belly
up,
you can take your time and learn what happened instead of having everyone
looking over your shoulder because the network is down and you have to
read
a couple of chapters to get the problem fixed.
Reading?
The addition of AD to your Win 2k3 server will make it a domain
controller.
See:http://support.microsoft.com/kb/324753/en-us
Don't run dcpromo on your existing Win 2k3 server now, it will loose all
the
configured users on it.
For an AD domain to work right you need DNS also
See:http://support.microsoft.com/kb/814591/en-ushttp://support.microsoft.com/kb/825036/en-ushttp://support.microsoft.com/kb/323380/en-us
hth
DDS
<arod...@xxxxxxxxx> wrote in message
news:1181325223.362576.284550@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I work at an elementary school in Los Angeles and our school just
purchased a Windows Server 2003 R2 64 bit. I have 36 computers in a
lab which I would like to connect to the server as a file and print
server. I want the students to be able to access the file server from
any computer in the lab to access their teachers shared folders where
they work and save their documents. I want to do this with as little
passwords as possible.
Currently all the computers and server are in a workgroup where they
can see each other. When I try to access any computer from the server
or any other computer, I am unable because it asks for user and
passwords.
On the server, I've set up file server and print server only, but I
cannot connect between computers. Is this an issue having to do with
domain vs workgroups and do I have to set up user accounts in
workgroup. Or can the computers connect and access the shared folders
on the server?
In my scenario, would a domain server be best or would workgroup be
all I need?
Do accounts and passwords need to be set?
What other questions do I need to ask myself before I continue
networking?
Any help is greatly appreciated.
1200 elementary students at my school would greatly appreciate any
help.
Yes, we are a huge elementary school!
Thanks for the quick reply.
Money is short these days this late in the school year, but I've asked
the principal to hire a a consultant. I just need to wait and see if
the money is available. Meanwhile, I will read the links you suggested
and try to figure this out. I go back to work on Wednesday (short
vacation) and I'll apply what I've learned. Please check back on
Thursday to see if I had any luck (or if I have really screwed things
up).
Question:
With an AD domain, would students be able to log on to a lab computer
under limited user and still access the file server? Would they do
this with or without entering a user and password to connect to the
server?
My idea for the lab is this: a student can sit at any computer in the
lab, log-on as a limited user on that computer, access their files on
a shared folder on the server and continue their work. Each computer
already has the applications installed locally on its' HD. Then, save
their work in the shared folder on the file server, come back the next
day and do the same again from a different computer. Possible? What
Win 2k3 server components would be needed? I just need to be pointed
in the right direction regarding all the Win 2k3 server components.
There are so many. AD dominan server + DNS + ???
1200 Thank yous
.
- References:
- workgroup vs domain
- From: arodri3
- Re: workgroup vs domain
- From: Danny Sanders
- Re: workgroup vs domain
- From: arodri3
- workgroup vs domain
- Prev by Date: Re: Domain account iwth restricted rights
- Next by Date: Newbie question
- Previous by thread: Re: workgroup vs domain
- Next by thread: Re: workgroup vs domain
- Index(es):
Relevant Pages
|
