I’m getting nowhere fast using Microsoft resources, so I’m going to put my faith in the Dope.
When I use remote desktop to control the system on the other side of the room it logs me out of the local session. Which wouldn’t be a problem if it logged me back in after I disconnect the remote session.
On my work systems when they use remote desktop to poke around we stay logged in on our local session. We can see what they’re doing and we can move the mouse too. Great fun to just knock the mouse when they’re about to click on something
Can anyone help me find where I set things up to work that way? I’m setting up a system next to my TV to play MPGS and AVIs etc on and I want it to stay logged in when I remote control it and start the next video.
Now, what has me confused is that you seem to be saying ‘local’ to mean the active login on the machine next to your TV, the one you want to play videos on. If that’s the case, then yeah, it’s going to log you off – only one session at a time on XP Pro, whether it’s remote, local, or smoke-cloud-relay.
If you mean, on the other hand, that whatever machine you’re sitting at is logging you out when you remote into the machine sitting by your TV… then I got nuthin’. That’s certainly not expected behavior. If that’s what’s happening, I’d start by checking to make sure you’re using it right, then escalate to a witch doctor and a dead chicken.
It’s not remote assistance. I’ve spent time in the company IT dept using their remote desktops to help setup our new invoicing system. It’s definitely not remote assistance because you can initiate it from the remote system without sending an invite from the host system.
Sofaspud you were right the first time. The second scenario would be uber-weird.
What you said about “Once session at a time” is true.
Effectively I just need two people to share control of that one session, not start an extra session. As you’ve mentioned it can be done with Remote assistance which would mean walking across the room to send a Remote Assistance Invitation. I want that functionality without having to get out of my chair.
Microsoft do say that you can start Remote Assistance sessions from the remote system without an invite being sent from the host system. However you need both systems linked to the same domain controller for that, and my server is not set up in that way. I suppose it could be but this solution would still be far too long winded to use regularly.
There are lots of programs out there I can use to get this done, I was just trying to avoid that when what I’ve got should be able to do the job.
Like MSFT said & like you see at work: Given a common domain infrastructure (& suitable configuration/GPO), Remote Assistance doesn’t need an invite from the assistee. Absent the infrastructure, it does.
If you can’t operate your infrastructure within the design of the tools you’ve got, you’re gonna have to go with a 3rd party tool that can work with what you’ve got. Sad to say, MSFT RA ain’t it.
Thanks everyone. It does seem that both my memory and my It dept are faulty and it was not Remote Desktop we were using to control the systems.
So, the question is: Which is more fun?
Setting my server up a Domain server and linking my three systems into it ?
Or setting up VNC ?
I think I’ll go with VNC. The work in starting a connection each time with Remote assistance seems like a lot of work when I’m gonna be doing it five times per night.