Re: Preventing access to

For some reason I had the pre-conceived idea that you couldn't create
Software Restriction Policies for 16-bit applications. I just created a
Software Restriction Policy for and it works great.

Thanks for your help! :)

Steven L Umbach wrote:
You can delete if you have not need to use it for 16 bit apps
but that will not stop someone from copying it to their user profile to run.
A couple possibilities to try to prevent it's access could be - as you
mentioned delete it or change the permissions on it [probably better option
than deleting] so that only authorized users can execute copies the
currently exist on the computer, add to the disallowed Windows
application list under user configuration/administrative templates/system -
don't run specified Windows applications with the understanding that it will
not work if a user renames, using Group Policy Software
Restriction Policies for XP Pro to create a hash rule to disallow use of and if you do that try to find all the versions of
you can from the different operating systems or again assuming you have no
need to run 16 bit applications you could also try deleting or renaming
AUTOEXEC.NT in the \Windows\system32 folder.


<joshua.morgan@xxxxxxxxx> wrote in message
Hi all,

Whilst you can use Group Policy to prevent access to cmd.exe, you can't
prevent access to as it is a 16-bit application.

Is there any other way to prevent access to Will deleting render the system unusable?


Joshua Morgan


Relevant Pages