Win2000 Profiles

rgedye · 04-04-2002, 09:41 AM

Although I have sucessfully restricted just about everything on client wk2 desktops using profiles, I still have one hole.

If the users click start, then double click, say programs, explorer opens and they can browse the entitre machine (and possibly else where) & launch programs.

Anyone know of a way to restrict this action, or remove the startbutton/toorbar altogether?

I'd rather not try to get restrictive with rights on the machine.

I've played with locking down the profile directories on the local machine, but that causes problems in loading the profile upon boot.

Any help is appreciated.

**Zvalkor** · 04-04-2002, 07:53 PM

The only thing I can think of is Policy Editor. There is an option to allow the user to run only allowed applications, do not include explorer.exe and taskman.exe. If you do not have policy editor, you can get it here, http://support.microsoft.com/default...-US/policy.exe

good luck :)

04-04-2002, 09:41 AM	#1 (permalink)
rgedye Registered User Join Date: Apr 2002 Posts: 1 OS:	Win2000 Profiles Although I have sucessfully restricted just about everything on client wk2 desktops using profiles, I still have one hole. If the users click start, then double click, say programs, explorer opens and they can browse the entitre machine (and possibly else where) & launch programs. Anyone know of a way to restrict this action, or remove the startbutton/toorbar altogether? I'd rather not try to get restrictive with rights on the machine. I've played with locking down the profile directories on the local machine, but that causes problems in loading the profile upon boot. Any help is appreciated.

04-04-2002, 07:53 PM	#2 (permalink)
Zvalkor Senior Member Join Date: Apr 2002 Location: Central Valley, CA Posts: 598 OS: XP Pro , SuSE 8.2	The only thing I can think of is Policy Editor. There is an option to allow the user to run only allowed applications, do not include explorer.exe and taskman.exe. If you do not have policy editor, you can get it here, http://support.microsoft.com/default...-US/policy.exe good luck :)