That's kind of the point of Remote Desktop.  You don't actually interact with the user's desktop, unless what you mean is that they've sent you a Remote Assistance ticket, in which case you would be looking at their active desktop.  Otherwise, as long as RDP is enabled on the client, and you are in the Remote Desktop User's group, or Admins, you can connect.

http://www.microsoft.com/windowsxp/using/mobility/getstarted/remoteintro.mspx

If it is xppro, you can telnet to it and work from a cmd prompt.

I believe telnet is disabled by default.  You'd have to enable it first on all computers you want to manage.

Are you guys familiar with NetMeeting? Would that help? If so, how would I connect to a machine?

Thanks

I have had a question about this subject. I have been hesitant to use Remote Desktop because when I initiate a session, it normaly give me a message that the user will be logged out and any unsaved data lost. I am interested in what leeym wants, a seperate session that does not disrupt the user, but lets me go in and check settings, etc.  

yes that's exactly what I want. to be able to logon to a remote computer without interrupting their session

Netop offers that but requires the user to, "allow" you into their active session. Very useful for remote troubleshooting.

http://www.netop.com/netop-1.htm

"Once you can accept the universe as matter expanding into nothing that is something, wearing stripes with plaid comes easy"
Albert Einstein

Netmeeting would also put you into the user's live session.

I have never seen the behavior that MillMaster is describing.  Are these users logged on locally, or are they also in RDP sessions?

I'm exploring NetMeeting now but am having trouble figuring out what 'Directory Server' to enter. Any thoughts if we have to do this over the Internet and through a firewall?

Try leaving it blank to start with.  Remember that NetMeeting does not like blank passwords so you have to have at least one user at admin level with a password.

where do I enter a password?

I just tried it with no directory server, tried connecting from another lan-based client, and there is an error message: the person you called only accepts secure Netmeeting calls.

Thoughts?

Also check out DameWare, you can install the service, launch and log in remotely, porvided your are a admin (local or domain).

Only the truly stupid believe they know everything.
Stu.. 2004

Windows XP is not a server - the licensing of XP allows one user may use it at a time - you cannot have one person work on the console and one person connect remotely.  

Service Pack 2 WAS to allow this, but Microsoft pulled the feature.

looks like Netmeeting is my only option. However, we need it to work within the LAN, but also across the Internet and a firewall. Does anyone have a site/document on how to implement this?

Thanks

Ok, this is what I am doing with Remote Desktop:

I am logged on localy to my PC.
I initiate the remote desktop app. and enter the IP address of the box I want to go to. (The box is XP Pro logged onto our domain)

The first thing it gives me is "cannot log you on using that name/password" and then shows me a standard xp logon screen.

I enter the domain admin name and password. It then says "The remote user will be logged off, any unsaved data will be lost, etc"

I say ok, then it says "remote logoff in progress"

I then see the remote desktop like I am suposed to, but the users screen shows "this computer has been locked by administrator/domainname"

How can I login without loggin the user out?

Quote:

How can I login without loggin the user out?

Netop.

"Once you can accept the universe as matter expanding into nothing that is something, wearing stripes with plaid comes easy"
Albert Einstein

You might be better off using Remote Assistance http://www.microsoft.com/windowsxp/using/helpandsupport/remoteassist/default.mspx

I just installed the RealVNC client on our workstations. That works fine since RDP logs the existing user out