1 Overview
If the Remote Control Tool does not start when you connect to a computer, and you have followed the configuration steps in Remote Control Tool Configuration, you may take a look in the more detailed manual “External Tools Configuration”.
That manual describes how to configure the SoftwareCentral Client to launch programs such as the Remote Control Tool. The two checks below cover most cases.
2 Best practice
- Set the share path for every site. The Remote Control Tool Share Path (
CmRcViewer.exe) is entered per site under Settings › SCCM › Shares. A site without a path has nothing to start. - Only change the URI scheme option when you need to. Leave Manually register SoftwareCentral to a URI Scheme unticked unless you register the clients yourself: when it is unticked, SoftwareCentral registers itself on the clients.
- Make sure the users can read the share. The client starts the tool from the share, so a user without read access sees nothing happen.
3 Troubleshooting
| Symptom | Cause | What to do |
|---|---|---|
| The Remote Control Tool does not start | The Remote Control Tool Share Path for the site is missing or wrong, or the user cannot read the share. | Check the path under Settings › SCCM › Shares for the site, and that the user can read the folder that holds CmRcViewer.exe. |
| Clicking the tool in SoftwareCentral does nothing on the client | The client is not registered for the SoftwareCentral link type. This happens when Manually register SoftwareCentral to a URI Scheme is ticked, because SoftwareCentral then does not register itself. | Either untick the option, or register the client as described in External Tools Configuration. |
| Other external tools do not start either | The same URI scheme registration is used by the Remote Control Tool and Custom Tools. | Check the URI scheme registration first, then the tool's own settings in External Tools Configuration. |