Skip to main content

Installing the Combined Discovery + RDP Agent

The combined Discovery + RDP agent integrates asset discovery and remote desktop access into a single installation for Windows environments, simplifying deployment and reducing overhead.

note

Starting from Agent version 8.7.4, the Discovery and RDP Agents have been unified into a single agent. For standalone RDP-only agent installation (version 8.7.3 and earlier), see Installing the Standalone RDP Agent (Legacy) below. For all other agent installation instructions, refer to the Discovery Agent page.

Benefits of a Combined Installation​

Streamlined Deployment
  • Single Installation: Install both discovery and RDP functionality with one file
  • Reduced Complexity: Eliminate the need for separate agent installations
  • Consistent Configuration: Ensure both services use the same connection settings
Operational Efficiency
  • Unified Management: Manage both discovery and RDP capabilities from one agent
  • Simplified Updates: Update both functionalities together
  • Reduced Resource Usage: Single agent process for both services

Use Cases​

UserUse Case
IT Support TeamsNeed both asset discovery and remote access capabilities
System AdministratorsWant comprehensive asset management with remote troubleshooting
Help Desk OperationsRequire both asset visibility and remote support tools

Prerequisites​

This section covers the common prerequisites and Windows system requirements that apply to both the combined Discovery + RDP agent and the standalone RDP-only agent. For Linux and macOS standalone RDP agent requirements (such as Wayland configuration, supported OS versions, and SSL certificates), see the respective tabs in the Installing the Standalone RDP Agent (Legacy) section.

System Requirements​

Windows Systems​

  • OS: Windows 8 and above (32-bit & 64-bit)
  • Dependencies: .NET Framework 4+, Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019, and 2022

Required Information​

You will need the following details from your ServiceOps portal during installation:

  • ServiceOps Server URL: The web address of your ServiceOps instance.
  • Secure Auth Code: Found in Admin > Discovery and Agents > Agents > Agent Credential Profile. This is the required method for new installations.
  • Activation Code: (For upgrade scenarios only) Found in Admin > Organization > Account > License Details.
  • Protocol: HTTP or HTTPS, depending on your server configuration.

Pre-Installation Checklist​

1
RDP Server Ready
The RDP Server (MeshCentral) must be installed and configured within ServiceOps.
2
Asset Discovery
For RDP functionality to work, the target asset must already be discovered in ServiceOps (either through agent-based or agentless methods).
3
Network Accessibility
The ServiceOps server domain must be reachable from the target machine. If the server is not publicly accessible, add a host entry on the target machine mapping the server's IP address to its domain.
Hosts file location:
  • Windows: c:\Windows\System32\Drivers\etc\hosts
  • Linux/macOS: /etc/hosts
Syntax: {Live IP Address} {ServiceOps Server Client Domain name}
Example: 172.16.12.134 demo.motadataserviceops.com
4
Firewall Configuration
Ensure firewall rules are in place to allow outbound communication for discovery (Ports 8730, 8731, combined agent only) from the agent to the ServiceOps server, and bidirectional communication for RDP (Ports 80, 443, 8443) to and from the ServiceOps server.
5
Antivirus Exclusions
To prevent interference, exclude MotadataRemote.exe (located at C:\Program Files (x86)\Motadata\Motadata RDP WinServer\rdpapp\MotadataRemote.exe by default) from your antivirus scans. For example, if you're using Bitdefender Antivirus, refer to the document How to Exclude ServiceOps Agent from Bitdefender Antivirus Scan.
6
Add Folders
Add the rdpapp and Remote folders at the below locations if they do not exist:
  • C:\Program Files (x86)\Motadata\Motadata RDP WinServer\rdpapp
  • C:\ProgramData\Remote
note
  • The following ports are required for installing an agent: HTTP – 80, HTTPS – 443.
  • Communication will fail if the Agent Credential Profile used for installation is deleted or archived.

Combined Agent Installation on Windows​

The installation process for the combined agent is identical to the standalone Windows agent installation, with the key difference being the installer file you use.

1 Download the Combined Agent​

  1. Navigate to the Download Links section in your ServiceOps documentation.
  2. Download the latest Windows Combined Discovery + RDP agent (.msi) file (e.g., Motadata_ServiceOps_WinAgent_With_RDP_V8.x.x_x64.msi).
  3. Ensure you select the correct architecture (32-bit or 64-bit) for the target system.

