Re: A user that only has access to shared network folders
- From: "Ron Lowe" <ron-msng@{d.e.l.e.t.e}lowe-family.me.uk>
- Date: Thu, 26 Jan 2006 09:39:55 -0000
He won't be able to sit down and log on at the keyboard / screen of that
machine, correct.
But he WILL be able to connect to shared folders on that machine across the
network if they have been shared with the correct permissions for him.
This is a fairly standard configuration, and for example is often used on
servers:
Domain users are denied 'local logon' privilidges on the servers, only
domain admins can sit down at the server console and log in. Domain users
can, of course, connect to shares held on the server.
That was my understanding of the OP's request.
--
Best Regards
Ron Lowe
"Ian" <Ian@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:55F88888-0224-4875-BBCB-F44E1EDB5D7A@xxxxxxxxxxxxxxxx
> 3. Expand "Local Policies", "User Rights Assignment" in the tree; find
> "Deny
>> logon locally" in the list, double click that and add your user.
>
> If you do that, the user won't be able to log on. :-(
>
> However, if the user is a standard (non-Admin one) and you are using NTFS
> with the standard permissions set, then the user shouldn't be able to
> write
> to disk outside of their own profile-folder under "Documents and
> Settings."
> It's then just a matter of restricting folders like "my documents" to
> readonly. If you don't want ANY changes made by the user to survive a
> reboot, then enforcing a Mandatory Profile on the user would achieve that.
>
>
>
.
- References:
- A user that only has access to shared network folders
- From: billypurdue
- Re: A user that only has access to shared network folders
- From: Chris Priede
- A user that only has access to shared network folders
- Prev by Date: Re: sharing my network
- Next by Date: Re: Event 8003 causing reboot
- Previous by thread: Re: A user that only has access to shared network folders
- Next by thread: VPN error: 651
- Index(es):
Relevant Pages
|
