- Created by Former user , last modified by Former user on Apr 30, 2019
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 22 Next »
Description
Organizations use specific client management solutions for configuration of their Assets and other management requirements. Some of these client management solutions also collect detailed hardware and software inventory information from the endpoint Assets. While such solutions are designed to be used for client management requirements, they may not be efficient for managing the Assets. SUMMIT Application provides the Asset Integration feature to manage the Assets of an organization, efficiently.
The following external database servers are associated with the Asset integration process:
The following components are part of the SCCM integration process:
Hardware
Software that are installed and their usage
Exe files
Device Managers
You can configure the SCCM Database server details to import the hardware and software Asset details so that you can schedule the following jobs:
SCCM Hardware Data Synchronization
SCCM Software Data Synchronization
SCCM Exe Data Synchronization
SCCM Device Manager Data Synchronization
The following components are part of the LANSWEEPER integration process:
Hardware
Software that are installed and their usage
You can configure the LANSWEEPER Database server details to import the hardware and software Asset details so that you can schedule the following jobs:
LANSWEEPER Hardware Data Synchronization
LANSWEEPER Software Data Synchronization
Advantages
Customers can continue to use the client management software while they can use the data collected from Asset integration in SUMMIT application for a holistic Asset management experience.
In this integration process the data is directly collected from the SCCM and LANSWEEPER databases. Thus, no additional SUMMIT Asset agent is required for such integrations.
Process
The Asset integration consists of the following processes:
Scheduling data import from an external server to the SUMMIT application using the server plugin.
Managing the life cycle of the Asset Management module using the imported data available in the SUMMIT application database.
These data import processes use SUMMIT server or Proxy server to import appropriate data from the external database tables to the Asset Management module. Based on the configuration, you can import either full data or incremental data using the database.
Prerequisites
Prerequisites for SCCM Database Server
The following table describes the views, functions, and procedures that must be executed in the SCCM Database server:
File path: ~\SummitWeb\MDLAssetMgmt\AssetFiles\SCCM-Prerequest_Scripts.sql
Component | Description |
---|---|
Views | |
Vw_EX_Summit_DeviceManager | This View is used to get the Device Manager details of the Assets from the SCCM Database. |
Vw_EX_Summit_Hardware | This View is used to get the Hardware details of the Assets from the SCCM Database. |
Vw_EX_Summit_Software | This View is used to get the Software installed on the Assets from the SCCM Database. |
Functions | |
FN_Ex_SUMMIT_RemoveHiddenChar | This function is used to trim the XML data. |
fn_SplitString | This function is used to convert the comma separated value to table value. |
Stored Procedures | |
USP_EX_SUMMIT_AM_GET_ResourcesIDs | This procedure is used to get the Resource IDs of the Assets from the SCCM Database. |
USP_EX_SUMMIT_GetEXEByResourcecID | This procedure is used to get the EXE file details based on the Resource IDs of the Assets. |
USP_EX_SUMMIT_GetHardwareByResourcecID | This procedure is used to get the Hardware Asset details based on the Resource IDs of the Assets. |
USP_EX_SUMMIT_GetSoftwareByResourcecID | This procedure is used to get the Software Asset details based on the Resource IDs of the Assets. |
USP_EX_SUMMIT_GetDeviceManagerByResourcecID | This procedure is used to get the Device Manager Asset details based on the Resource IDs of the Assets. |
The following table describes the views, functions and procedures that must be executed in the LANSWEEPER Database server:Prerequisites for LANSWEEPER Database Server
File path: ~\SummitWeb\MDLAssetMgmt\AssetFiles\LANSWEEPER-Prerequest_Scripts.sql
Component | Description |
---|---|
Views | |
Vw_EX_Summit_Hardware | This View is used to get the Hardware details of the Assets from the LANSWEEPER Database. |
Vw_EX_Summit_Software | This View is used to get the Software installed on the Assets from the LANSWEEPER Database. |
Functions | |
FN_Ex_SUMMIT_RemoveHiddenChar | This function is used to trim the XML data. |
fn_SplitString | This function is used to convert the comma separated value to table value. |
Stored Procedures | |
USP_EX_SUMMIT_AM_GET_ResourcesIDs | This procedure is used to get the Resource IDs of the Assets from the LANSWEEPER Database. |
USP_EX_SUMMIT_GetHardwareByResourcecID | This procedure is used to get the Hardware Asset details based on the Resource IDs of the Assets. |
USP_EX_SUMMIT_GetSoftwareByResourcecID | This procedure is used to get the Software Asset details based on the Resource IDs of the Assets. |
Access Prerequisites for SCCM/LANSWEEPER:
- SCCM/Lansweeper database server must be accessible from SUMMIT server or Proxy server based on the monitoring source configuration.
- SQL port (1433 default) to SCCM/Lansweeper server must be opened for SUMMIT to send queries to the database.
- An SQL server authentication account or Windows Authentication account is required. This account requires following permissions:
- While using Transact-SQL statements, the authentication account requires ALTER ANY LINKED SERVER permission on the server or membership in the setupadmin fixed server role.
- While using Management Studio, the authentication account requires CONTROL SERVER permission or membership in the sysadmin fixed server role.
Accessing the Feature
In SUMMIT Application, you can view and schedule Asset Integration jobs on the ASSET INTEGRATION page and view the Asset Integration Status report on the ASSET INTEGRATION STATUS page. For more information about these pages, see Configuring Asset Integration Details and Asset Integration Status, respectively.
- No labels