KACE Systems Management Appliance 13.2 Common Documents - Administrator Guide

The time, in seconds, after which a DNS lookup expires. If an address is not found during this time, the process “times out.”

Relay

Enable a KACE Agent to act as a tunnel WinRM, SSH and SNMP traffic to the agent connection protocol for WinRM, SSH and SNMP discovery schedules, agentless inventory, and agent provisioning.

Relay Device

Specify the device that you want to use as a relay for agentless device inventory.

A relay device that is used during discovery as a relay is used for agentless inventory, when a new device is provisioned automatically from discovery results.

Selected relay devices are listed on the following pages:

•

On the Agentless Device Connection Details page, when a new device is provisioned automatically from discovery results. For more information about this page, see Enable Agentless management by entering device information manually.

•

On the Provisioning Schedule Detail page, when agent provisioning is initiated from discovery results. For more information, see Install the KACE Agent on a device or multiple devices.

•

Ping

Perform a ping test during the network scan. During this test, the appliance sends a ping test to determine whether a system responds.

Socket

Perform a connection test during the network scan. During this test, the appliance sends a packet to the port to determine whether the port is open.

TCP Port List

Enable a port scan using TCP (Transmission Control Protocol). Use a comma to separate each port number.

UDP Port List

Enable a port scan using UDP (User Datagram Protocol). Use a comma to separate each port number.

Active Directory

Enable the appliance to check for device information on an Active Directory server. During Active Directory scans, the status is indicated as an approximate percentage instead of the number of devices scanned.

Use Secure LDAP (LDAPS)

Enable the appliance to use a secure port for LDAP communication.

Privileged User

The username of the administrator account on the Active Directory server. For example, username@example.com.

Privileged User Password

The password of the administrator account on the Active Directory server.

Search Context

The criteria used to search for devices. This criteria specifies a location or container in the Active Directory structure to be searched. Enter the most specific combination of OUs, DCs, or CNs that match your criteria, ranging from left (most specific) to right (most general). For example: DC=company,DC=com

KACE Cloud Mobile Device Manager

This option allows you to access mobile devices such as smart phones and tablets connected to the KACE Cloud Mobile Device Manager (MDM). You must obtain a tenant name and a Secret Key from the KACE Cloud MDM in order to access the devices associated with it.

Tenant Name

The name of the tenant on the KACE Cloud MDM associated with the devices that you want to manage.

For more information, see Add and edit Secret Key credentials.

The details of the account that is used to connect to the KACE Cloud MDM device. Select an existing credential from the drop-down list, or select Add new credential to add a new credential, as required.

If selected, all mobile devices discovered in the next scan are added to inventory.

NOTE: Use this option with care, to avoid expanding your inventory to an unexpected extent.

G Suite

Working with G Suite devices requires credentials that grant the appliance access to a Google Apps Domain using the Admin SDK API. You must obtain a Client ID and a Client Secret from Google so that you can get an approval code for the appliance to use.

Discover Chrome Devices

If selected, any Chrome devices will be discovered in the next scan.

Discover Mobile Devices

If selected, any G Suite mobile devices will be discovered in the next scan.

For more information, see Add and edit Google Workspace credentials.

The details of the account that is used to connect to the Chrome device. Select an existing credential from the drop-down list, or select Add new credential to add a new credential, as required. The selected credential must have an approval code that can be associated with the appropriate device type. For example, if you want to discover G Suite mobile devices, you cannot use a credential whose approval code is generated for Chrome devices.

If selected, all Chrome and mobile devices discovered in the next scan are added to inventory.

NOTE: Use this option with care, to avoid expanding your inventory to an unexpected extent.

Workspace ONE

VMware® Workspace ONE® is an enterprise-level mobility management platform that allows you to manage a wide range of different device types.

Host

The host name of the Workspace ONE administration console.

REST API Key

The REST API key, available in the Workspace ONE administration console. The key must be provided to enable integration with Workspace ONE through API calls.

The details of the service account required to connect to the device and run commands. Select an existing credential from the drop-down list, or select Add new credential to add a new credential, as required.

If selected, all Workspace ONE devices discovered in the next scan are added to inventory.

NOTE: Use this option with care, to avoid expanding your inventory to an unexpected extent.

WinRM, Hyper-V, VMM

WinRM is the connection type to use for Windows devices.

The time, in seconds, up to 1 minute, after which the connection is closed if there is no activity.

Require Kerberos

If selected, Kerberos is required for authentication. NTLM will not be used as an alternative when Kerberos is unavailable.

