Does anyone know how to clear the above error message without having to reboot. Rebooting must be restarting a service or something somewhere that if we knew what, we could do remotely and then be able to remote on without having to reboot the machine. Does anyone know how this can be acheived?

Hi, You could try restarting the SMS Agent host.. Regards, Jrgen-- My System Center blog ccmexec.com -- Twitter @ccmexec

Have tried that and stopping and restarting the host makes no difference.

Further to this, if i test a connection to a machine that operates fine, it has the RCAgent.exe process running. Killing that shuts down the remote session and continues to work next time. However on the machine in question that has the above error, they dont have a RCAgent.exe running but do have RCServer.exe running. Could this be the cause? I havent attempted to shut it down as its a users live machine and dont want to affect anything unrelated.

Hello, is this issue on one Particular machine ? Or is this something thats affecting multiple machines in multiple collections. if this is an issue with one Machine,you can uninstall and re-install the CM client and that should help you resolving this.You can also check remotecontrol.log on the client to help you get in deep with this issue. let me know if this helps. Thanks Arvind

It is an issue that crops up every now and then on multiple machines. It may well be that the client needs repairing or reinstalling to prevent it from reoccuring but in the short term, I am looking for a way to clear the session remotely, enabling me to logon.

OK.So these are the things you can do. But just to be clear,Are you sure you are connecting to the system you think you are connecting to? Have you verified DNS resolution from the system you are initiating the remote tools viewer from actually resolves the IP of the system yout think you are controlling? The next logical steps are Try giving 'users' read access to HKLM\SOFTWARE\Microsoft\SMS\Client\Configuration\Client, then restarting the workstation. Have you tried RDP/Remote Assistance on these machines and do they work correctly ? Can you check the WMI ? May be perform a basic check on WMI. You can check this http://blogs.technet.com/b/askperf/archive/2007/06/22/basic-wmi-testing.aspx to know the Basic TS steps. Do you have any Firewall issue,Is there a possibilty that you could have an exception created allowing RCagent.exe over firewall ? These are the steps that i could think of.Let me know if these help.As far as i understand,if these things dont resolve this issue,then the next logical step will be to Re-install the SM client on the machines or have them re-imaged if the reinstall dont work. Thanks Arvind

Thank you very much for this Arvind BS. These could be steps to look into the root cause of the issue but not for the actual question. My goal is to find out what service or process is running that I can kill without having to restart the machine so I can then remote into it via the SCCM console. If i ever get that answer I can do what I need to, and then look into the above suggestions to avoid the issue repeating.

Thank you very much for this Arvind BS. These could be steps to look into the root cause of the issue but not for the actual question. My goal is to find out what service or process is running that I can kill without having to restart the machine so I can then remote into it via the SCCM console. If i ever get that answer I can do what I need to, and then look into the above suggestions to avoid the issue repeating. I'm not near a ConfigMgr Client at the moment. Why don't you do a few tests with two local machines and start a remote session then examine the processes hogging the CPU on the remoted machine?

Thanks SMS Marshall. I have attempted this and mentioned above that I found RCAgent.exe present when I had an active session. The machine in question though didnt have this but did have RCServer.exe running. Do we know if they are related and could that be a cause on that machine specifically?

Thanks SMS Marshall. I have attempted this and mentioned above that I found RCAgent.exe present when I had an active session. The machine in question though didnt have this but did have RCServer.exe running. Do we know if they are related and could that be a cause on that machine specifically? I'm in contact with ConfigMgr Clients today, I'll have a look for you ...