ServiceDesk Plus uses Endpoint Central (formerly Desktop Central) agents <from 11300> for scanning Windows, Linux, and Mac machines. The agent-based scan is made mandatory.
Steps for downloading and integrating Endpoint Central with ServiceDesk Plus/Asset Explorer are mentioned below. Choose and follow a method that suits your user type.
a. New customers of ServiceDesk Plus after BUILD NO 11300
Endpoint Central (formerly Desktop Central) is a robust unified endpoint management system. Agents from Endpoint Central improve ServiceDesk Plus' asset scanning functionality by fetching complete hardware details during the scan as well as maintain the uniformity of data fetched across Windows, Linux, and Mac machines. Endpoint Central agent integration also avoids the need to have two agents for users who already have integration between ServiceDesk Plus and Endpoint Central.
New customers of SDP (from ServiceDesk Plus version 11300 or newer) will have inventory and warranty features served from Endpoint Central for all SDP nodes. However, for features like remote control, chat, announcement, Wake-on-LAN, system manager, an add-on license has to be purchased. Once the add-on license is purchased, these features will be supported for the number of nodes purchased in the add-on.
All existing SDP customers with Endpoint Central integration enabled already (prior to ServiceDesk Plus version 11300) will have inventory, warranty, and remote control features served by Endpoint Central for all SDP nodes. So, if the number of nodes purchased in SDP is higher than the nodes in Endpoint Central, inventory, warranty, and remote control features will be supported for all SDP nodes. Other Endpoint Central features like Wake-on-LAN, system manager, announcement, chat, system tools, remote shutdown (which includes shut down, restart, hibernate, standby, and lock computers) would work for nodes purchased in Endpoint Central.
All existing SDP customers without Endpoint Central integration (prior to ServiceDesk Plus version 11300) will have inventory, warranty, and remote control features served from Endpoint Central for all SDP nodes. For features including chat, announcement, Wake-on-LAN, system manager, an add-on license has to be purchased. Once the add-on license is purchased, these features will be supported for the nodes purchased in the add-on license.
Endpoint Central (formerly Desktop Central) agent is tightly coupled with the Endpoint Central server, and therefore Endpoint Central itself will be downloaded and silently installed in the same folder location as SDP/AE. Only technicians with the SDAdmin role can download and install Endpoint Central. Once installed, Endpoint Central gets integrated with SDP. This can be checked under Admin > Integrations > Endpoint Central (formerly Desktop Central).
If the silent installation fails, you can proceed with the manual installation. The instructions are provided with appropriate download URLs inside the product pages.
Once SDP/AE and Endpoint Central are integrated, Endpoint Central will start and shut down whenever SDP/AE is started or shut down.
Endpoint Central (formerly Desktop Central) can only be installed on a Windows machine. If SDP is installed on a Linux machine, then Endpoint Central has to be installed manually on another Windows machine and integrated with SDP under Admin > Integrations > Endpoint Central (formerly Desktop Central).
As Endpoint Central is installed within the SDP folder, a maximum of 1 GB of free space is required.
If Endpoint Central is purchased separately, please refer here for detailed hardware requirements based on the number of assets purchased.
The ports used by the Endpoint Central servers are 8383, 8027, 8020, and 8028, and ports used for tools, file transfer, and remote control functionality are 8444 and 8443. More details on the purpose of each port are mentioned here.
By default, DC gets installed with bundled PGSQL. DC also supports MSSQL. Please check here for MSSQL versions supported by DC.
Click here for detailed steps for moving DC to MSSQL.
While upgrading SDP to later versions, few upgrades might require DC also to be upgraded in order to be compatible. In such cases, post-upgrade a message would be displayed on the top banner in SDP, that DC also has to be upgraded with the compatible build number and the service pack link. This upgrade has to be performed manually