2 Run the Installation Wizard​

  1. Right-click the downloaded .msi file and select Run as administrator.
  2. When the User Access Control (UAC) prompt appears, click Yes.
  3. The installation wizard will launch. Click Next to begin.

3 Configure Connection Settings​

  1. In the server configuration screen, enter the following:
    • URL: Your ServiceOps server URL.
    • Port: Leave this blank to use default ports (80/443) or enter a specific port if required.
    • Protocol: Select HTTPS (recommended) or HTTP.
  2. Click Next.

4 Provide Authentication Details​

  1. Select the Secure Communication option.
  2. Enter the Secure Auth key obtained from the Agent Credential Profile in ServiceOps.
  3. Click Next.

For new installations, the Activation Code method is not supported.

5 Complete the Installation​

  1. Click Install to start the installation process.
  2. Once the installation is complete, click Finish to exit the wizard.

Post-Installation Verification​

After installation, it is crucial to verify that both Discovery and RDP components are functioning correctly.

1 Verify Service and Program Installation​

  • Check that the agent appears in Control Panel > Programs and Features.
  • Open the Services application (services.msc) and confirm that both the Discovery and RDP agent services are running.

2 Verify Portal Registration​

  1. Log in to your ServiceOps portal.
  2. Navigate to Discovery > Agents. Confirm the new device appears in the list with an "Online" status.
  3. Navigate to Admin > Asset Management > RDP Configuration > RDP Agents. Confirm the new device also appears in this list.

3 Verify Discovery Functionality​

  1. Asset Discovery: After installation, allow time for the agent to complete its initial discovery cycle (typically runs every 60 minutes, or can be manually triggered from the ServiceOps portal if available).
  2. Asset Registration: Check that assets are being discovered and appear in the Hardware Assets list.
  3. Asset Information: Verify that detailed asset information is being collected.

4 Verify RDP Functionality​

  1. Wait for Registration: Allow 5-7 minutes after installation for the RDP agent to fully register with the RDP server before attempting a connection.
  2. Establish Connection: Try to establish an RDP connection from the ServiceOps portal.
  3. Verify Session: Ensure the RDP session connects successfully without errors.
  4. Test Features: Verify RDP features like screen recording and session management.

Configuration Best Practices​

RDP Server Setup
  • Install RDP Server: Install the MeshCentral RDP server
  • Configure RDP Settings: Set up RDP configuration in the ServiceOps portal
  • Test Connectivity: Verify communication between RDP server and agents
Network Configuration
  • Firewall Rules: Configure firewall rules for both discovery and RDP communication
  • Port Access: Ensure required ports are accessible (80, 443, 8443)
  • SSL Certificates: Configure SSL certificates for secure communication
Security Considerations
  • Antivirus Exclusions: Exclude MotadataRemote.exe from antivirus scans
  • File Permissions: Ensure proper file permissions for both discovery and RDP components
  • Authentication: Use strong authentication methods for both services

Performance Considerations​

Resource Usage​

  • Memory: Combined agents use more memory than individual agents
  • CPU: Both discovery and RDP processes run simultaneously
  • Network: Increased network traffic for both discovery and RDP communication

Optimization Tips​

  • Deploy During Off-Peak: Install during low-usage periods
  • Monitor Resources: Keep track of system resource usage
  • Configure Schedules: Set appropriate discovery and RDP session schedules

Uninstallation​

Windows Agent​

  1. Use Programs and Features to uninstall
  2. Or use the command line: msiexec /x [agent-msi-file] /quiet
  3. Once the agent is uninstalled, delete the agent directory (WinAgent) from the path C:\ProgramData\Motadata.

Troubleshooting​

See the Troubleshooting section at the end of this guide, or refer to the RDP Installation and Troubleshooting guide for detailed help.

Installing the Standalone RDP Agent (Legacy)​

This section covers installation of the standalone RDP-only agent on Windows, Linux, and macOS. Use this only if you are on Agent version 8.7.3 or earlier. For all new deployments, use the Combined Discovery + RDP Agent instead.

Before continuing, review the Prerequisites section for required ServiceOps information and the pre-installation checklist. OS-specific system requirements are listed within each platform's tab below.

Installation Methods​

ServiceOps provides multiple options for installing RDP agents. Choose the method that best suits your environment:

Windows RDP Agent Installation​

System Requirements​

Refer to the Windows Systems requirements in the Prerequisites section above.

1 Download the Agent​
  1. Navigate to the Download Links section in your ServiceOps documentation
  2. Download the latest Windows RDP agent (.msi) file
  3. Choose the appropriate version (32-bit or 64-bit) for your system
