Users Guide

Specifying discovery mode for creating a

MULTIPLE protocol discovery job

1. From the Type drop-down menu, select MULTIPLE to discover devices using multiple protocols.

2. Type the IP address, host name, or IP range in IP/Hostname/Range.

3. To create customized discovery template by clicking Additional Settings, see Creating customized device discovery job protocol for

servers–Additional Settings for Discovery Protocols.

Related information

Discovering devices for monitoring or management

Editing a device discovery job

You can edit only one device discovery job at a time.

1. Select the check box corresponding to the discovery job you want to edit, and then click Edit.

2. In the Discover Devices dialog box, edit the properties.

For information about the tasks to be performed in this dialog box, see Creating device discovery job.

Related information

Discovering devices for monitoring or management

Enabling WS-Man in HTTPS mode for discovering

Windows or Hyper-V servers

By default, the WS-Man service is not enabled on the Windows servers. You must enable the WS-Man service on target servers in HTTPS

mode.

Pre-requisites:

• IIS with HTTPS enabled

• WS-Man service with HTTPS enabled

• PowerShell 4.0 to configure the WS-Man service with certificate

Creating a Self-Sign Certificate

NOTE:

If you have a publicly-signed certificate, things are easier and you can use Set-WSManQuickConfig -UseSSL.

Run the following command on PowerShell by logging in as an administrator:

$Cert = New-SelfSignedCertificate -CertstoreLocation Cert:\LocalMachine\My -DnsName "myHost"

It is important to enter the name of the server that you want to manage remotely to the ‑DnsName parameter. If the server has a DNS

name, you must use the fully qualified domain name (FQDN).

NOTE: The $Cert variable is important because it stores thumbprint for future command use.

Creating PowerShell Remoting on the host system

The Enable-PSRemoting command also starts a WS-Man listener, but only for HTTP.

Enable-PSRemoting -SkipNetworkProfileCheck -Force

1. If you do not want anyone to use HTTP to connect to the server, you can remove the HTTP listener by running the command:

Get-ChildItem WSMan:\Localhost\listener | Where -Property Keys -eq "Transport=HTTP" |

Remove-Item -Recurse

Discovering devices for monitoring or management