Local Logon

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am looking for a way to have users logon with a local machine account then
use a auto logon, or post logon script to log on to the net work which is a
windows 2003 server network, so that non net work user have access to just
one drive on the network without issueing a net work id to them.

Any Ideas?
 
In
Doug Beard said:
I am looking for a way to have users logon with a local machine
account then use a auto logon, or post logon script to log on to the
net work which is a windows 2003 server network, so that non net work
user have access to just one drive on the network without issueing a
net work id to them.

Any Ideas?
Click to expand...

Hmmm - this doesn't make a lot of sense to me, at least not as written. I'm
presuming you have a domain. If so, create domain logins for all your users,
and *no* local workstation accounts at all (password protect the local
administrator accounts & don't grant domain users local admin rights
either).

You can control who gets access to what, on the server, via groups - and put
the users into the appropriate groups.

Of course, you also need a good password policy - 8-char minimum with forced
regular changes, at minimum.
 
OK
Lets put it this way then.
You have a domain that is CAC provisioned, and visitors, lets say to a
university, where maybe 40 or 50 people come to take a class for a day or
two. They need to calaborate their work on a shared drive or use network
printers.

You dont want to issue CAC cards to be used, nor issue net work user ids and
passwords. You dont mind they use the computers, but want to keep network
security by hiding a generic network account,,.

You may have a combination of students in the class some that are network
users that have CACs to logon to the network, and the group that doesnt. So
at the windows logon you want Network users to logon with their credintiels,
and you would like the guest to logon, but want local account to assign net
work account privledges reduced of course but to some extent, without using a
shared guest network user id/password.
Hope this clarifies the enviroment that I am looking to use this.

Thanks For the response
 
Doug said:
OK
Lets put it this way then.
You have a domain that is CAC provisioned, and visitors, lets say to a
university, where maybe 40 or 50 people come to take a class for a day
or two. They need to calaborate their work on a shared drive or use
network printers.

You dont want to issue CAC cards to be used, nor issue net work user
ids and passwords. You dont mind they use the computers, but want to
keep network security by hiding a generic network account,,.

You may have a combination of students in the class some that are
network users that have CACs to logon to the network, and the group
that doesnt. So at the windows logon you want Network users to logon
with their credintiels, and you would like the guest to logon, but
want local account to assign net work account privledges reduced of
course but to some extent, without using a shared guest network user
id/password. Hope this clarifies the enviroment that I am looking to
use this.
Click to expand...

Why don't you just set them up with their own server and printer instead
of even allowing them on your network? Or else simply create a generic
user called "student" with a simple password ("student" perhaps!) and
have them log on that way. Put them into a "student" group and then you
can limit them as you wish. You don't need to hide anything or write
scripts. Server 2003 is more than capable of creating user groups that
only give access to whatever you want.

Malke
 
Back
Top