Skip to main content

Discovery

Discover assets and configuration items across your entire IT environment using network scans, cloud integrations, domain scans, and more.

ServiceOps Discovery supports both agentless and agent-based discovery for on-premises and SaaS deployments. You can scan IP ranges, connect to AWS or Azure cloud accounts, query Active Directory domains, and import data from SCCM, all from the same module. Each scan type has its own configuration, scheduler, and set of available actions.

To access Discovery, navigate to Admin > Discovery and Agents > Discovery.

Supported Operating Systems​

Linux​

DistributionSupported Versions
Ubuntu26.04 LTS, 24.10, 24.04 LTS, 23.04, 22.10, 22.04, 21.04, 20.04, 20.10, 18.04, 16.04
CentOS9 and 10 (Stream)
RedHat10, 9.6, 9.5, Core, 8, 7
Mint22, 22.1, 21, 21.1, 21.2, 21.3, 20, 19
openSUSE15.6, 15.5
SUSE15.6, 15.7, 16 Server; 15.6 and 15.7 Desktop
Debian13, 12, 11
Oracle Linux9, 8, 7
Fedora44, 40
SunOSAll supported versions
VMwareAll supported versions
VMware PhotonAll supported versions
SolarisAll supported versions
IBMAIX, VIO
Rocky Linux9.5, 9.6, 9.7, 9.8, 10, 10.1, 10.2
AlmaLinux9.5, 9.6, 9.7, 9.8, 10, 10.1, 10.2

macOS​

macOS 10.15 (Catalina), 10.16, 12, 13, 14, 15, 26

Windows Server​

Windows Server 2008, 2012, 2016, 2019, 2022, 2025

Windows​

Windows 7, Windows 10 and above

Prerequisites​

Windows Agentless Discovery​

For Windows 7 and Windows Server 2008 machines, install .NET Framework 4 before running discovery.

To enable agentless discovery on Windows, run the following commands in PowerShell v3.0 or above with Run as Administrator rights:

Set-WSManQuickConfig -Force
Enable-PSRemoting -SkipNetworkProfileCheck -Force
Set-Item -Force WSMan:\localhost\Client\TrustedHosts -value {ServiceOps IP or hostname/Poller IP}
Set-Item -Force WSMan:\localhost\Service\AllowUnencrypted -value 'true'
Set-Item -Force WSMan:\localhost\Service\Auth\Basic -value 'true'
Set-Item -Force WSMan:\localhost\Service\MaxConnections -value '100'
Set-Item -Force WSMan:\localhost\Service\MaxConcurrentOperationsPerUser -value '4294967295'
Set-Item -Force WSMan:\localhost\Service\MaxConcurrentOperations -value '4294967295'
Set-Item -Force WSMan:\localhost\Shell\MaxMemoryPerShellMB -value '1024'
Set-Item -Force WSMan:\localhost\Shell\MaxProcessesPerShell -value '2147483647'
Set-Item -Force WSMan:\localhost\Shell\MaxConcurrentUsers -value '100'
Set-Item -Force WSMan:\localhost\Shell\MaxShellsPerUser -value '2147483647'
Set-Item -Force WSMan:\localhost\MaxEnvelopeSizeKb -value '8192'
net stop winrm
net start winrm
CommandDescription
Set-WSManQuickConfig -Force

Configures the WinRM service to enable remote management.

The -Force parameter automatically configures WinRM without prompting for confirmation.

Enable-PSRemoting -SkipNetworkProfileCheck -Force

Enables PowerShell remoting, which allows remote management of Windows endpoints using PowerShell commands.

The -SkipNetworkProfileCheck parameter allows remoting on public networks.

The -Force parameter enables remoting without prompting for confirmation.

Set-Item -Force WSMan:\localhost\Client\TrustedHosts -Value (ServiceOps IP or hostname/Poller IP)

Sets the list of trusted hosts for the WinRM client.

Replace (ServiceOps IP or hostname/Poller IP) with the IP address or hostname of the ServiceOps server or Poller, whichever system you want to trust for remote management.

Set-Item -Force WSMan:\localhost\Service\AllowUnencrypted -value 'true'Allows unencrypted WinRM connections.
Set-Item -Force WSMan:\localhost\Service\Auth\Basic -value 'true'Enables basic authentication for WinRM connections, providing a simple authentication mechanism for remote management.

If PowerShell remoting is disabled, configure the following instead:

  • Enable UAC by setting LocalAccountTokenFilterPolicy to 1. Do this in one of two ways:

    • In Registry Editor, navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System and set the value of LocalAccountTokenFilterPolicy to 1.

      Registry Editor showing the LocalAccountTokenFilterPolicy value set to 1

      Reboot the machine after making this change.

    • Run the following command in Command Prompt with Run As Administrator rights:

      HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f

  • If the Windows Firewall is ON, allow the following Inbound Rules:

    Windows Firewall Inbound Rules showing WMI rules enabled

    • Windows Management Instrumentation (DCOM-In) (Private, Public)
    • Windows Management Instrumentation (DCOM-In) (Domain)
    • Windows Management Instrumentation (WMI-In) (Private, Public)
    • Windows Management Instrumentation (WMI-In) (Domain)

    Windows Firewall Inbound Rules showing Remote Service Management rules enabled

    • Remote Service Management (NP-In) (Private, Public)
    • Remote Service Management (NP-In) (Domain)

  • To verify that the ServiceOps server can communicate with the agent, run:

    python3 /opt/flotomate/main-server/config/impacket/examples/wmiexec.py {user_name}:{password}@{ip} "wmic os get Name"

Verifying Windows Discovery Prerequisites​

Run the following checks on the target Windows machine using PowerShell as Administrator before running a discovery scan.

1. .NET Framework 4.x

