Take over the Console via Terminal Services?

[yourISguy]

Can Terminal Services be configured so that I can take over the server's console remotely while allowing access to tech's onsite simultanesouly (poor man's pcanywhere)?

Both people would need to see the same screen.

Thanks everyone!

 

[PPettit]

I don't think there is a way to do what you ask via Terminal Server/Remote Desktop.

I've never used it, but I've seen lots of recommendations for VNC.

I just checked out Snapfiles.com (

http://www.snapfiles.com/reviews/TightVNC/tightvnc.html)

and TightVNC looks promising. The website (

http://www.tightvnc.com)

states:
free, GPL-licensed, with full source code available;
useful in remote administration, remote customer support, education, and for many other purposes;
cross-platform, available for Windows and Unix, compatible with other VNC software;
well maintained and being actively developed.

 

[58sniper]

I think you can as long as your BOTH connected to the box via a TS client. One cannot be at the console, as you cant remote control a console session.

Pat Richard, MCSE(2) MCSA:Messaging, CNA(2)

 

[markdmac]

If you install the Admin Pack it will give you a new Remote Desktops MMC Snap-In. This snap in gives you the ability to save multiple server login configurations and proveds a check box to allow you to remote control session zero which is the console.

Note however that when taking over the console the screen locally gets locked to prevent prying eyes.

If you are both logged in via terminal services, then you can use TS ADmin to remote control a TS session.

I hope you find this post helpful.

Regards,

Mark

 

[PPettit]

It seems to me that you might want to clarify your situation, yourISguy.

My understanding is that you will be connecting remotely (by executing something along the lines of "mstsc /console") while someone else will be sitting right in front of the server. You want the person at the server (who is currently logged on via the normal process and not via Remote Desktop) to be able to follow along with what you're doing. Is this correct?

P.S. After investigating it some more, I would advise against TightVNC unless you're using some other secure means to connect to the server (i.e. SSH). Apparently, TightVNC doesn't offer encrypted communication yet. It only encrypts the password to access the VNC service.

http://www.tightvnc.com/faq.html#howsecure

Although TightVNC encrypts VNC passwords sent over the net, the rest of the traffic is sent as is, unencrypted

 

[Andreh]

Windows XP/ 2003 has a great new tool built in for this sort of thing. I have used it before with great effect.

http://www.petri.co.il/offer_remote_assistance_in_windows_xp.htm

No need to use VNC anymore (though have used it alot in the past).


Goodluck



"Assumption is the mother of all f#%kups!

 

[PPettit]

I completely forgot about Remote Assistance. I've only used it once and that was a long time ago. We had pcAnyhwere which seemed to work a little better so I never gave it much thought again.

I bet Andreh is right. This would probably take care of your issue.

 

[tiwas]

Ever tried tightvnc? It's ok if you *must* control the console session, but apart from that it...I'm probably not allowed to say suck her, but the word I was thinking of is close to that. Reeeeeal close p

It's slower than rdp, and it's got less functions. Nice app for cross-platform work, though.

Lars Kvanum
alfa konsult - Proffe IT-tjenester til fornuftige priser

http://www.alfa-konsult.no