Recommended Posts

Hello Everyone ,

Im running a Win2k srv with Xp clients all over the place. Now what i want to be able to do is make use of the Remote desktop services. I want to be able to troubleshoot clients with issues in real time - i however do not want to use remote assitance. I dont want the user to see what i am doing and i do not want to take control over the users session. I want to create a remote session behind their own session. Thats cool i know what i want, now with remote desktop connections i can connect to clients computers but only in console mode - this isnt realy what i want as i feel its too intrusive and if i wanted to kik off the user to fix the computer i might aswell go down to their floor/room myself and do it.

Ive also tried the command line tool MSTSC

MSTSC /v:<compname> /console

now that as you might imagine get me a console session. that works.

MSTSC /v:<compname>

this gives me the same result

I have seen this working in a win2k3 course i did - and i was wondering if its a Win2k3 thing - or something i could download for win2k? However in the course i saw this working we were all member servers not XP clients - would that make a difference? As far as i now you canhave 2 concurrent sessions going with both clients and server.

Any one got any ideas? And can anyone tell me why i have to kik offusers to use their computer remotley? thanks in advance.

Link to comment
https://www.neowin.net/forum/topic/157145-remote-desktop-in-win2k/
Share on other sites

What you are talking about require the usage of Windows XP sp2, which is still in beta. Sp2 will allow you to accomplish what you need, but not with the current Sp1.

What you did in your win03 course is solely for win03. I believe someone made a thread which include some registry hack to accomplish what you are wanting without the need for sp2.

Thanks Guys

Ill be keeping an eye out for SP2 then - and just a quick Q bout VNC , as far as i now there are quite a few VNC's outthere whihc is the best?

And also - how do u kno whats going to be in the next Service Packs? lol sorry but id like to know where you get ur info please if thats coolio?

Thanks again fellas

I was not aware of being able to use VNC to create a session that is no the same as the users session(which is what I think you are after). If I am not mistaken, I think you are looking for a way to use a pro box similarly to TS. That way you can remote in and fix problems without the user even knowin you are in the box. That option may not be available in the final SP2, but there is a reg hack for it. THe main prob is that the RDP protocal only allows for one concurrent session which is why the current user gets kicked. THe reg hack will allow you to have multiple concurrent session like TS, however you would still be limited by the TCP cap of 10 concurrent connections. There are trd party apps to allow this, one is called WinConnect. The last time I tried to test it out, some mem leak ended up hoseing the system (had to reboot into safe mode anf kill the service then uninstall the app inorder to have any functionality of the machine). here is a link to a news thread... https://www.neowin.net/comments.php?id=16494&category=main

I think MS may have concurrents disabled by default in SP2 but since it is all reg hacking, you could create a gpo to hack all reg's in your domain and thus allow you to do just what you need.

0o0o creating GPO's sounds hard as nuts! Ive been reading about ADM files and stuff like that but it says you have toknow the software code and then know how to manipulate it urself - i know crap all bout Programming.

Do you know if and where there are prepackaged ADM's for Group policy say for like .... office 2k3? or remote dekstop? And is group policy extendable? or is it limited to some thing?

Thanks buddy

I have read too much of the details but the main difference between Remote desktop and WinVNC is that RD sends and recieves the draw commands from the OS. VNC essentiall grabs screenshots. In theory, Remote Desktop has the potential to be way faster than VNC. Plus, with the new remote desktop in XP and 2003 you can connect local printers and drives to remote sessions which was a pain to do before (also a pain with VNC)

As far as the GPO goes, they are not hard to make. as long as you knwo the registry key that needs to be changed, you can do it. THe ADM file simply tells what key is to be changed and what options you can change it to. It is a simple txt file. When SP2 officially comes out, we can make an ADM for this together cause I would love to use this at my job too.

  Billprozac said:
I have read too much of the details but the main difference between Remote desktop and WinVNC is that RD sends and recieves the draw commands from the OS. VNC essentiall grabs screenshots. In theory, Remote Desktop has the potential to be way faster than VNC.

Why don't you just try UltraVNC and find out for yourself?

http://ultravnc.sourceforge.net/

I do use both and have found that Remote desktop is much more efficient especially if you are using high resolutions, but there may be a way to configure it better than I have it. I must say, the best reason for UltraVNC before RDP was the web interface, bu tsince you can use TSWeb or the fact that all computer running XP have the TS client makes this point almost moot.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.