Using Kerberos requires DNS Lookup to be enabled in the same discovery configuration. The DNS Server is also required in the local appliance network settings.

Scan for Hyper-V and Virtual Machine Manager

If selected, the appliance imports a Microsoft Hyper-V or System Center Virtual Machine Manager infrastructure using agentless management. For more information about this feature, see Add a Discovery Schedule for a Microsoft Hyper-V or System Center Virtual Machine Manager.

Port

If this field is left blank, the default port 5985 is used.

SNMP (Simple Network Management Protocol) is a protocol for monitoring managed devices on a network.

SNMP

SNMP Full Walk

Enable a Full Walk of data in the MIB (management information base) on devices. If this option is cleared, the appliance does a Bulk GET, which searches three core OIDs (object identifiers). When selecting this option, be aware that a Full Walk can take up to 20 minutes per device. The default, Bulk GET, takes approximately one second and acquires all of the information needed for Discovery.

IMPORTANT: SNMP inventory walk does not support non-English characters on Windows devices. If it encounters non-English characters, the SNMP inventory process reports an error and stops loading inventory information.

The time, in seconds, after which the scan ends if no response is returned.

Maximum Attempts

The number of times the connection is attempted.

Credentials(SNMPv1/v2)

The details of the SNMP v1/v2 credentials required to connect to the device and run commands. Select an existing credential from the drop-down list, or select Add new credential to add a new credential, as required.

Credentials(SNMPv3)

The details of the SNMP v3 credentials required to connect to the device and run commands. Select an existing credential from the drop-down list, or select Add new credential to add a new credential, as required.

Use the SSH protocol with authentication.

SSH

IMPORTANT: Discovery though SSH is not supported for Windows devices.

IMPORTANT: After a Discovery Schedule is saved, you cannot change SSH to SNMP authentication.

The time, up to 5 minutes, after which the connection is closed if there is no activity.

Try SSH2 Connection

Enable the SSH2 protocol for connecting to and communicating with devices.

Use SSH2 if you want device communications to be more secure (recommended).

VMware

The time after which the scan ends if no response is returned.

NOTE: Running more than one of the four Nmap discovery types at a time, although possible, is not recommended. It can extend the length of a run and can cause erratic OS detection results.

Nmap

The time after which the scan ends if no response is returned.

Fast Scan

Enable the appliance to quickly scan 100 commonly used ports. If this option is cleared, all available TCP ports are scanned, which can take much longer than the fast scan.

Nmap Operating System Detection (Best Guess)

Enable the appliance to detect the operating system of the device based on fingerprinting and port information. This option might increase the time required for the scan.

TCP Port Scan

Enable a port scan using TCP (Transmission Control Protocol) of 1000 commonly used TCP ports. If this option is cleared, and UDP is selected, the appliance performs a UDP scan. If both TCP and UDP are cleared, the appliance uses a TCP scan.

If you select this option, Quest recommends that you set the Timeout value to 10 minutes to decrease the likelihood of erroneous results.

Do not combine this scan with the Fast Scan option. Doing so results in only 100 commonly used ports being scanned.

UDP Port Scan

Enable a port scan using UDP (User Datagram Protocol) of up to 1000 UDP ports. UDP scans are generally less reliable, and have lower processor overhead, than TCP scans because TCP requires a handshake when communicating with devices whereas UDP does not. However, UDP scans might take longer than TCP scans, because UDP sends multiple packets to detect ports, whereas TCP sends a single packet.

If you select this option, Quest recommends that you set the Timeout value to 30 minutes to decrease the likelihood of erroneous results.

Do not combine this scan with the Fast Scan option. Doing so results in only 100 commonly used ports being scanned.

If this option is cleared, the appliance does not scan ports using UDP.

Optional: Enter an email address for being notified of when the discovery scan completes. The email includes the name of the discovery schedule.

Specify the scan schedule:

TIP: To maintain the scan inventory without scanning, set the schedule of the scan configuration to None.

Option

Description

None

Run in combination with an event rather than on a specific date or at a specific time.

Every n hours

Run at a specified interval.

Every day/specific day at HH:MM

Run daily at a specified time, or run on a designated day of the week at a specified time.

Run on the nth of every month/specific month at HH:MM

Run on the same day every month, or a specific month, at the specified time.

Run on the nth weekday of every month/specific month at HH:MM

Run on the specific weekday of every month, or a specific month, at the specified time.

Custom

Run according to a custom schedule.

