Session Reconnect

  • Thread starter Thread starter HS
  • Start date Start date
H

HS

Guest
We are testing windows 08 TS. We want to be able to run script when a user
reconnects to a disconnected session. Is it possible to detect reconnect for
each session in TS08 then do something? There is an app called reconnAct
that works with TS03, we tried but it didn't work with TS08.

All users are logging in from XPe and Linux Thin Clients.

--
HS
 
Re: Session Reconnect

This is very interesting scenario, can you please share with us what do you
want to do after reconnect/disconnect a session?
At the api level, you can try WTSWaitSystemEvent
http://msdn.microsoft.com/en-us/library/aa383856(VS.85).aspx
or WTSRegisterSessionNotification
http://msdn.microsoft.com/en-us/library/aa383841(VS.85).aspx apis.
Thanks
Soo Kuan



--
This posting is provided "AS IS" with no warranties, and confers no rights.

"HS" <HS@discussions.microsoft.com> wrote in message
news:8EDEE24B-DFEC-4D49-BA24-04D530A0BF69@microsoft.com...
> We are testing windows 08 TS. We want to be able to run script when a
> user
> reconnects to a disconnected session. Is it possible to detect reconnect
> for
> each session in TS08 then do something? There is an app called reconnAct
> that works with TS03, we tried but it didn't work with TS08.
>
> All users are logging in from XPe and Linux Thin Clients.
>
> --
> HS
 
Re: Session Reconnect

Soo Kuan, my original need was to detect reconnect and then run a script that
looks at “clientname” variable and re run parts of the logon script.
Specifically we need to provide proper printers depending on location of the
thin clients. Also delete printers if they reconnect from non thin client
locations.

I looked at WTSWaitSYstemEvent API but I am not a good VB coder and freeware
apps for Windows 2003 don’t really work well in Windows 2008.

After talking to Microsoft I did find out that I can create a task and use
“on connection to user session” as trigger to run a script. This is exactly
what I was looking for.
Now comes the hard part. The “clientname” environment variable is not
updated when a user reconnects a session. So I would still have CLIENTNAME
=thin1, when I reconnect a session from “thin2”. Would anyone know how I can
pull updated CLIENTNAME?

--
HS


"Soo Kuan Teo [MSFT]" wrote:

> This is very interesting scenario, can you please share with us what do you
> want to do after reconnect/disconnect a session?
> At the api level, you can try WTSWaitSystemEvent
> http://msdn.microsoft.com/en-us/library/aa383856(VS.85).aspx
> or WTSRegisterSessionNotification
> http://msdn.microsoft.com/en-us/library/aa383841(VS.85).aspx apis.
> Thanks
> Soo Kuan
>
>
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "HS" <HS@discussions.microsoft.com> wrote in message
> news:8EDEE24B-DFEC-4D49-BA24-04D530A0BF69@microsoft.com...
> > We are testing windows 08 TS. We want to be able to run script when a
> > user
> > reconnects to a disconnected session. Is it possible to detect reconnect
> > for
> > each session in TS08 then do something? There is an app called reconnAct
> > that works with TS03, we tried but it didn't work with TS08.
> >
> > All users are logging in from XPe and Linux Thin Clients.
> >
> > --
> > HS

>
>
 
Back
Top