"Brad" <Br...@discussions.microsoft.com> wrote in message
news:4FCA8EFA-1385-4B94...@microsoft.com...
> I am using autologon inxp embedded and it works great the first time.
After I use remote Desktop Connection to access the machine and do some
service, and logout form the remote session. I am left with a logon on the
machine.
>
> The machine is used as a kiosk and on ocassion there is a need to go mess
with something. We do this over the network using the remote desktop
connection. Once we are done we need it to turn back into the kiosk it was
not have a logon on the screen. The kiosk has not keyboard....
>
> Thanks
> Brad
I don't know any good solution here unless you do a custom MSGina and send it a signal to re-logon again when a remote terminal
session is over.
Another possible solution (this has been discussed in the NG) was to issue a reboot command on the RDP session termination (or just
remotely restart the device). Then on the next boot Autologon will happen.
--
Regards,
KM, BSquare Corp.
"KM" <konstmor@nospam_yahoo.com> wrote in message
news:OvtdQjeb...@tk2msftngp13.phx.gbl...
http://www.microsoft.com/windows2000/techinfo/administration/security/msgina.asp (+ many useful links on MSDN).
Also, there is a custom MSGina sample code on www.xpefiles.com.
Bug Report / Suggestions for the Windows Embedded team.
E-mail this bug report or product suggestion below to wecrt AT
microsoft.com. All suggestions or bugs will be added to the product
team’s bug database. If you require assistance in troubleshooting a
problem with your device or runtime, either post your question to the
Microsoft public newsgroup (microsoft.public.windowsxp.embedded) or
contact Microsoft Product Support Services
(http://support.microsoft.com/default.aspx?pr=cntactms&style=home).
Your Name:
(Optional)
Your e-mail address:
(Optional unless you want us to contact you):
XPe Version:
(Gold, SP1, SP2)
MUI Language Pack:
(N/A, English, Japanese, etc...)
Brief Bug Description or Product Suggestion:
(This is the Title of your Bug or Suggestion)
Detailed Bug Description or Product Suggestion:
(Be as detailed as possible, list hardware or software required to
repro the bug, etc...)
Steps to Reproduce the Bug:
(If applicable, please list the exact steps to repro the issue and be
as detailed as possible)
Additional Information:
(Paste sections of the FBA Log, the TD Build log, list of componen
"Andy Allred [MS]" <and...@online.microsoft.com> wrote in message
news:#vOtGMfb...@TK2MSFTNGP11.phx.gbl...
Please add my vote to the request for the addition of this option.
Regards,
Joe
Thanks
Brad
Regards,
Sean Gahan
If it is scheduled disconnect from the terminal server, you can definitely
reboot client devices.
If you want to trace accidential disconnects (like server timeout or etc.)
than you have to work with the RDP client APIs.
I haven't really played with the mstsc.exe on low level API. There must be
something useful to you.
However, the Terminal Services Clint ActiveX control exposes a couple of
useful things for you too (at least it is a start point): "Connected"
property, "OnDisconnected" event (this event is called when the client
control has been disconnected from the terminal server) and you use
get_ExtendedDisconnectReason methoed to retrieve extended information about
why the RDP control disconnected.
KM
Check out Terminal Services API functions.
Particularly, WTSxxx stuff.
http://msdn.microsoft.com/library/en-us/termserv/termserv/wtswaitsystemevent.asp
KM
VNC - Virtual Network Computing.
You may actually be interested in WinVNC. Freeware: http://www.snapfiles.com/get/vnc.html
Or even servers: http://www.realvnc.com/winvnc.html, http://www.csd.uwo.ca/staff/magi/doc/vnc/winvnc.html
I personally prefer RAdmin (lighter but pretty much the same functionality): www.radmin.com.
--
Regards,
KM, BSquare Corp.