Use standard 5-field cron format (extended cron format is not supported):

Use the following when specifying values:

•

Spaces ( ): Separate each field with a space.

•

Asterisks (*): Include the entire range of values in a field with an asterisk. For example, an asterisk in the hour field indicates every hour.

•

Commas (,): Separate multiple values in a field with a comma. For example, 0,6 in the day of the week field indicates Sunday and Saturday.

•

Hyphens (-): Indicate a range of values in a field with a hyphen. For example, 1-5 in the day of the week field is equivalent to 1,2,3,4,5, which indicates Monday through Friday.

•

Slashes (/): Specify the intervals at which to repeat an action with a slash. For example, */3 in the hour field is equivalent to 0,3,6,9,12,15,18,21. The asterisk (*) specifies every hour, but /3 restricts this to hours divisible by 3.

Examples:

•

15 * * * * Run 15 minutes after every hour every day

•

0 22 * * * Run at 22:00 every day

•

0 0 1 1,6 * Run at 00:00 on January 1 and June 1

•

30 8,12 * * 1-5 Run weekdays at 08:30 and 12:30

•

0 2 */2 * * Run every other day at 02:00

View Task Schedule

Click to view the task schedule. The Task Schedule dialog box displays a list of scheduled tasks. Click a task to review the task details. For more information, see View task schedules.

Click Save.

Things to take into consideration with Nmap discovery

For successful outcomes with Nmap discovery, there are some issues to consider and best practices to adopt to improve speed and accuracy and to avoid problems.

Best practices for improving the speed and accuracy of discovery

To improve the speed and accuracy of Nmap discovery:

•

Avoid using DNS Lookup. DNS Lookup can slow down scan times by up to 500 percent if you specify an invalid or unreachable IP address for the DNS.

•

Run one discovery type at a time. Although it is possible to run multiple discovery types simultaneously, doing so can extend the length of a run and can cause erratic OS detection results.

•

Select Nmap Operating System Detection (Best Guess) if you are unsure what to run. This selection can give you a reasonable view into your subnet or subnets. At a minimum, using Best Guess can identify what OSs are on what devices. If you do not get the expected results, for example if some devices appear with unknown as the Operating System, try increasing the timeout value and rerunning the discovery.

•

Discovery does not work correctly through a VPN. Use another source for access to the devices.

Issues that can impede discovery

Be aware that devices that are offline or otherwise inaccessible at the time of a scan are ignored because they appear to be nonexistent.

If you know that there are devices that should be reported, but are not, they are either:

•

Being blocked by a firewall

•

Actively blocking pings

•

Actually offline (no power)

•

Thwarting fingerprinting, through various methods.

Some devices, typically security devices, hide themselves from view, or misrepresent themselves to avoid detection.

Troubleshooting unknown operating systems

If the Operating System appears as unknown in the Discovery Results list page:

•

Check to see if the Nmap checkmark is present in the Nmap column. If not, the device was offline during the scan, and the operating system could not be determined.

•

If the Nmap checkmark is present, but the Operating System is unknown, the most likely cause is a firewall that is blocking the ports that Nmap is using to determine what OS is running on the device.

For example, if you scan using only UDP ports 7 and 161, the device appears online with the Nmap checkmark displayed. However, the Operating System appears unknown, because UDP ports alone are not sufficient to determine what OS is running on the device.

Things to take into consideration with Nmap discovery

Add a Discovery Schedule to perform a quick "what and where" scan of your network

Things to take into consideration with Nmap discovery

Use one of the available schedules to quickly obtain Discovery Results that show the availability of devices.

This type of Discovery scans for any device type in your network: managed computers or non-computer devices.

If you want to add an Nmap Discovery Schedule, there are several issues to consider. See Things to take into consideration with Nmap discovery.

Go to the Discovery Schedule Detail page:

On the left navigation bar, click Inventory, then click Discovery Schedules.

Select Choose Action > New.

Select the Discovery Type to display the form with the options for the selected type.

Depending on the type you select, the following options appear before the Notify section:

◦

Ping. DNS Lookup and Ping discovery options appear.

◦

Socket. DNS Lookup and Socket discovery options appear.

◦

Active Directory. DNS Lookup and Active Directory discovery options appear.

◦

External Integration [KACE Cloud Mobile Device Manager, G Suite, Workspace ONE]. KACE Cloud Mobile Device Manager, G Suite, and Workspace ONE discovery options appear.

NOTE: Any devices discovered through External Integration such as KACE Mobile Device Manager, G Suite, Workspace ONE devices do not count toward the appliance license limit.

