A common issue encountered by Support Teams when using ControlUp for remote session management is the challenge of releasing the session control guard when a user’s device experiences network issues. In such scenarios, the support agent is often disconnected and attempts to reconnect to the remote session can fail or be significantly delayed, especially during active phone support sessions. This delay can hinder timely assistance and prolong user downtime.
The root cause stems from the remote control session remaining locked or guarded by the ControlUp client process, preventing immediate reconnection or takeover of the session. To resolve this, a practical workaround involves terminating the ControlUp Remote Control process associated with the session on the support agent’s device. Specifically, killing the process named CU_RC.exe frees the control of the remote session, allowing the agent to reconnect without the usual delays caused by the locked session state.
This method has been verified by multiple users within the community as an effective way to release the session control guard promptly. It is recommended as a quick and straightforward action in cases where network instability disrupts remote control continuity. Teams are advised to share this approach as a standard troubleshooting step to minimize downtime during remote support sessions.
It should be noted that forcibly terminating the CU_RC process might interrupt an ongoing session and should be performed with clear communication to the end-user. Additionally, this technique is applicable in environments using current versions of the ControlUp Remote Control feature and may need adaptation if underlying product updates change process names or behaviors.
For more detailed information on managing remote control sessions in ControlUp and handling connectivity issues, users can refer to ControlUp’s official documentation and knowledge base at https://docs.controlup.com or explore training resources at https://cuacademy.controlup.com.
Read the entire ‘How to Release Remote Control Session Guard in ControlUp During Network Issues’ thread below:
Hi all, just curious if there’s a way to release the session control guard? When a user’s device is having network issues, we often get kicked off and then attempt to reconnect, but this doesn’t always work immediately/soon enough whilst on the phone, is there any command/way in CU to release the Remote Control for the active user/session.
Kill the CU_RC process
Thanks Eugene!
Worked for you?
Yes thank you
Sharing this with my team as well – thanks for the idea
Continue reading and comment on the thread ‘How to Release Remote Control Session Guard in ControlUp During Network Issues’. Not a member? Join Here!
Categories: All Archives, ControlUp for Desktops
