Endpoint Central for Agent-Based Scan

Endpoint Central for Agent-Based Scan


AssetExplorer uses Endpoint Central agents (from build ≥ 6900) for scanning Windows, Linux, and Mac machines.

About Endpoint Central   

ManageEngine Endpoint Central (formerly Desktop Central) is a unified endpoint management system. Agents from Endpoint Central improve AssetExplorer's asset scanning functionality by fetching complete hardware details across Windows, Linux, and Mac machines. 

Endpoint Central Agent Features 

 
For fresh customers of AssetExplorer (build ≥ 6900)
For existing customers of AssetExplorer (migrating to build ≥6900) without Endpoint Central integration configured
For existing customers of AssetExplorer (migrating to build ≥6900) with Endpoint Central integration configured.
General Features
Agent-based inventory for Windows, Mac, and Linux machines

Warranty information for devices

Auto upgrade of agents to newer versions
Agent-based inventory for Windows, Mac, and Linux machines

Warranty information for devices

Remote control for Windows, Mac, and Linux machines

Auto upgrade of agents to newer versions
Agent-based inventory from Windows, Mac, and Linux machines

Warranty information for devices

Remote control for Windows, Mac, and Linux machines

Auto upgrade of agents to newer versions
Features on purchase of UEM Remote Access Plus Add-on  
Chat

Remote control

Wake-on-LAN

System manager  
Chat

Wake-on-LAN

System manager
Chat

Wake-on-LAN

System manager
 
   

Agent - Server Communication in Endpoint Central   

Scanning and remote control are done through the Endpoint Central server and its agents. The agent connects to the server upon installation and sends inventory data via HTTPS during startup and every 90 minutes until shutdown. Agents also use TCP to receive notifications for on-demand actions like instant scans and remote control.

Before enabling agent-server communication, a valid third-party SSL certificate should be applied in Endpoint Central. Click here for the steps to configure the SSL certificate in Endpoint Central.
 

OS supported by Endpoint Central Agents 

Windows OS
Windows Server OS
MAC
Linux
Windows 11
Windows 10
Windows 8.1
Windows 8
Windows 7
Windows Vista
Windows XP
 
 
Windows Server 2019
Windows Server 2016
Windows Server 2012 R2
Windows Server 2012
Windows Server 2008 R2
Windows Server 2008
Windows Server 2003 R2
Windows Server 2003
 
10.7 Lion
10.8 Mountain Lion
10.9 Mavericks
10.10 Yosemite
10.11 El Capitan
10.12 Sierra
10.13 High Sierra
10.14 Mojave
10.15 Catalina
11.0 Big Sur
 
Ubuntu (version ≥ 10.04)
RedHat Enterprise Linux (version ≥ 6)
CentOS (version ≥ 6)
Fedora 1(version ≥ 19)
Mandriva (version ≥ 2010)
Debian (version ≥ 7)
Linux Mint (version ≥ 13)
Open SuSe (version ≥ 11)
Suse Enterprise Linux (version ≥ 11)
Pardus (versions 17 and 19)
Oracle Linux Server (versions 6, 7, and 8)
 

Endpoint Central Agent Resource Utilization    

Endpoint Central agents consume approximately 1GB of disk space on the installed device.  
Agent Processes
Running application name
Bandwidth consumption
CPU consumption
Memory (RAM) consumption
At agent Idle state
dcagentservice.exe
dcondemand.exe
dcagenttrayicon.exe
 
(These processes are constantly running in the background on both Windows and Mac systems.)
1 Kbps
0-2%
11 MB
Refresh cycle
(90 minutes once)
dcconfig.exe
4KB
0-2%
6MB
Inventory scan
(At the scheduled time on the server)
dcinventory.exe
2MB
17-20%
14MB
Agent upgrade
dcconfig.exe
AgentUpgrader.exe
20MB
2-5%
3MB
 

Database Supported by Endpoint Central   

By default, Endpoint Central comes bundled with PGSQL and also supports MSSQL. Click here for a list of MSSQL versions supported by Endpoint Central. For detailed instructions on migrating Endpoint Central to MSSQL click here.

Procedure for AssetExplorer Running with Fail Over Service (FOS) Enabled  

Applicable to new customers of AssetExplorer and existing customers migrating to AssetExplorer build ≥ 6900 without Endpoint Central integration configured.

If FOS is configured for AssetExplorer, it will work for Endpoint Central too, but only if it's installed in the same folder as AssetExplorer and only if AssetExplorer is installed on a Windows machine. Click here for more details on FOS.

 

Steps to Install Endpoint Central and Deploy Agents     

Step 1: Download and Install Endpoint Central

