• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

RDP and Windows XP - multiple sessions

multiband8303

Senior member
Have some users on the LAN - that get cranky when I use VNC - I want to be able to RDP into them without breaking there session - they are on a non server OS - Windows XP - is this possible?
 
Originally posted by: InlineFive
If you are using a workgroup network, no. If you are using a domain network, yes.

Domain versus non domain does not change the single session limit of XP Pro...at least as far as I know.

OP, depending on what you are doing, I would look into non GUI tools so you can script/do things remotely.

For instance, using psexec (from the pstools by systernals) I can grab cmd.exe from the remote machine and do what I need using netsh often times. Or setup a batch file to run, and then copy the file to the remote machine and use psexec to call that file.
 
Originally posted by: nweaver
Originally posted by: InlineFive
If you are using a workgroup network, no. If you are using a domain network, yes.

Domain versus non domain does not change the single session limit of XP Pro...at least as far as I know.

OP, depending on what you are doing, I would look into non GUI tools so you can script/do things remotely.

For instance, using psexec (from the pstools by systernals) I can grab cmd.exe from the remote machine and do what I need using netsh often times. Or setup a batch file to run, and then copy the file to the remote machine and use psexec to call that file.

Well with a domain you can initiate Remote Assistance sessions. Which are more useful for helping end users, IMHO.
 
I agree with Inline Five...

We have (most) of our workstations (in our domain) on WinXP. We can use Remote Assitance to log into their machine (without kicking them out) and watch what they are doing to help troubleshoot the issue.

Go to the Start\Help and Support, click on "Use Tools to view your computer information and diagnose problems", click on "Offer Remote Assistance", and type in the computer name or IP address. Pretty simple from there...

AFAIK, you have to be a local administrator (or Domain admin) to do this.
 
Based on the fact that you say they get cranky, I am assuming you want to RDP into their system without sharing their desktop.

If this is the case, then you can probably get away with using the old termserv.dll and also a few registry tweaks. I know this to be true as I have 6 concurrent connections to my XP box right now with different users each with their own desktop

If your situation is not what I describe then using Remote Desktop Assistance is the only way without purchasing 3rd party software.

TheSophist
 
I don't know where you work, but using hacked dlls and other "tweaks" that violate MS licensing is a definite no no at most places...
 
Originally posted by: mrbill14
I agree with Inline Five...

We have (most) of our workstations (in our domain) on WinXP. We can use Remote Assitance to log into their machine (without kicking them out) and watch what they are doing to help troubleshoot the issue.

Go to the Start\Help and Support, click on "Use Tools to view your computer information and diagnose problems", click on "Offer Remote Assistance", and type in the computer name or IP address. Pretty simple from there...

AFAIK, you have to be a local administrator (or Domain admin) to do this.

how is that any different then using VNC?
 
The .dll is not hacked.
The registry modification can also be done through the group policy mmc, via Microsoft's own interface, it is not hidden.

In terms of licensing, if it is illegal, then I don't recommend it. Keep in mind that by this reasoning, VNC is illegal as well.
 
Back
Top