Open Registry Editor (regedit) and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full. Confirm the Version value is 4.x or later. If missing, install .NET Framework 4.x on the device.

2. WinRM Service

winrm enumerate winrm/config/listener

Expected: Transport = HTTP, Port = 5985, Enabled = true. If not present, run Set-WSManQuickConfig -Force and Enable-PSRemoting -SkipNetworkProfileCheck -Force.

3. PowerShell Remoting

Get-PSSessionConfiguration

Expected: A list of session configurations. If none appear, run Enable-PSRemoting -SkipNetworkProfileCheck -Force.

4. Trusted Hosts

Get-Item WSMan:\localhost\Client\TrustedHosts

Expected: The ServiceOps server IP or hostname is listed. If missing, run Set-Item WSMan:\localhost\Client\TrustedHosts -Value "<ServiceOps Server IP>" -Force.

5. Basic Authentication

Get-Item WSMan:\localhost\Service\Auth\Basic

Expected: Value: True. If False, run Set-Item WSMan:\localhost\Service\Auth\Basic -Value $true -Force.

6. Allow Unencrypted

Get-Item WSMan:\localhost\Service\AllowUnencrypted

Expected: Value: True. If False, run Set-Item WSMan:\localhost\Service\AllowUnencrypted -Value $true -Force.

7. WinRM Limits

Get-Item WSMan:\localhost\Service\MaxConnections
Get-Item WSMan:\localhost\Service\MaxConcurrentOperationsPerUser
Get-Item WSMan:\localhost\Service\MaxConcurrentOperations
Get-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB
Get-Item WSMan:\localhost\Shell\MaxProcessesPerShell
Get-Item WSMan:\localhost\Shell\MaxConcurrentUsers
Get-Item WSMan:\localhost\Shell\MaxShellsPerUser

Expected: All values should be present and configured. If any are missing, run:

Set-Item WSMan:\localhost\Service\MaxConnections 100
Set-Item WSMan:\localhost\Service\MaxConcurrentOperationsPerUser 4294967295
Set-Item WSMan:\localhost\Service\MaxConcurrentOperations 4294967295
Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1024
Set-Item WSMan:\localhost\Shell\MaxProcessesPerShell 2147483647
Set-Item WSMan:\localhost\Shell\MaxConcurrentUsers 100
Set-Item WSMan:\localhost\Shell\MaxShellsPerUser 2147483647

8. LocalAccountTokenFilterPolicy

reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v LocalAccountTokenFilterPolicy

Expected: REG_DWORD 0x1. If missing, run:

reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f
note

Restart the Windows device after making this change.

9. Windows Firewall Rules

Get-NetFirewallRule -DisplayGroup "Windows Management Instrumentation (WMI)" | Select DisplayName, Enabled
Get-NetFirewallRule -DisplayGroup "Remote Service Management" | Select DisplayName, Enabled

Expected: All rules show Enabled: True. If disabled, run Enable-NetFirewallRule -DisplayGroup "Windows Management Instrumentation (WMI)" and Enable-NetFirewallRule -DisplayGroup "Remote Service Management".

Device Type Prerequisites and Port Requirements​

Device TypePrerequisitesRequired Ports
Windows
  • Local or Domain Admin rights on target machines
  • WMI service enabled
  • Firewall rules allowing WMI
  • Remote UAC disabled for workgroup machines
TCP 135, 445, 5000-6000, 49152
Linux / Unix
  • SSH service enabled
  • Sudo user rights
  • Firewall allows SSH
  • For SSH key discovery: public key uploaded to the target device; private key stored in ServiceOps
TCP 22
SNMP devices (routers, switches, printers, storage)
  • SNMP enabled on the target device
  • Connectivity between the server and the device
  • SNMP data traffic allowed from the ServiceOps server
  • ServiceOps server IP allowed
UDP 161
SNMP v3 network devices
  • SNMP v3 enabled with auth and encryption
  • Correct user credentials configured
  • ServiceOps server IP allowed
  • AES and AES128 configured to AES128
UDP 161
VMware (VMs and hosts)
  • vCenter or ESXi accessible
  • Root user rights
  • API access enabled
TCP 443
AWS (S3, EC2, RDS, and other resources)
  • AWS Access Key ID and Secret Key
  • IAM role with ec2:Describe* and relevant permissions
  • API enabled
HTTPS TCP 443
Azure (VMs, storage, and other resources)
  • Azure App Registration (Client ID, Tenant ID, Secret)
  • API permissions assigned (Azure RM read access)
HTTPS TCP 443
Nutanix (VMs and clusters)
  • Prism Central accessible
  • Admin API account
  • Nutanix API v2 and v3 enabled
HTTPS TCP 9440
APIs and cloud services (OAuth)
  • OAuth Client ID and Secret
  • Redirect URL configured
  • Token endpoint and scopes defined
HTTPS TCP 443

Discovery Scan Types​

Discovery ServiceMonitor pending, running, and completed discovery scans and track live asset counts.Network ScanScan IP ranges or specific addresses to discover assets across your network using credentials or Nmap.Public Cloud NetworkDiscover assets in AWS and Azure cloud environments using stored cloud credentials.Private Cloud NetworkDiscover assets in private cloud environments such as Nutanix using IP addresses and credentials.Domain ScanDiscover all devices registered in your Active Directory domain using domain credentials.SCCM ScanImport asset data directly from Microsoft System Center Configuration Manager into ServiceOps.ChromeOS ScanDiscover ChromeOS devices using Google OAuth credentials and add them to your asset inventory.DNS ConfigurationConfigure the Primary and Secondary DNS servers required for domain-based asset discovery.Discovery Preference RuleDefine rules to control whether discovered devices are created as Assets or Configuration Items.