◦

Authenticated [WinRM, SNMP, SSH, VMware, Hyper-V]. DNS Lookup, Relay, WinRM, Hyper-V, VMM, SNMP, SSH, and VMware discovery options appear.

◦

Nmap. DNS Lookup and Nmap discovery options appear.

◦

Custom. DNS Lookup, Ping, Nmap, WinRM, SNMP, SSH, and VMware discovery options appear.

In the Name field, enter a name for the scan.

This name appears on the Discovery Schedules page.

TIP: The appliance supports both IPv6 (Internet Protocol version 6) and IPv4 addresses.

CAUTION: A maximum of 25,000 IP addresses is supported. If you specify an IP range that results in more than 25,000 addresses, a warning appears when you attempt to save the provisioning schedule.

Select the Discovery options. The options that appear depend on the Discovery Type you have chosen:

Name Server for Lookup

The hostname or IP address of the name server.

TIP: The appliance supports both IPv6 (Internet Protocol version 6) and IPv4 addresses.

The time, in seconds, after which a DNS lookup expires. If an address is not found during this time, the process “times out.”

Relay

Enable a KACE Agent to act as a tunnel WinRM, SSH and SNMP traffic to the agent connection protocol for WinRM, SSH and SNMP discovery schedules, agentless inventory, and agent provisioning.

Relay Device

Specify the device that you want to use as a relay for agentless device inventory.

A relay device that is used during discovery as a relay is used for agentless inventory, when a new device is provisioned automatically from discovery results.

Selected relay devices are listed on the following pages:

•

On the Provisioning Schedule Detail page, when agent provisioning is initiated from discovery results. For more information, see Install the KACE Agent on a device or multiple devices.

•

Ping

Perform a ping test during the network scan. During this test, the appliance sends a ping test to determine whether a system responds.

Socket

Perform a connection test during the network scan. During this test, the appliance sends a packet to the port to determine whether the port is open.

TCP Port List

Enable a port scan using TCP (Transmission Control Protocol). Use a comma to separate each port number.

UDP Port List

Enable a port scan using UDP (User Datagram Protocol). Use a comma to separate each port number.

Active Directory

Use Secure LDAP (LDAPS)

Enable the appliance to use a secure port for LDAP communication.

Privileged User

The username of the administrator account on the Active Directory server. For example, username@example.com.

Privileged User Password

The password of the administrator account on the Active Directory server.

Search Context

KACE Cloud Mobile Device Manager

Tenant Name

The name of the tenant on the KACE Cloud MDM associated with the devices that you want to manage.

For more information, see Add and edit Secret Key credentials.

If selected, all mobile devices discovered in the next scan are added to inventory.

NOTE: Use this option with care, to avoid expanding your inventory to an unexpected extent.

G Suite

Discover Chrome Devices

If selected, any Chrome devices will be discovered in the next scan.

Discover Mobile Devices

If selected, any G Suite mobile devices will be discovered in the next scan.

For more information, see Add and edit Google Workspace credentials.

If selected, all Chrome and mobile devices discovered in the next scan are added to inventory.

NOTE: Use this option with care, to avoid expanding your inventory to an unexpected extent.

Workspace ONE

VMware® Workspace ONE® is an enterprise-level mobility management platform that allows you to manage a wide range of different device types.

Host

The host name of the Workspace ONE administration console.

REST API Key

The REST API key, available in the Workspace ONE administration console. The key must be provided to enable integration with Workspace ONE through API calls.

If selected, all Workspace ONE devices discovered in the next scan are added to inventory.

NOTE: Use this option with care, to avoid expanding your inventory to an unexpected extent.

WinRM, Hyper-V, VMM

WinRM is the connection type to use for Windows devices.

The time, in seconds, up to 1 minute, after which the connection is closed if there is no activity.

Require Kerberos

If selected, Kerberos is required for authentication. NTLM will not be used as an alternative when Kerberos is unavailable.

Using Kerberos requires DNS Lookup to be enabled in the same discovery configuration. The DNS Server is also required in the local appliance network settings.

Scan for Hyper-V and Virtual Machine Manager

Port

If this field is left blank, the default port 5985 is used.

SNMP (Simple Network Management Protocol) is a protocol for monitoring managed devices on a network.

SNMP

SNMP Full Walk

The time, in seconds, after which the scan ends if no response is returned.

Maximum Attempts

The number of times the connection is attempted.

Credentials(SNMPv1/v2)

