Force to use only one application after logon via RDP
- From: "Wx" <sciuscianebbia@xxxxxxxxx>
- Date: 20 Sep 2006 01:38:46 -0700
Hi,
1st problem: I want to force a user working via RDP to use only one
application. No problem setting the startup application in the property
of the RDP connection, but the user can connet without using this
option, having "full" access on the server.
2nd problem: this application need administrative access to work (yes,
it sucks!) so, looking at the point n.1, it's very important to
limitate what the user can do.
My domain is based on Windows 2003 STD, the clients are Windows XP
machines.
I think that those points can be accomplished by using Policy; but
which?
Those policy are useful when applied to user who have administrator
privileges?
Many many thanks
Matteo
Sorry for the (maybe) bad english, but it's not my native language and
i'm still learning it :)
.
- Follow-Ups:
- Re: Force to use only one application after logon via RDP
- From: Mahesh Lotlikar [MS]
- Re: Force to use only one application after logon via RDP
- Prev by Date: Re: Multiple mstsc.exe sessions running on WinXPw/SP2
- Next by Date: Win2003 R2 with SP1 terminal server crash and restart
- Previous by thread: TS 2k3 redirected printers do not get purged
- Next by thread: Re: Force to use only one application after logon via RDP
- Index(es):
Relevant Pages
|
