When remote controlling TS sessions, screen flickers and data is erased of System

  • Thread starter Thread starter Brett Brown
  • Start date Start date
B

Brett Brown

Hi,

We have set up that an observing user can remote control any user
logged onto a TS, mainly our call centre users, who are all using thin
clients. The problem is when we establish the remote control the
screen flickers and when we have our in house app open and data is
being inputted into the system, the screen flickers and if they are
typing in data it erases it. As soon as the screen flickers our users
know that they are being monitored and resume their work. Is there any
way around this???

Thanks
 
Hi Brett,
The problem is when we establish the remote control the
screen flickers
Click to expand...

as a _workaround_ I would tell the observing user to open on his PC one
session for each user to be checked and have the session run all day
long. So, the observing user has to switch the session on his PC. Make
sure the windows-shortcuts work only locally (Remotedesktop
connection/options/local ressources/keyboard) so that the observer can
ALT-TAB between the users.

arno
 
PS: In the logon/logoff-scripts of the users you could have a net send
message to inform the observer (PC) about who logged in and out.
 
arno said:
PS: In the logon/logoff-scripts of the users you could have a net send
message to inform the observer (PC) about who logged in and out.
Click to expand...

See the thing is our call centre during the year is only about 30 ppl,
around christmas its upwards of 150. Her job is just the view the
session and make sure they are working, but if they see their screen
flicker then they all know they are being watched. Big mouths who
found out this have now told all of our new temps
 
Hi Brett,

this is why I say:

the observer goes to his PC and opens one RDP-Sessions for each user to
observe when the uer logs on! In each session you observe one user.
This is the contrary of opening one RDP Session and within that session
you observe userA, then UserB etc. which will cause the flickering when
you actually change the user.

With my workaround the users will see the flickering once in the
morning, however, all day long they will not know when the observer is
really watching them.

regards

arno
 
As much as your trying to help its not going to help. Think about it,
she has 150+ users coming into the call centre. Try flicking between
150 different sessions, its not going to happen, but your help is
appreciated, thanks

Brett
 
As much as your trying to help its not going to help. Think about it,
she has 150+ users coming into the call centre. Try flicking between
150 different sessions, its not going to happen, but your help is
appreciated, thanks
Click to expand...

This is why my "solution" is just a workaround - still better than
nothing. Simply use more than one RDP session at a time. Make sure
everyone hears when you find somebody doing nothing.

Did you think about some sort of spyware (keylogger)?

arno
 
Back
Top