Credentials(SNMPv3)

Use the SSH protocol with authentication.

SSH

IMPORTANT: Discovery though SSH is not supported for Windows devices.

IMPORTANT: After a Discovery Schedule is saved, you cannot change SSH to SNMP authentication.

The time, up to 5 minutes, after which the connection is closed if there is no activity.

Try SSH2 Connection

Enable the SSH2 protocol for connecting to and communicating with devices.

Use SSH2 if you want device communications to be more secure (recommended).

VMware

The time after which the scan ends if no response is returned.

NOTE: Running more than one of the four Nmap discovery types at a time, although possible, is not recommended. It can extend the length of a run and can cause erratic OS detection results.

Nmap

The time after which the scan ends if no response is returned.

Fast Scan

Enable the appliance to quickly scan 100 commonly used ports. If this option is cleared, all available TCP ports are scanned, which can take much longer than the fast scan.

Nmap Operating System Detection (Best Guess)

Enable the appliance to detect the operating system of the device based on fingerprinting and port information. This option might increase the time required for the scan.

TCP Port Scan

If you select this option, Quest recommends that you set the Timeout value to 10 minutes to decrease the likelihood of erroneous results.

Do not combine this scan with the Fast Scan option. Doing so results in only 100 commonly used ports being scanned.

UDP Port Scan

If you select this option, Quest recommends that you set the Timeout value to 30 minutes to decrease the likelihood of erroneous results.

Do not combine this scan with the Fast Scan option. Doing so results in only 100 commonly used ports being scanned.

If this option is cleared, the appliance does not scan ports using UDP.

Optional: Enter an email address for being notified of when the discovery scan completes. The email includes the name of the discovery schedule.

Specify the scan schedule:

TIP: To maintain the scan inventory without scanning, set the schedule of the scan configuration to None.

Option

Description

None

Run in combination with an event rather than on a specific date or at a specific time.

Every n hours

Run at a specified interval.

Every day/specific day at HH:MM

Run daily at a specified time, or run on a designated day of the week at a specified time.

Run on the nth of every month/specific month at HH:MM

Run on the same day every month, or a specific month, at the specified time.

Run on the nth weekday of every month/specific month at HH:MM

Run on the specific weekday of every month, or a specific month, at the specified time.

Custom

Run according to a custom schedule.

Use standard 5-field cron format (extended cron format is not supported):

Use the following when specifying values:

•

Spaces ( ): Separate each field with a space.

•

Asterisks (*): Include the entire range of values in a field with an asterisk. For example, an asterisk in the hour field indicates every hour.

•

Commas (,): Separate multiple values in a field with a comma. For example, 0,6 in the day of the week field indicates Sunday and Saturday.

•

Hyphens (-): Indicate a range of values in a field with a hyphen. For example, 1-5 in the day of the week field is equivalent to 1,2,3,4,5, which indicates Monday through Friday.

•

Examples:

•

15 * * * * Run 15 minutes after every hour every day

•

0 22 * * * Run at 22:00 every day

•

0 0 1 1,6 * Run at 00:00 on January 1 and June 1

•

30 8,12 * * 1-5 Run weekdays at 08:30 and 12:30

•

0 2 */2 * * Run every other day at 02:00

View Task Schedule

Click to view the task schedule. The Task Schedule dialog box displays a list of scheduled tasks. Click a task to review the task details. For more information, see View task schedules.

Click Save.

Things to take into consideration with Nmap discovery

For successful outcomes with Nmap discovery, there are some issues to consider and best practices to adopt to improve speed and accuracy and to avoid problems.

Best practices for improving the speed and accuracy of discovery

To improve the speed and accuracy of Nmap discovery:

•

Avoid using DNS Lookup. DNS Lookup can slow down scan times by up to 500 percent if you specify an invalid or unreachable IP address for the DNS.

•

Run one discovery type at a time. Although it is possible to run multiple discovery types simultaneously, doing so can extend the length of a run and can cause erratic OS detection results.

•

Discovery does not work correctly through a VPN. Use another source for access to the devices.

Issues that can impede discovery

Be aware that devices that are offline or otherwise inaccessible at the time of a scan are ignored because they appear to be nonexistent.

If you know that there are devices that should be reported, but are not, they are either:

•

Being blocked by a firewall

•

Actively blocking pings

•

Actually offline (no power)

•

Thwarting fingerprinting, through various methods.

Some devices, typically security devices, hide themselves from view, or misrepresent themselves to avoid detection.

Troubleshooting unknown operating systems

