Other Discovered Sources

This article contains the following topics:

If you are using a third-party discovery tool to discover assets, you can use the Other Discovered Sources option. To import assets from other discovered sources, install the following on-premise components:

• Asset Discovery Manager

You can import the assets from the following third-party tools to the application repository.

• Client Automation
• Microsoft SCCM
• Symantec Altiris
• LANDESK
• Other

Other Discovered Sources: Installation

To import assets from other discovered sources, install the following on-premise component:

Asset Discovery Manager

Asset Discovery Manager establishes the communication channel and sends the discovered assets from your on-premise network to Serviceaide Intelligent Service Management. By default one Asset Discovery Processor is installed with the Asset Discovery Manager. The Asset Discovery Manager has dependency on third-party software’s like Couch DB and Active MQ. When you run the setup file, all the prerequisite third-party software’s are installed. The Asset Discovery Manager sends the discovered assets to the application server using the built-in bulk import functionality. 

Note: A maximum of 5 active Asset Discovery Managers can be configured per slice. Multiple Asset Discovery Processors can be linked to multiple Asset Discovery Managers. A maximum of 3 active Asset Discovery Configurations per Asset Discovery Manager can be configured.

The Asset Discovery Manager components have the following important features:

• Discovers the assets on the specified IP address range and the credentials that are provided for the target servers.
• Asset Discovery Manager takes these IP addresses and distributes them to the various processors reporting to the Asset Discovery Manager.
• If the credentials are not provided for target servers, only the basic attributes are discovered. For example, host name, IP address.
• Using the correct credentials, Asset Discovery Manger can perform a deep discovery of the assets. As a result it fetches detailed information corresponding to hardware, installed applications and the virtual environment.
• The virtual environment discovery identifies the guest and host relationships for various virtual environments like VMware, ESX, and Hyper-V.
• Asset Discovery Manager sends the discovered assets to the application server using the built-in bulk Import functionality.

Follow these steps:

1. Navigate to MANAGE, ADMINISTRATION, Tools, Downloads, and click Asset Connector/Asset Discovery Manager Installer - Windows [353 MB]. The Asset Discovery Manager is downloaded.
2. Navigate to the downloads directory and double-click the clouditsm-assetconnector-installer- 1.0.0-windows-64bit .exe file. The Installation wizard appears.
3. Select a Destination Folder for the Asset Discovery Manager and click Next.
   Note: Installer populates the default installation location of the Asset Discovery Manager. You can also select a custom location.
4. Specify the following details:
   Application URL: Specify the URL for the application.
   Admin Username: Specify the application Admin User ID.
   Admin Password: Specify the application Admin Password.
   Discovery Repository Port: Specify the port number of the CouchDB, used by the asset discovery repository. This port is prepopulated, however you can edit it and can specify the value as appropriate.
5. Specify the following Asset Discovery Configuration Details and click Next. The following ports are prepopulated with default values, however you can edit them and can specify the values as appropriate.
   Messaging Service Port: Specify the port number of the ActiveMQ, used by the asset discovery manager.
   Processor Service Port: Specify the port number, which Asset Discovery Processor Windows service uses.
   Note: Make a note of the details that are specified for the Asset Discovery Manager installation. The same details are required to install the Asset Discovery Processor.
6. Verify the information available on the Pre-Installation Summary screen and click Install.
7. Click Finish to complete the Installation.
   Note: Upon the successful installation, the Asset Discovery Manager registers the following three windows services:
   Active MQ
   Apache Couch DB
   Asset Discovery Manager
   Asset Discovery Processor Service

Other Discovered Sources: Configuration

You can import the asset that the third-party discovery tool discovers, into the Intelligent Service Management repository. A maximum of three active Asset Discovery Configurations per Asset Discovery Manager can be configured.

Please note you must have completed the above steps to install and configure the Asset Discovery Manager before starting the bellow steps.

Set the configurations as follows:

Follow these steps:

1. Log in to the application as an Administrator.
2. Click MANAGE, ADMINISTRATION, Tools, Asset, and Asset Discovery Configuration, The asset discovery tab is displayed.
3. Select Other Discovered Sources from the Asset Discovery drop-down list.
4. Specify the Discovery Source.
   Note: Intelligent Service Management supports the following versions of the third-party discovery tools:
   • Altiris 7.1
   • Altiris 7.5
   • Client Automation 12.5
   • Client Automation 12.8
   • LANDESK 9.0
   • LANDESK 9.5
   • SCCM 2007
   • SCCM 2012
   • Other

5. Select the Asset Discovery Connector. This must be downloaded and configured prior to selecting it in this step. See the above section on Asset Discovery Manager.

6. Specify the Organisation to which the discovered assets are assigned.

7. Specify the Database Host Name of the other discovered source. 
8. Specify the Database Name of the other discovered source.
9. Specify Database Port, of the other discovered source.
   Note: Intelligent Service Management currently supports  third-party discovery tools running on SQL Server only.
10. Specify the User Name and the Password.
    Note: The user should be an SQL database user or can be any user who has db_datareader permission. Only the mixed mode or SQL server authentication mode are supported.
11. Set the recurrence schedule by specifying the following values.
    Start date/time: Specify the time at which the scan is scheduled to start.
    End date/time: Specify the time at which the scan ends.
    Repeat on: Specify the time at which the scan must be repeated.
    Note: Default polling interval is two hours. The scheduled job takes up to a maximum of two hours to start from the scheduled time.
12. Click Save.

Note: The recurrence scheduler lets you schedule scans to import assets from the third-party discovery tools database. You can set the job to occur at future time. When creating a recurrence schedule, you can schedule the job to repeat at a specific interval. For example, you can schedule the job to repeat on a daily or weekly basis.

Scan Status for Other Discovered Sources

To access the Asset Discovery Status tab, navigate to MANAGE, ADMINISTRATION, Tools, and Asset Discovery Status. Schedule an Other Discovered scan, navigate to the Asset Discovery Status. After you schedule a scan, you can check its status from the application. If the status indicates that the scan has failed, you can restart the scan. A discovery job can take the following statuses:

• Started: This status indicates that a discovery scan has been triggered.
• Running: This status indicates that the target network is being scanned.
• Discovery Interrupted: This status indicates that the discovery was interrupted while the scan was in progress. For more information, check the log files on the server where Asset Discovery Manager is installed.
• Discovery Completed: This status indicates that the discovery scan is completed.
• Import in Progress: This status indicates that the import of the discovered assets, to cloud asset repository, is in progress.
• Partially Imported: This status indicates that some of the discovered assets were not imported on to the cloud asset repository. For more information, check the log files on the server where Asset Discovery Manager is installed.
• Finished: This status indicates that the discovery scan and import are completed.
• Failed: This status indicates that discovery scan or import has failed. For more information, check the log files on the server where Asset Discovery Manager is installed.