• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 455
  • Last Modified:

Using Remote control within a users RDP session

Hi All,

We run windows server 2003 standard edition in the office and have a  single remote user using a windows 2000 PC with Microsoft RDP client installed.

All works fine and within the server "Terminal services Manager" I can see the user has logged in and can log then off, reset their connect etc.

I would like to view what they are doing sometimes, but the remote control option is grayed out. I have tried enabling the remote control option in their account policy (within active directory), but the option is always grayed out.

Am I doing something wrong or do I need to buy terminal server licenses?

C
0
chris_msl
Asked:
chris_msl
  • 5
  • 4
  • 2
  • +1
1 Solution
 
chris_mslAuthor Commented:
ps. sorry it's only 200 points, but I dont have many left.
0
 
PberSolutions ArchitectCommented:
0
 
chris_mslAuthor Commented:
Hi Pber,

Have followed instructions, and also ensured the user has remote control ticked and does not require permission.

Still no remote control lit up.

Any other ideas?

C
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
PberSolutions ArchitectCommented:
You need to logon the box the user is remoted on and then click Remote control.  You can't load terminal services manager from your machine and connect to your terminal server box and perform a remote control.  You must load the terminal service manager from the box being terminal served.





0
 
chris_mslAuthor Commented:
Not sure if I understand that.

I am sitting on the Win2003 server that runs terminal services manager and am trying to remote control the remote users session

I've explained that very badly, will try again:--

Box_A = Win 2003 server running terminal services
Box_B = Remote user sitting at a windows 2000 client box who is connected to Box_A using RDP client.

I am sitting at Box_A trying to view/interact with the session.

Hope this makes sense?

C
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
If the client machines are XP SP2, then this is blocked.  You need to add the following to the workstation's registry:

regkey: "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server"

Add a value named "AllowRemoteRPC", type "REG_DWORD" and Value Data = "1"

Jeff
TechSoEasy
0
 
DaMaestroCommented:
Has the Remote Control Addin been registered in AD? rcontrolad has to be installed and registered in the directory before that option will become available

Remote Control Add-on for Active Directory Users & Computers
http://www.microsoft.com/downloads/details.aspx?FamilyID=0A91D2E7-7594-4ABB-8239-7A7ECA6A6CB1&displaylang=en
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
All that does is add Remote Control to the Shell's Right Click menu... it's the same thing as going to Terminal Services Manager and requesting remote control.  If you don't have the registry set right on the remote workstation, that wouldn't make it any better.

Jeff
TechSoEasy
0
 
DaMaestroCommented:
~I would like to view what they are doing sometimes, but the remote control option is grayed out. I have tried enabling the remote control option in their account policy (within active directory), but the option is always grayed out.~  

I interpret this question as "why is Remote Control grayed out?" Answer - Remote Control has not been registered in AD.

Chris only wants to take control (or see) a session on the terminal server (Chris is at the server) in which a remote Windows 2000 desktop user is connecting remotely. Since the session takes place on the Terminal Server, for which Chris confirmed that the remote client can connect, there is nothing to do on the remote client. The remote client at this point is a shell.
0
 
chris_mslAuthor Commented:
Hi All,

Thanks for your suggestions. I have tried installing the software, but that still has not resolved the issue and the remote control option within "terminal services manager" is still grayed out.

I have also checked that the account has a tick in remote control as provided by the link from Pber, but still grayed out.

Also, just to clarify, DaMaestro interpretation on his comment of what I am trying to achieve is correct.

I am going to try a server reboot over the weekend just in case it helps, though any other ideas would be appreciated.

Chris
0
 
PberSolutions ArchitectCommented:
Back to the original article I posted above from windowsitpro, here a clip from the bottom.


Note: Remote Control doesn't work from the Console. You can't remotely control the session labeled Console. Remote Control's Protocol (RDP) works only with similar client protocols. For example, only RDP can remotely control other RDP clients.

Also see this:
http://support.microsoft.com/kb/q232792/
0
 
PberSolutions ArchitectCommented:
I hit submit too early.

Anyhow, that being said.  RDP into the server instead of logging onto the console.  Now let the user RDP into the server.  Both your sessions will need to be RDP-Tcp#?? for this to work.

See if you can get the Remote Control Feature now.
0
 
chris_mslAuthor Commented:
Hi All,

Many thanks for everyone's help on this. Pber is correct and remote does work when using remote control from 1 client to another and does not work from the server console itself (I didnt read the article link he sent me fully DOH!!).

Apologis for my error to the other helpers as well.

Sincerest thanks to all

Regards

Chris
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 4
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now