I can recommend a couple of good books on the subject: Windows XP Embedded
Step-by-Step and Windows XP Embedded Advanced.
Chapter 16 of Windows XP Embedded Advanced talks about creating custom
shells.
Is Remote Desktop Connection the only application that you want to have the
user access in the system?
Regards,
Sean Liming
XP Embedded Manager
A7 Engineering (www.a7eng.com)
Author: Windows XP Embedded Advanced and Windows NT Embedded Step-by-Step
I did this by changing the "Shell" value in "HKLM\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon" to point to a .cmd script that invokes mstsc.exe
with a specific .rdp file pointing to my Terminal Server. It loops around so
launches again if the user logs off or otherwise loses their session. Simple
but effective and the user doesn't really see the script - they can stop the
script but the cmd window closes so they can't get at the local system. I
guess you could write a simple Win32 GUI app that used CreateProcess() if
you wished but this saves the effort and is easier to change. I guess that
you could just specify mstsc.exe as the executable if you didn't want to
pre-customise the user's settings (or change their default.rdp instead).
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.