Documentation forSolarWinds Service Desk


On this page


The SolarWinds Service Desk (SWSD) Discovery connections can be created manually or automatically and include these types:

  • SolarWinds Platform nodes
  • SCCM
  • Router
  • Subnet
  • vCenter
  • AWS
  • Azure Cloud
  • Jamf
  • Intune

After a discovery scanner is installed, it detects the subnet on which it is deployed and automatically creates a new connection for the subnet. In addition, it detects the default router and automatically creates a new connection with the router. All additional SCCM, router, vCenters, subnets, nodes, and Cloud discovery on the network can be manually entered on the All Connections index page.

For the scanner to report, the device it is installed on must be connected to the network. The scanner cannot pull data regarding software; only agents can do that.

See for instructions on how to establish a connection.

SolarWinds strongly recommends that you review the Best practices before setting up connections.

You might also find useful information about what products you can integrate with SolarWinds Service Desk in Integrations setup.


Setup > Discovery & Assets > Connections.

All Connections index page

To view a list of all connections, navigate to Setup > Discovery & Assets > Connections.

You can filter, add/remove columns, and sort the data in the view by clicking Edit View. To learn more about editing the view, see List view.

The table below explains the columns on the All Connections index page.



The connection name*.



Defines whether the connection is:

  • Inactive. Connection is not used.

  • Idle. Connection is used but not in process.

  • Queued. Connection is about to start scanning but other connections are currently being scanned.

  • Scanning. Connection scan in progress.

  • Overlapping. Connection was intended to start scanning but a previous scan has not yet completed.

  • Empty. No connected devices found during last scan.

  • Not reporting. Connection was not sending data for too long.

  • No Connection. The IP address used for the connection does not respond.

  • Invalid credentials. The supplied credentials could not be used to access the connection. The status is not applicable to the subnet connection type.


The IP address / Host name / Subnet definition of the connection.


The scanner assigned to scan the connection.


Router, subnet, vCenter, or SCCM.


The associated credentials for the connection.

Most connections require credentials. SolarWinds strongly recommends the use of credentials for all connections.


One of the following:

  • Empty (when a connection is inactive or not reporting).
  • Next scheduled scan time when connection is active and not during scan.
  • Progress when connection is running a  scan.


The toggle lets you activate and deactivate the scan.  When you hover over the row a trash bin displays.  You may delete the device by clicking on the trash icon.

*Automatically created connections are assigned a generic name. SolarWinds recommends you manually edit them and provide a name that is meaningful for your data collection.

Connections details page

When viewing a connection's details page you can see details about the specific connection, such as the name, a description, the IP address, the scanner that identified the connection, and the credentials used.

Add a new Discovery connection

  1. Navigate to Setup > Discovery & Assets > Connections.

  2. From the All Connections index page, click the Add icon, and select the appropriate connection type from the dropdown list.

  3. Enter the relevant information for the specific connection type you selected. See Select your connection for information needed to configure each different connection type.

Be aware that any incorrect information (for example, an incorrect password) will prevent proper reporting in the scanning report.

Select your connection

Click the appropriate link to find information you will need in setting up your connection.

SolarWinds recommends the use of credentials for all connections.

Data collected during Discovery through connections

The table below shows what data the Discovery Agent and Scanner can pull via the connections you configure. Below the table is a list of additional information you can pull via Intune.

Details SCCM vCenter SNMP SSH Nmap WMI AWS Azure Jamf SolarWinds Platform

Host Name


IP Address





MAC Address


Operating System (OS)

Processor Type





# of Processors



Processor Speed











Active Directory







Manufacturer Version

Release Date






Serial #




(Total physical memory)





SVT (Total virtual memory)






Unique SCCM ID







OS Service Pack


















Unique ID







Device Type



Open Ports










Volume Name


Free space






Name, Total Size, and Drive Type

Type, Volume Name, and Capacity


Network Adapters

MAC Address



IP Address

MAC Address

DHCP Server



IP Address

MAC Address





IP Address MAC Address  














Azure specific data pulled:

Subscription, Public and Private DNS names, Subnets, instance ID, tenant ID, Location, VM size, virtual networks, and tags


*Host Name accuracy depends on the local DNS server always being updated.

**IP address discovered depends on the SCCM server accuracy.

***IP address is only discovered when the host is running.

****For local subnets only.

Data collection via Intune

In addition to the table above, you can pull fields from your mobile device via Intune, which is a part of Microsoft Endpoint Manager. Below is a list of data pulled:

  • Owner
  • Manufacturer
  • OS version
  • Serial Number
  • IMEI Number
  • IP address
  • Wi-Fi Mac
  • App List

See Intune configuration for instructions on integrating Intune with SWSD.

Data collection via WMI

WMI provides the ability to obtain management data from remote computers in an enterprise environment operating on Windows OS.  This is accomplished via remote WMI connections made through DCOM.

Address security measures

The security measures below must be addressed to ensure proper access to data.

  1. Ensure firewall allows WMI access.

  2. Disable UAC filter by following these steps:

    1. Navigate to Start.

    2. Type: firewall

    3. Select Allow a program through Windows Firewall.

    4. Select Change settings.

    5. Select Windows Management Instrumentation (WMI), and then click OK.

  3. If it is necessary to allow for a specific user:

    1. Run wmimgmt.msc

    2. Right-click WMI Control (local).

    3. Select Properties > Security tab > click Security > Add.

    4. Type the name of the user into Enter the object names to select.

    5. Click Check names, and then click OK.

    6. Click Advanced.

    7. Double-click the specific user.

    8. For Applied to select This namespace and subnamespaces.

    9. Select both:

      • Remote Enable

      • Execute Methods

    10. Runnet localgroup "Distributed COM Users" USERNAME /add

    11. Replace USERNAME (For example IE11WIN10\IEUser)

Management information Base (MIB)

See Management Information Base (MIB) for a list of supported device types and vendors.

Related topics