Note: We've updated our pricing and packaging. This feature is available on Garden, Estate & Forest plans for customers who signed up before Nov 2nd 2020.

Overview

The Freshservice Discovery Agent can be installed on all Windows, Mac, and Linux machines. It collects the machine’s hardware and software information and updates Freshservice regularly without needing further intervention from the respective user(s). Besides making asset discovery extremely easy, it helps you keep track of your assets better in the long run. 

The Discovery Agents use two update logics to send information to Freshservice:

• Dynamic Discovery: Every time the Agent detects a change in its host machine, including changes to Hardware or Software Installation/uninstallation, it will update the data to Freshservice. This ensures that the database always represents your assets in the best possible way.

• Periodic Discovery: The Discovery Agent updates Freshservice weekly to maintain an up-to-date record of all your assets. This is done regardless of whether changes were made to the asset.

Downloading the Discovery Agent

The Discovery Agent for Windows, Mac and Linux operating systems can be downloaded directly from your Freshservice Portal. 

1. Navigate to Admin -> Discovery
2. In the Agent tab, choose the required Operating system
3. Click on Download Agent

Installing Discovery Agent

There are multiple ways in which the Discovery Agent can be deployed for each operating system.  

Windows

1. Install on a single machine 

2. To install on all machines in a domain, use Group Policy Object

3. To install on all machines in a workgroup, use the PsExec tool

Mac

To install on a single/multiple machines, follow this solution article

Linux

To install it on a Linux machine, run the script using the command: >sudo python FS-Linux-Agent.py

Supported Operating Systems

Note: 

• Mac Agent does not work in Mac Arm64 as .NET Core 3.1 runtime is not supported in the architecture.
• Starting from Mac version 5.1.0 and Linux version 4.0.0, the Freshservice discovery agent will now operate on the .NET 6 runtime. Please use the attached script, If you wish to uninstall .NET Core 3.1.
  
  

Prerequisites 

Windows: Microsoft .NET 4.6

Linux: Python Version 3.8 or above 
OpenSSL is a prerequisite for .Net runtime to work

.Net runtime has the following library dependencies:

• wget or curl
  
  

Specific to Linux agents:

• Linux packages

  • GNU C Library (glibc)

  • GNU C++ Library

  • GCC low-level runtime library

  • ICU

  • Kerberos

  • Open SSL

  • zlib compression library
    
    

Linux distribution-specific dependencies

• Ubuntu

  • Libc6

  • Libgcc1

  • Libgssapi-krb5-2

  • libicu52 (for 14.x)

  • libicu55 (for 16.x)

  • libicu60 (for 18.x)

  • libicu66 (for 20.x)

  • libssl1.0.0 (for 14.x, 16.x)

  • libssl1.1 (for 18.x, 20.x)

  • libstdc++6

  • zlib1g

• Alpine 

  • icu-libs

  • krb5-libs

  • libgcc

  • libgdiplus (if the .NET app requires the System.Drawing.Common assembly)

  • libintl

  • libssl1.1 (Alpine v3.9 or greater)

  • libssl1.0 (Alpine v3.8 or lower)

  • libstdc++

  • zlib

• CentOS 

  • krb5-libs

  • libicu

  • openssl-libs

  • zlib
    
    

• CentOS Stream and RedHat Enterprise Linux

  • krb5-libs

  • libicu

  • openssl-libs

  • zlib
    
    

• Debian

  • libc6

  • libgcc-s1

  • libgssapi-krb5-2

  • libicu52 (for 8.x)

  • libicu57 (for 9.x)

  • libicu63 (for 10.x)

  • libicu67 (for 11.x)

  • libssl1.0.0 (for 8.x)

  • libssl1.1 (for 9.x-11.x)

  • libstdc++6

  • Zlib1g

• Fedor

  • krb5-libs

  • libicu

  • openssl-libs

  • zlib
    
    

• OpenSuse 

  • krb5

  • libicu

  • libopenssl1_0_0
    
    

• SLES 

  • krb5

  • libicu

  • libopenssl1_1

Support for the following OS versions/flavors deprecated as of September 21, 2017

Support for the following OS versions/flavors deprecated as of August 01, 2017

MAC: OS X Mountain Lion (10.8) and OS X Mavericks (10.9)

Linux: openSUSE and Fedora

FAQs:

1. Does the Discovery Agent auto-update on the asset's own?

When the end user makes changes to the asset/device, and the device goes online, the discovery agent detects this and, based on the unique identifier - the serial Number - updates the corresponding asset in the freshservice inventory.

2. Can the discovery agent sync be force-updated, similar to Probe?

As the sync is automatic with the discovery agent, only in scenarios as mentioned in FAQ 1 does the sync occur. Alternatively the discovery agent performs a scheduled sync of the device once every week apart from the detected changes.

3. On what basis does the discovery agent create and update the assets in the inventory?

The Serial Number of the asset being scanned by the discovery agent is the primary and unique identifier for the asset import/update in the inventory. If there are no Serial number matches, a new asset is created, and if a serial number match is found, that matched asset gets updated.

dotnet-core-uninstall.sh

(637 Bytes)