For customers already using UEM products other than Endpoint Central 
If any of the following ManageEngine products are installed and used in your environment, we recommend you contact our support before proceeding with this installation for configuring changes in the asset inventory:  
  1. Patch Manager Plus On-Premise/Cloud  
  2. Remote Access Plus On-Premise/Cloud  
  3. Device Control Plus  
  4. Vulnerability Manager Plus  
  5. Patch Manager Plus Cloud  
  6. Endpoint Central Cloud
If Endpoint Central is purchased separately, please refer here for detailed hardware requirements. 
Endpoint Central requires a separate installation and is installed in the same folder as AssetExplorer. A minimum of 1GB disk space is required to install Endpoint Central.

Endpoint Central can be installed in two ways:
  1. Silent Installation
    Endpoint Central can be downloaded from Admin > Discovery > Agent Configuration in AssetExplorer. Internet access is required from the AssetExplorer server machine to download Endpoint Central. Upon installation of Endpoint Central, AssetExplorer is informed about the successful installation, and agents become available for download.

  1. Manual Installation  
    If the AssetExplorer server machine does not have internet connectivity or if it takes more than 90 minutes for Endpoint Central to be successfully installed, the process will time out. A manual prompt for installation will appear and the product can be downloaded and installed in EXE format.

Installing Endpoint Central if the AssetExplorer server runs on Linux or Mac OS:
Endpoint Central can only be installed on a Windows machine. If the AssetExplorer server runs on a Linux or Mac OS, Endpoint Central must be downloaded and installed on a separate Windows machine. Here, auto integration of AssetExplorer and Endpoint Central will not happen, and integrating Endpoint Central into AssetExplorer must be manually done from Admin > Apps & Add-ons > Integrations > UEM Products.
Endpoint Central is installed with PGSQL as the default database. For detailed instructions on migrating Endpoint Central to MSSQL click here. 
 

Step 2: Configure Agent settings 

Before downloading and deploying the agents on the client machines, it is essential to configure specific agent settings. For more information on agent configurations, click here.
 

Step 3: Ensure Ports used by Endpoint Central are Open 

Refer here for the Endpoint Central port details.
 

Step 4: Download Endpoint Central Agents on Windows, Linux, and Mac Machines 

After Endpoint Central is successfully installed and integrated with AssetExplorer, Endpoint Central agents for Windows, Linux, and Mac machines can be downloaded from Admin > Discovery > Agent Configuration as a ZIP file.

Step 5: Uninstall AssetExplorer Agents or Replace them with Endpoint Central Agents on Windows 

Only applicable to existing customers of AssetExplorer migrating to build ≥ 6900

Uninstall AssetExplorer Agents

You can uninstall AssetExplorer agents on Windows by executing the UnInstallAgent.vbs as a Group Policy Object (GPO) in Active Directory.

Follow the below steps to configure a GPO in Active Directory:
  1. Create a common network share path accessible to every machine on the network.
  2. Download and extract UnInstallAgent.vbs.
  3. From your domain controller, open the Group Policy Management Console by going to Start > Run or pressing Windows + R. Type gpmc.msc and click OK.
If gpmc is not installed in your Active Directory, install gpmc and proceed.  Click here to learn more.
  1. Right-click the domain and select Create a GPO in this domain and link it here.

  1. Specify a name for the GPO. Once the new GPO is created, you can see it in the GPMC in the left navigation pane, under Group Policy Objects.
  2. Right-click the GPO and click Edit. The Group Policy Management Editor will open.
  3. Expand Computer Configuration > Policies > Windows Settings > Scripts (Startup/Shutdown).

  1. Right-click Startup and click Properties.
  2. Click Show Files. Drag and drop the UninstallAgent.vbs file to this location and copy its path before closing. 
           Example: \Domain name\SysVol\Domain name\Policies\{ID}\Machine\Scripts\Startup\UninstallAgent.vbs 
  1. In the Startup Properties dialog box, click Add.
  2. Browse and select the UninstallAgent.vbs script or specify the copied path.
  3. Click OK. 
  4. Close the Add a Script dialog box and the Startup Properties dialog box.
The agents will be uninstalled automatically when the client computers power on.

Replace AssetExplorer Agents with Endpoint Central Agents

You can replace the AssetExplorer agents on Windows by executing ReplaceAgents.vbs as a Group Policy Object (GPO) in Active Directory.

Follow the below steps to configure a GPO in Active Directory:
  1. Create a common network share path accessible to every machine on the network.
  2. Download and extract the Windows Endpoint Central agent zip file.
  3. Save the UEMSAgent.msi and UEMSAgent.mst files in the network share.
  4. From your domain controller, open the Group Policy Management Console by going to Start > Run or pressing Windows + R. Type gpmc.msc and click OK.