2 Run the Installation​
  1. Run the .msi file with administrator rights
  2. The User Access Control popup will appear - click Yes to continue
  3. Follow the installation wizard

3 Configure Connection Settings​
  1. Click Next to proceed with the installation
  2. Enter the following details:
    • URL: Your ServiceOps server URL
    • Port: Leave blank for default ports, or enter specific port (443 for HTTPS)
    • Protocol: Select HTTP or HTTPS based on your configuration
4 Enter Authentication​

Choose one of the following authentication methods:

For Upgrade Scenarios​
  • Secure Communication: Enter the Secure Auth key from Agent Credential Profile
  • Activation Code: Enter the activation code from License Details
For New Installations​
  • Secure Communication: Enter the Secure Auth key from Agent Credential Profile

  • Activation code feature will not work for new installations

5 Complete Installation​
  1. Click Install to begin the installation process

  1. Wait for the installation to complete
  2. Click Finish when the wizard completes

6 Verify Installation​
  1. Check that the agent appears in Programs and Features
  2. Verify the agent appears in the RDP Agent tab of the RDP Configuration page
  3. Confirm the agent is listed in your ServiceOps portal.

Post-Installation Verification (Standalone RDP Agent)​

Check Agent Status​

  1. Windows: Check Services app for the RDP agent service
  2. Linux: Use systemctl status motadata_rdpwrapper.service
  3. macOS: Check LaunchDaemons for the RDP agent service

Verify Portal Registration​

  1. Log into your ServiceOps portal
  2. Navigate to RDP Configuration > RDP Agents
  3. Verify your agent appears in the list
  4. Check that the agent status shows as "Online"

Test RDP Functionality​

  1. Wait for Registration: Allow 5-7 minutes after installation before testing
  2. Establish Connection: Try to establish an RDP connection from the ServiceOps portal
  3. Verify Session: Ensure the RDP session connects successfully without errors

RDP Server Integration​

Proper integration with the RDP server is crucial for enabling remote access. This section outlines the key requirements and deployment options.

Prerequisites
  1. RDP Server Installation: Install the MeshCentral RDP server
  2. Configuration: Configure RDP settings in the ServiceOps portal
  3. Network Access: Ensure proper network connectivity between RDP server and agents
Deployment Options
  • Local Deployment: RDP Server and ServiceOps Server on the same machine
  • Remote Deployment: RDP Server and ServiceOps Server on different machines
Port Configuration
  • Local Connection: Port 8443 must be enabled
  • Remote Connection: Port 443 is used
  • Database Access: Port 5432 for database connectivity

Next Steps​

After successfully installing RDP agents:

  1. Configure RDP Settings: Set up connection types and security settings
  2. Test Remote Access: Verify RDP sessions work correctly
  3. Set Up Monitoring: Configure alerts for RDP session events
  4. Deploy Additional Agents: Install RDP agents on remaining target machines

For detailed configuration options and advanced settings, refer to the RDP Configuration guide in the Core Concepts section.

Troubleshooting​

This section covers common issues for both the combined Discovery + RDP agent and the standalone RDP agent above.

For a more detailed guide on resolving RDP-related problems, refer to the RDP Installation and Troubleshooting guide.

Installation fails, rolls back, or shows "Permission denied"
Solution:

Ensure you are running the installer with administrator (Windows) or root (Linux/macOS) privileges. For the combined Windows agent, also check that all prerequisites (especially the .NET and Visual C++ dependencies) are met.

Agent does not appear in the portal / cannot connect to the ServiceOps server
Solution:

Verify the URL, port, and protocol settings entered during installation. Check for network connectivity issues or firewalls blocking communication between the agent and the ServiceOps server.

RDP connection or session fails to establish
Solution:

Confirm the RDP Server (MeshCentral) is running and properly configured. Double-check that the asset was discovered before the RDP agent was installed, and that all required firewall ports are open.

Authentication issues (invalid activation code or secure auth key)
Solution:

Double-check the codes from your ServiceOps portal: under Agent Credential Profile for the Secure Auth key, or License Details for the Activation Code.

Firewall issues
Solution:

Configure firewall rules for the required ports (80, 443, 8443, and 8730/8731 for discovery on the combined agent).

Antivirus blocks the agent
Solution:

Exclude MotadataRemote.exe from antivirus scans, as described in the Prerequisites section above.