If the Operating System appears as unknown in the Discovery Results list page:

•

Check to see if the Nmap checkmark is present in the Nmap column. If not, the device was offline during the scan, and the operating system could not be determined.

•

If the Nmap checkmark is present, but the Operating System is unknown, the most likely cause is a firewall that is blocking the ports that Nmap is using to determine what OS is running on the device.

Add a Discovery Schedule for a thorough scan of managed Windows, Mac, Linux, and UNIX computers

To scan your network for devices and capture information about devices, you use Discovery Schedules. After devices are discovered using the Active Directory or Authenticated discovery type, you can add those discovered devices to inventory.

Go to the Discovery Schedule Detail page:

On the left navigation bar, click Inventory, then click Discovery Schedules.

Select Choose Action > New.

Select the Discovery Type to display the form with the options for the selected type.

Depending on the type you select, the following options appear before the Notify section:

◦

Active Directory. DNS Lookup and Active Directory discovery options appear.

◦

Authenticated [WinRM, SNMP, SSH, VMware, Hyper-V]. DNS Lookup, Relay, WinRM, Hyper-V, VMM, SNMP, SSH, and VMware discovery options appear.

In the Name field, enter a name for the scan.

This name appears on the Discovery Schedules page.

In the IP Address Range field, do one of the following:

◦

If you select the Active Directory Discovery Type, enter the IP address of the Active Directory server to be scanned.

◦

Enter an IP address range to scan. Use hyphens to specify individual IP address class ranges.For example, type 192.168.2-5.1-200 to scan for all IP addresses between 192.168.2-5.1 and 192.168.2-5.200, inclusive.

TIP: The appliance supports both IPv6 (Internet Protocol version 6) and IPv4 addresses.

CAUTION: A maximum of 25,000 IP addresses is supported. If you specify an IP range that results in more than 25,000 addresses, a warning appears when you attempt to save the provisioning schedule.

Select the Discovery options. The options that appear depend on the Discovery Type you have chosen:

Name Server for Lookup

The hostname or IP address of the name server.

TIP: The appliance supports both IPv6 (Internet Protocol version 6) and IPv4 addresses.

The time, in seconds, after which a DNS lookup expires. If an address is not found during this time, the process “times out.”

Relay

Enable a KACE Agent to act as a tunnel WinRM, SSH and SNMP traffic to the agent connection protocol for WinRM, SSH and SNMP discovery schedules, agentless inventory, and agent provisioning.

Relay Device

Specify the device that you want to use as a relay for agentless device inventory.

A relay device that is used during discovery as a relay is used for agentless inventory, when a new device is provisioned automatically from discovery results.

Selected relay devices are listed on the following pages:

•

On the Provisioning Schedule Detail page, when agent provisioning is initiated from discovery results. For more information, see Install the KACE Agent on a device or multiple devices.

•

Active Directory

Use Secure LDAP (LDAPS)

Enable the appliance to use a secure port for LDAP communication.

Privileged User

The username of the administrator account on the Active Directory server. For example, username@example.com.

Privileged User Password

The password of the administrator account on the Active Directory server.

Search Context

DC=company,DC=com.

WinRM, Hyper-V, VMM

WinRM is the connection type to use for Windows devices.

The time, in seconds, up to 1 minute, after which the connection is closed if there is no activity.

Require Kerberos

If selected, Kerberos is required for authentication. NTLM will not be used as an alternative when Kerberos is unavailable.

Using Kerberos requires DNS Lookup to be enabled in the same discovery configuration. The DNS Server is also required in the local appliance network settings.

Scan for Hyper-V and Virtual Machine Manager

This field is only used if you want to monitor a a Microsoft Hyper-V or System Center Virtual Machine Manager infrastructure. Ensure this option is cleared. For more information about this feature, see Add a Discovery Schedule for a Microsoft Hyper-V or System Center Virtual Machine Manager.

Port

If this field is left blank, the default port 5985 is used.

The details of the service account required to connect to the device and run commands. Select existing credentials from the drop-down list, or select Add new credential to add credentials not already listed.

Use the SSH protocol with authentication.

SSH

IMPORTANT: Discovery though SSH is not supported for Windows devices.

NOTE: After a Discovery Schedule is saved, you cannot change SSH to SNMP authentication.

The time, up to 5 minutes, after which the connection is closed if there is no activity.

Try SSH2 Connection

Enable the SSH2 protocol for connecting to and communicating with devices.

Use SSH2 if you want device communications to be more secure (recommended).