This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
BMC Client Management
BMC Client Management (BCM) >= 12.8
I want to take control of devices that don't have an agent on, how can I do?
Remote control of an end user's desktop usually requires that a BCM agent is installed on that desktop. Through the web console, a helpdesk admin can remotely control a device on which a BCM agent is not installed. The remote control feature is supported on Windows and macOS systems.
1- Prepare the configuration
- Connect to the heavy or to the web start consoles in this Knowledge Article (KA): Client Management: How to connect to the master using the Web start console - INCLUDES VIDEO
- Setup a DMZ relay. To use the agentless remote control it should be sufficient to open the agent ports on the DMZ (1610 and 1611 by default).
- Create or update a rollout configuration:
To remotely control devices that do not have a BCM agent, BCM provides 3 rollout packages out of the box:
- Select the rollout configuration (here "Remote Control 64 bits")
- Go to the sub-node Agent Configuration > Security (1)
- Compare the settings on the right pane with the settings in Agent Configuration > Security on the master - If they differ, fix the settings in the rollout to match the ones of the master
- Go to the tab "Communication":
- Set the public ip or the public FQDN of the DMZ relay. For this example the master is not in a DMZ, but a relay has been setup as a DMZ relay.
- Go to the sub-node "Servers", then click on "Assign Rollout Server":
- Assign the relay that was set as a static relay to be the rollout server for this configuration
- Set the network interface that it will listen to:
The network interface should be the network interface that has access to the internet.
- Right Click on the server name on the left (or on the line on the right pane):
Wait for it to change to the status to be "Available".
2- Connect to the web console
Check the following KA to learn how to connect to the web console and learn about its available functionalities: Client Management: How to connect to the master using the Web console.
3- Send the remote control on request invite to the end-user
- Generate the invite:
(1) Select the remote control on request rollout configuration that was generated in step 1 by its friendly name (see schreenshot #4)
(2) Click on "Generate"
(3) Select the type of invitation that should be generate:
- "URL of the Remote Control package" will generate a link that will not require any extra steps from the end-user
(5) The invite is listed:
The end-user will have to:
- Open the link in the browser
In this example the basic link was sent, and the helpdesk admin shared the token id with the end-user by phone:
- Type the token then click on "Download"
- Double-Click on the exe file that he just downloaded to his computer
A popup from Windows might show-up to show the app is unrecognized:
- click on "More info"
- click on "Run anyway"
- The mini agent will display a popup when the install is done:
Do NOT click on "Quit". This popup will be closed when the remote session on this device will start successfully.
5- Start the remote session
Back to the admin web console: when the mini agent will have been installed it will send an identity to the relay. From there the admin will be able to start a remote session by clicking on the "play" icon:
(1) is the actual screen of the target
(2) is the list of the devices being remote controlled by this admin.
If there are also BCM Clients on the WAN there would be extra configuration to set the DMZ relay. More information in the following KA: Client Management: Managing Devices Across the Internet with Client Management.
More information in the official documentation here (12.9)