- For individual users
- Instant access to solutions
- Ask your tech questions
- Start your 30-day Free Trial
Main Topics
Browse All TopicsI have an application that I am publishing on Server 2008, using Terminal Services RemoteApp manager.
If a remote client connects with the "correct" client software (basically XP sp3 or Vista) they see the application in it's own window just the way they are supposed to.
But if they remote in using an earlier client (such as the one on Windows 2000) they are allowed to log on to the desktop. And even though I have the box checked in RemoteApp that only allows them to run the designated program, they are still able to do things like run Services (in read only mode) and run Notepad.
I don't want them to run anything. I don't want them to see the desktop. I don't want them in there at all unless they have the client they need to run the application that I'm publishing.
How can I keep these older clients from connecting to my RemoteApp machine?
Thanks.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: gateguardPosted on 2009-06-20 at 16:17:12ID: 24675597
I found what to do:
ve Templates\Terminal Services\Terminal Server\Remote Session Environment\Start a program on connection
Start | Run | MMC
Add snapin: Group Policy Object Editor
Click Browse and choose an available user or group (NOT administrators)
User Configuration\Administrati
Put in the program, path and working directory. Even with a "low grade" remote desktop connection, the user will now be able to only run the designated program and will be logged out when exiting that program.