Re: Shadow user seesions via Terminal Server Manager

I think perhaps you misunderstand my post; a user on a third machine is
shadowing the session, but they were doing so from TSM on the SBS server by
using the "remote control" option which is built into the app. This did
indeed work; we used it for many months. I was not the one who originally set
this up; all I know is that at some point during our watch, it stopped
working. I used to be able to list all the machines, expand the list and
shadow the sessions via TSM; the list of machines is still there, but now all
I get is "You could not be authenticated on this server."

Regardless, none of the methods noted in the tech bulletins work, either.
That suggests there is something more to this than the obvious.

The bottom line is that I want an outside vendor to be able to shadow
sessions on XP Pro machines. We did this is the past, and I have no idea why
it no longer works. VNC is not exactly secure, and buying licenses for
PCAnywhere is a costly option.

Any other ideas?

BA



"Frank McCallister SBS MVP" wrote:

> You can't Shadow TS sessions on XP boxes, only on the Server itself. To
> watch users on Workstations you need to use Remote assistance or a Third
> party Web based product.
>
> --
> Frank McCallister SBS MVP
> COMPUMAC
> "BA" <BA@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:34C43245-A3DB-443C-A5CA-C39C68CCD877@xxxxxxxxxxxxxxxx
> >I am having a problem w/ shadowing user sessions via Terminal Server
> >Manager,
> > and the tech bulls do not help (and 1 is actually inaccurate).
> >
> > One of our customers runs SBS 2003, and they used Terminal Server Manager
> > to
> > allow a 3rd party software vendor to access and shadow user sessions (to
> > watch them replicate errors). They would access the server, open TSM,
> > click
> > the user machine and then select "remote control." But for some reason,
> > this
> > has stopped working, even though RDP and RWW connections still work fine.
> > Whenever I try to access any of the XP Pro workstations through TSM, I now
> > get "You could not be authenticated on this server." I have admin rights
> > on
> > every box in the network.
> >
> > Tech bull 320191 doesn't work; when I enter "shadow #" (or "shadow
> > rdp-tcp#xx") I get error code 7050, stating that the seesion is either
> > disconnected or there is no user logged on (incorrect in both cases). Tech
> > bull 278845 says to eliiminate the -console parameter, but when you do
> > that,
> > you are forced to login--thus knocking the user off (which means you
> > cannot
> > shadow the session). I followed the steps in tech bull 232792, but this
> > had
> > no effect; in any event, Domain Admins already had full control
> > permissions.
> > I also read tech bull 281307; the machines are indeed listed in TSM, but I
> > can't connect to any of them other than the server I am already on.
> >
> > How can I restore the ability to shadow user sessions via TSM? More
> > specifically, what are the necessary permissions/settings for accessing
> > machines remotely via the TSM? All of the lit I've read on TS is oreinted
> > toward setting up a thin-client network, something we won't be doing, and
> > in
> > any event, can't be done on a SBS 2003 server.
> >
> > Any assistance you can offer is much appreciated.
> >
> > BA
> >
>
>
>
.

Relevant Pages

  • Re: Shadow user seesions via Terminal Server Manager
    ... but they were doing so from TSM on the SBS server ... > shadow the sessions via TSM; the list of machines is still there, ... > sessions on XP Pro machines. ...
    (microsoft.public.windows.server.sbs)
  • RE: EIF: Trace Session Manager service warning on startup
    ... I did as you suggested and -- as before -- the TSM ... re-loads the config file fine when I disable/enable sessions while it is ... > Files\Microsoft Enterprise Instrumentation\Bin\Trace ...
    (microsoft.public.vsnet.enterprise.tools)
  • RE: Shadowing Terminal sessions
    ... Have you looked at the native SHADOW command (command prompt utility to ... detect sessions and start a shadow. ... Microsoft Terminal server which serves as a gateway. ...
    (Focus-Microsoft)
  • Re: How can i find my server is taken in Remote?
    ... connection - remote and allow users to see sessions ... I did enable it but unable to see any sessions on the Remote Desktop server itself. ... I just found out that I must create another remote session to the same Remote Desktop server and shadow the session ID that I want to view by issuing command "shadow ID#" ...
    (microsoft.public.windows.server.general)
Quantcast