If gpmc is not installed in your Active Directory, install gpmc and proceed.  Click here to learn more.
  1. Right-click the domain and select Create a GPO in this domain and link it here.
  1. Specify a name for the GPO. Once the new GPO is created, you can see it in the GPMC in the left navigation pane, under Group Policy Objects.
  2. To install agents on only select client computers, follow these steps:  
    1. Select the GPO and click the Scope tab
    2. Click Add in the Security Filtering section
    3. Click Object Types in the Select User, Computer, or Group dialog box
    4. Select the specific computer object types and click OK
    5. Specify the computer names
    6. Click Check Names and click OK
  3. Right-click the GPO and click Edit. The Group Policy Management Editor will open.
  4. Expand Computer Configuration > Policies > Windows Settings > Scripts.
  5. Right-click Startup and click Properties.
  6. Click Show Files. Drag and drop the ReplaceAgent.vbs file to this location and copy the path before closing. 
           Example: \Domain name\SysVol\Domain name\Policies\{ID}\Machine\Scripts\Startup\UninstallAgent.vbs 
  1. In the Startup Properties dialog box, click Add. Browse and select the ReplaceAgent.vbs script.
  2. Specify the Script Parameters as mentioned below if Endpoint Central uses HTTP mode for agent-server communication: UEMSAgent.msi UEMSAgent.mst 
When Endpoint Central is configured to use HTTP mode for agent-server communication, follow the methods below:
  1. If a valid SSL third-party certificate is uploaded on the server,  
    1. Add the DMRootCA.crt file along with the UEMSAgent.msi and UEMSAgent.mst agent installer files in the network share.
    2. Specify the script parameters as: UEMSAgent.msi UEMSAgent.mst DMRootCA.crt
  1. If an invalid or self-signed SSL third-party certificate is uploaded on the server,
    1. Add the DMRootCA.crt DMRootCA-Server.crt file along with the UEMSAgent.msi and UEMSAgent.mst files.
    2. Specify the script arguments as: UEMSAgent.msi UEMSAgent.mst DMRootCA.crt DMRootCA-Server.crt 
To add the SSL third-party certificate in AssetExplorer, go to Admin > Security Settings > Import SSL Certificates.
  1. Click OK to close the Add a Script dialog box and the Startup Properties dialog box.
  2. Close the Group Policy Object Editor.
The Endpoint Central agents will be installed automatically when the client computers power on.

Step 6 - Methods to Deploy Endpoint Central Agents in Windows, Linux, and Mac 

To be followed if Step 4 is not performed.
Windows
Linux
Mac





 
 

 
 
 

Step 7: Image a Computer with an Endpoint Central Agent 

The Endpoint Central agent has a unique ID that represents the machine with its name and system details. If more than one Endpoint Central agent is identified with the same ID, the details listed in AssetExplorer will be overwritten. This will result in listing details of only one computer, even though there are several computers with the same ID. To avoid this issue, image a computer with the Endpoint Central agent on it. 

Refer to the following links to learn more:
 

FAQs on Endpoint Central Integration 

If you're having trouble setting up Endpoint Central, we suggest taking a look at our FAQs.

    • Related Articles

    • Agent-Based Scan

      How does an agent-based scan work? Refer to the following link: UEM Agent What are the OS supported in the agent-based scan? The following Windows OS versions are supported: Windows 10 Windows 8.1 Windows 8 Windows 7 Windows Vista Windows XP* ...

    • FAQs on Agent-Based Scan

      How does an agent-based scan work? Please refer to this link for more details. What is the OS supported in the agent-based scan? Windows OS Windows Server OS MAC Linux Windows 11 Windows 10 Windows 8.1 Windows 8 Windows 7 Windows Vista Windows XP ...

    • Agent Configuration

      Agent-based scanning is supported for Windows, Linux, and Mac machines. Before proceeding with an agent-based scan, Endpoint Central has to be installed. Click here to learn more. Configure Endpoint Central agent settings in AssetExplorer under Admin ...

    • Extracting logs for Endpoint Central and AssetExplorer

      Extract Endpoint Central Log Files You can access the Endpoint Central server logs from the path below. <Install_Dir>\DesktopCentral_Server\logs Note: <Install_Dir> refers to the directory where the Endpoint Central server is installed. Extract ...

    • Mac Agent

      Role Required: Administrator Refer here for a list of the supported Mac OS versions. Install Mac Agent Manually Follow the steps mentioned below to install the Mac agent manually, Install the Endpoint Central agent on the computer intended for ...