G
Guest
Hello, I think I’m doing this through my MSDN alias correctly this time. If
not maybe one of the MS guys can point that out.
I’m currently working with an XPe build that is headless, has a custom shell
and starts with an autologin (full Windows login, not minilogon). I want to
be able to control the machine remotely for diagnostics and whatnot with
minimally Remote Desktop and preferably Netmeeting Desktop Sharing, Remote
Assistance, or in a pinch VNC.
Right now I have two problems.
1 – Remote Desktop doesn’t work unless the user logs out first. When I use
RDP with XP Pro, the currently logged in user is kicked as soon as an RDP
connection is made. I’ve tried logging in with the shell account and another
account as well, with no luck. Currently I have a hack in place to log out
the user if they select “allow remote controlâ€, but this is just silly. I’ve
tried enabling Fast User Switching in the image (via
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\
AllowMultipleTSSessions but this hasn’t fixed anything. What am I missing
with this?
2 – How do I programmatically (or via scripting) allow for remote control of
the device without kicking the user? Both Neetmeeting Desktop Sharing and
Remote Assistance allow this, but they both send up UI elements for the user
to click and approve the connection. This obviously won’t fly in a headless
device with a custom shell. I can configure some flavor of VNC to do this,
but I’d rather keep my security vulnerabilities constrained to MS products.
Thanks in advance.
not maybe one of the MS guys can point that out.
I’m currently working with an XPe build that is headless, has a custom shell
and starts with an autologin (full Windows login, not minilogon). I want to
be able to control the machine remotely for diagnostics and whatnot with
minimally Remote Desktop and preferably Netmeeting Desktop Sharing, Remote
Assistance, or in a pinch VNC.
Right now I have two problems.
1 – Remote Desktop doesn’t work unless the user logs out first. When I use
RDP with XP Pro, the currently logged in user is kicked as soon as an RDP
connection is made. I’ve tried logging in with the shell account and another
account as well, with no luck. Currently I have a hack in place to log out
the user if they select “allow remote controlâ€, but this is just silly. I’ve
tried enabling Fast User Switching in the image (via
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\
AllowMultipleTSSessions but this hasn’t fixed anything. What am I missing
with this?
2 – How do I programmatically (or via scripting) allow for remote control of
the device without kicking the user? Both Neetmeeting Desktop Sharing and
Remote Assistance allow this, but they both send up UI elements for the user
to click and approve the connection. This obviously won’t fly in a headless
device with a custom shell. I can configure some flavor of VNC to do this,
but I’d rather keep my security vulnerabilities constrained to MS products.
Thanks in advance.