My guess is that it will be supported if not built into future versions of
the operating system. I find that using the Shared Computer Toolkit is
rather easy to use once you try it a bit and is probably the best and
fastest way to lock down a user particularly on a non domain computer. If
the computer is XP Pro and in an Active Directory domain you can use
Software Restriction Policies to restrict that user. You could also use NTFS
permissions to give the user explicit deny permissions to any folder you do
not want that user to access or run an application from and would also need
to modify the user's permissions on his user profile under documents and
settings so that he does not have execute permission to it to prevent the
user from installing or running any application/executable from there since
by default users have full control permissions to their user profile. ---
Steve
http://support.microsoft.com/default...b;en-us;308418 --- NTFS
folder/file permisisons
"bestofcomputer" <(E-Mail Removed)> wrote in message
news:575EA165-E34F-4944-B982-(E-Mail Removed)...
> Hi.
> Thanks for that Toolkit.
> Very usefull.
> Will it come to XP into a SP3 ?
> Or will be part of Vista also ?
> Anyway, I find it a little bit difficult, so would you give me a sample of
> modification of my Group Policy or Registry, in my XP SP2, without the
> need
> to install this Tollkit ?
> Where else to find some ressources, not related to this Toolkit, because I
> just want to disable executables for 1 account, not maintaining a cyber
> cafe !
> Thanks.
>
>
>
> "Steven L Umbach" wrote:
>
>> As Dominikus suggested try the Shared Computer Toolkit or if you are
>> using
>> XP Pro you can configure Software Restriction Policies in Local Security
>> Policy as shown in the link below and the enforcement rule can be
>> configured
>> to not restrict local administrators. --- Steve
>>
>> http://www.microsoft.com/technet/pro.../rstrplcy.mspx
>>
>>
>> "bestofcomputer" <(E-Mail Removed)> wrote in
>> message
>> news:07F2716E-61A9-4811-B413-(E-Mail Removed)...
>> > How to create an account of a user who will be unable to install
>> > anything,
>> > either by himself, or as an automatic script or else coming from
>> > internet
>> > or
>> > mail or cd-roms ?
>> > I dont think a Limited Account is enough for that.
>> > It might be necessary to configure the user Policy.
>> > But how ? What to do ?
>> > Thanks.
>> > Frederic Laroche.
>> >
>> >
>>
>>
>>
Similar Threads
