Terminal Service Security in Application through System32

[Alcksang]

My company actually is a Application Service Provider which enable our
clients to logon to our systems through Terminal Servers to access our
Application.
Unfortunately, our Application need to have a 'File -> Open' function to
open some files for the Application.
Althought, we have used the GPO for Terminal Service to only allow the users
in just accessing the Application itself.
What I have found out is that, through this 'File -> Open' function, I can
easily navigate to 'Windows\System32' to activate the 'cmd.exe' command. From
here, then I can do whatever I want especially when there is a Administrator
account (some users need that better authority to some service).
May I know if there is any kind of ways in blocking our users in navigating
to the 'cmd.exe' command or simply to say, block them from accessing the
'System32' commands?

 

[Lynn Trapp]

You'll probably get a better response if you post this in one of the Windows
newsgroups. This newsgroup is dedicated to MS Access, the database product.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html

 

[Alcksang]

Ops. Guess I been misleaded by the 'Access Security'.
Never think that is a Microsoft Access. Thank you for the information.

 

[Lynn Trapp]

You're welcome. Lots of people get fooled by that. Good luck with your
project.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html