USER GUIDE. Snow Integration Manager Version 4.5 Release date Document date

Transcription

1 USER GUIDE Product Snow Integration Manager Version 4.5 Release date Document date

2 CONTENT ABOUT THIS DOCUMENT... 3 PREREQUISITES... 3 INSTALLATION... 4 CONFIGURATION... 7 GENERAL... 7 INVENTORY FILE HANDLING... 8 CONNECTOR OPTIONS Connector specific options Symantec Altiris 6/ Connector specific options BMC Atrium Discovery and Dependency Mapping Connector specific options Citrix XenServer Connector specific options Dell KACE Connector specific options FrontRange/HEAT Discovery Connector specific options HP Discovery & Dependency Mapping Inventory Connector specific options HP Server Automation Connector specific options IBM Tivoli Asset Discovery for Distributed Connector specific options Inventory File Forwarder Connector specific options iquate iqsonar Connector specific options LANDesk Connector specific options Microsoft Hyper-V Connector specific options Microsoft SCCM 2007/ Connector specific options Snow Device Manager Connector specific options Snow Inventory Oracle Scanner Connector specific options Snow ServiceNow Connector Connector specific options Snow Xml Connector specific options VMware vsphere LOGGING IMPORT PROVIDER SETTINGS Page 2 of 36

3 ABOUT THIS DOCUMENT This document describes how to install and configure Snow Integration Manager (formerly known as the Snow External Data Provider). PREREQUISITES Very important! Read before beginning the installation. Verify that the server meets the system requirements for this product; see the document System Requirements for all Snow products, which is available for download at For configuration of the Snow Integration Connectors, a user account with read-only access rights to the database or on the server is normally required. If additional access rights are required for a specific connector, these will be described in detail in the section of that particular connector. Configuration of Snow third party inventory connector for IBM TAD4D requires that IBM Data Server Driver Package is installed on the server where the Snow Integration Manager is installed. Download the latest version of Snow Integration Manager from ftp.snowsoftware.com. Page 3 of 36

4 INSTALLATION Make sure that the requirements listed in System Requirements for all Snow products are fulfilled before continuing with the installation. 1. Uninstall any previous versions of Snow Integration Manager (or Snow External Data Provider). 2. Double-click on the file SetupSIM.exe to begin the installation. 3. The Snow Integration Manager Setup Wizard is started. 4. Click Next to continue. Page 4 of 36

5 5. Read and accept the terms of the End User License Agreement. 6. Click Next to continue. 7. Select destination folder and which connectors to install. 8. Click Next to continue. 9. Click Install to start the installation. Page 5 of 36

6 10. The Snow Integration Manager is installed. 11. Click Finish to exit the Setup Wizard. Page 6 of 36

7 CONFIGURATION To configure the Snow Integration Manager, open the Snow Integration Manager Properties which is located in the start menu under Snow Software/ Snow Integration Manager. GENERAL Select global settings for Site id and aggregation scheduling. The global Site id setting can be overridden using the Site id setting in the connector specific options. NOTE: The global setting for aggregation scheduling will affect all connectors. If connectors are to be scheduled separately, do not enable this setting. 1. In the Site id text box, enter the name provided by the Service Provider (SPE platforms only), or the default site name used in the Snow Inventory installation (Enterprise). 2. In the Scheduling section, schedule an aggregation interval (or disable it). Page 7 of 36

8 INVENTORY FILE HANDLING Select method for handling of inventory data. 1. When Snow Inventory Server is running on the same server as the Snow Integration Manager, select the Save to local inventory server option and specify the incoming folder in the Inventory incoming file folder field. Example: C:\Program Files\Snow Software\Snow Inventory\Data\Incoming 2. When sending the inventory data to a remote server, select the Save to remote inventory server option (i.e. Snow Inventory Data Receiver) and enter the complete URL in the Url text box. Example: To enter proxy settings, click Proxy. To activate the proxy functionality, enable the Use proxy option. In the Settings section, use the default proxy configured in Internet Explorer by enabling the Use default proxy option, or configure manual proxy settings in the text boxes below. Page 8 of 36

9 3. In the Software filtering section, folder paths and file types which by default are excluded from/included in the inventory are listed. NOTE: Software filtering is only applicable for the Microsoft SCCM 2007/2012 and LANDesk connectors. Example: By default, all content of the folder _:\WINDOWS\* will be excluded except for the folder _:\WINDOWS\SYSTEM32\SPOOL\DRIVERS\*. By default, only.exe and.dll file types will be included in the inventory, but more file types can be added. To remove a filter, select filter in the list and click Remove. To create a new filter, click Add. 4. To exclude a folder, enter a path in the Filter text box and enable the Excluding option. Click Save. 5. To include a folder in an already excluded path, enter a path in the Filter text box and leave Excluding disabled (cleared). Click Save. 6. To include a new file extension, enter the extension in the Filter text and enable the Is extension option. Click Save. Page 9 of 36

10 CONNECTOR OPTIONS 1. To add connectors, select connector in the Available connectors list and click Add >>. 2. To remove connectors from the Active connectors list, select connector and click << Remove. 3. To configure connector specific options, click Settings; see the sections that follow. 4. To configure a schedule for a selected Active connector, click Schedule. 5. To rename an Active connector, select connector and click Rename. 6. Click Aggregate selected to immediately start aggregation for a selected connector. This option is mostly used for testing purposes. 7. In the Missing metadata reporting level drop-down list, select how to handle reporting of missing metadata. 8. Enable the Include software with missing metadata option to include software that lacks description. Filename will be used as placeholder for the description. Page 10 of 36

11 CONNECTOR SPECIFIC OPTIONS SYMANTEC ALTIRIS 6/7 The Symantec Altiris 6/7 connector uses a database connection. 1. In the Server text box, enter the SQL server name. 2. Enter user credentials for the Symantec Altiris database in the User id and Password text boxes - or Enable the Use integrated security option. 3. In the Database drop-down list, select database. 4. To verify the connection, click Test connection. 5. In the Initial aggregation length field, select number of months for initial aggregation of inventory data. 6. To reset an ongoing incremental aggregation, click Clear Last Aggregation Date. 7. Optionally, enter a Site Id for this connector. Page 11 of 36

12 CONNECTOR SPECIFIC OPTIONS BMC ATRIUM DISCOVERY AND DEPENDENCY MAPPING The BMC ADDM connector uses an API connection. DATA CONNECTION 1. In the Server text box, enter the server URL. Example: 2. Enter user credentials for the server connection in the User id and Password text boxes. 3. To verify the connection, click Test connection. 4. In the Initial aggregation length field, select number of months for initial aggregation of inventory data. 5. To reset an ongoing incremental aggregation, click Clear Last Aggregation Date. 6. Optionally, enter a Site id for this connector HOST FILTERING 1. To include or exclude computers, define a filter based on a computer attribute. Multiple criteria can be used in the filter. 2. To add the created filter, click Add. 3. To test the filter and check the result, click Preview. 4. To remove a created filter, click Remove. Page 12 of 36

13 CONNECTOR SPECIFIC OPTIONS CITRIX XENSERVER The Citrix XenServer connector uses an API connection. 1. In the Site name text box, enter a site name for this collection of XenServer servers. 2. To add one or more XenServer servers to scan for virtual machines, click Add. 3. In the Name text box, enter a name for the server. 4. Enable the Use this name as datacenter name option to use the entered name instead of the default name of the server. 5. Select whether HyperThreading is enabled on the hosts to ensure that correct processor core count is reported to Snow License Manager. 6. Enter IP address, Port, and user credentials to access the server. XenServer uses port 80 by default, so use that port on a default installation. 7. To verify the connection, click Test. 8. Click OK to save settings and close the Citrix XenServer dialog. 9. Click OK to save the settings. Page 13 of 36

14 XENSERVER TOOLS The connector will be able to extract more information from virtual machines with XenServer Tools installed. Install XenServer Tools on all VMs to retrieve the maximum amount of information. HOSTS AND VIRTUAL MACHINES If a VM is not running, it is not necessarily associated with any host. It is only when a VM is running that a host is defined. This means that a VM that is not running may in fact be associated with *no* host. When the connector is trying to figure out which host a VM is associated with, the following logic is used: 1. If the VM is running, the host is known and we use that. 2. If the VM is not running, the host is inferred by the VM's affinity field (the preferred starting host). 3. If the host could not be inferred, the VM is ignored. XENSERVER CONNECTOR AND SSL 1. Configure the connector to communicate over HTTPS by specifying port 443 in the server settings. Page 14 of 36

15 A default XenServer installation uses a self-signed certificate for TLS/SSL. To make the connector work over HTTPS, either replace the default certificate with one from a trusted certificate authority, or add XenServer s self-signed certificate to the client machine s trusted certificate store. To replace XenServer s default certificate, refer to the XenServer documentation. To trust the self-signed certificate, follow the steps described below on the machine that the connector is running on. 1. Start Internet Explorer using the running as administrator option. 2. Navigate to the XenServer over HTTPS. 3. If this warning is displayed, XenServer is not using a trusted certificate. 4. Click Continue to this website. 5. Click the Security report icon in the URL and click View certificates. Page 15 of 36

16 6. In the Certificate dialog, click Install Certificate The Certificate Import Wizard is started. 8. Select Local Machine and click Next. Page 16 of 36

17 9. Select Place all certificates in the following store. 10. Click Browse and select Trusted Root Certification Authorities. Click OK. 11. Click Next. 12. Click Finish to start the import. 13. A message box should be displayed informing that the import was successful. 14. Restart Internet Explorer and verify that it is possible to navigate to the XenServer over HTTPS without getting a certificate warning. Page 17 of 36

18 CONNECTOR SPECIFIC OPTIONS DELL KACE 1000 The Dell KACE 1000 connector uses a database connection. 1. In the Server text box, enter the MySQL server name. 2. Enter user credentials for the Dell KACE 1000 database in the User id and Password text boxes - or - Enable the Use integrated security option. 3. In the Database text box, enter the name of the database. 4. To verify the connection, click Test connection. 5. In the Initial aggregation length field, select number of months for initial aggregation of inventory data. 6. To reset an ongoing incremental aggregation, click Clear Last Aggregation Date. 7. Optionally, enter a Site id for this connector. Page 18 of 36

19 CONNECTOR SPECIFIC OPTIONS FRONTRANGE/HEAT DISCOVERY The FrontRange/HEAT Discovery connector uses a database connection. 1. In the Server text box, enter the SQL server name. 2. Enter user credentials for the FrontRange/HEAT Discovery database in the User id and Password text boxes - or Enable the Use integrated security option. 3. In the Database drop-down list, select database. 4. To verify the connection, click Test connection. 5. In the text box Organizations that start with, specify an organization filter which will be used to select computers that are connected to those organizations. Use % as a wildcard. 6. In the Initial aggregation length field, select number of months for initial aggregation of inventory data. 7. To reset an ongoing incremental aggregation, click Clear Last Aggregation Date. 8. Optionally, enter a Site id for this connector. Page 19 of 36

20 CONNECTOR SPECIFIC OPTIONS HP DISCOVERY & DEPENDENCY MAPPING INVENTORY The HP DDMI connector reads data from files in a folder. The HP Discovery & Dependency Mapping Inventory (HP DDMI) connector opens each of the HP DDMI scan files (.xsf) and converts the inventory data to a standard Snow inventory file that can be integrated with the Snow database. 1. In the XSF scan file folder text box, enter the folder where the HP DDMI connector will look for HP DDMI XSF scan files. 2. Optionally, enter a Site id for this connector. 3. In the Initial aggregation length field, select number of months for initial aggregation of inventory data. 4. To reset an ongoing incremental aggregation, click Clear Last Aggregation Date. NOTE: Due to high CPU and memory usage the recommendation is to use a server with higher performance than the recommended minimum SIM server requirements, or there is a risk that the HP DDMI aggregation will underperform. Page 20 of 36

21 CONNECTOR SPECIFIC OPTIONS HP SERVER AUTOMATION The HP Server Automation connector uses an API connection. 1. In the Server text box, enter the server URL. Example: 2. Enter user credentials for the server connection in the User id and Password text boxes. 3. To verify the connection, click Test connection. 4. In the Initial aggregation length field, select number of months for initial aggregation of inventory data. 5. To reset an ongoing incremental aggregation, click Clear Last Aggregation Date. 6. Optionally, enter a Site id for this connector KNOWN LIMITATIONS When gathering inventory data from HP Server Automation (HPSA) using this integration connector the actual servers running the HPSA software itself will not be included and presented in Snow License Manager. This is due to a limitation in the HPSA API that excludes these servers from the list of devices managed by HPSA. Page 21 of 36

22 CONNECTOR SPECIFIC OPTIONS IBM TIVOLI ASSET DISCOVERY FOR DISTRIBUTED The IBM TAD4D connector uses a database connection. 1. In the Server text box, enter the DB2 server name. 2. Enter user credentials for the IBM TAD4D database in the User id and Password text boxes. 3. In the Database text box, enter the name of the database. 4. In the Port text box, enter the database server port. 5. To verify the connection, click Test connection. 6. In the Period (days) field, enter the number of days to be included in the period for Sub Capacity Reporting. 7. In the Initial aggregation length field, select number of months for initial aggregation of inventory data. 8. To reset an ongoing incremental aggregation, click Clear Last Aggregation Date. 9. Optionally, enter a Site id for this connector. Page 22 of 36

23 CONNECTOR SPECIFIC OPTIONS INVENTORY FILE FORWARDER The Inventory File Forwarder connector reads data from files in a folder. 1. In the Inventory file folder text box, enter the folder where the connector will look for inventory files. 2. In the Data receiver url text box, enter the complete URL to the Inventory Data Receiver. Example: 3. To verify the connection, click Test. 4. Optionally, enter a Site id for this connector. 5. Enable the Use proxy option to activate the proxy functionality. 6. In the Settings section, use the default proxy configured in Internet Explorer by enabling the Use default proxy option, or configure manual proxy settings by using the text boxes. Page 23 of 36

24 CONNECTOR SPECIFIC OPTIONS IQUATE IQSONAR The iqsonar connector uses a database connection. 1. In the Server text box, enter the SQL server name. 2. Enter user credentials for the iqsonar database in the User id and Password text boxes - or Enable the Use integrated security option. 3. In the Database drop-down list, select database. 4. To verify the connection, click Test connection. 5. In the Initial aggregation length field, select number of months for initial aggregation of inventory data. 6. To reset an ongoing incremental aggregation, click Clear Last Aggregation Date. 7. Optionally, enter a Site id for this connector. Page 24 of 36

25 CONNECTOR SPECIFIC OPTIONS LANDESK The LANDesk connector uses a database connection. 1. In the Server text box, enter the SQL server name. 2. Enter user credentials for the LANDesk database in the User id and Password text boxes - or Enable the Use integrated security option. 3. In the Database drop-down list, select database. 4. To verify the connection, click Test connection. 5. In the Initial aggregation length field, select number of months for initial aggregation of inventory data. 6. To reset an ongoing incremental aggregation, click Clear Last Aggregation Date. 7. Optionally, enter a Site id for this connector. Page 25 of 36

26 CONNECTOR SPECIFIC OPTIONS MICROSOFT HYPER-V The Microsoft Hyper-V connector uses an API connection. SYSTEM REQUIREMENTS When running SIM from Windows 7 or Windows Server 2008, Windows Management Framework 3.0 must be installed. Logon credentials: o Standalone Hyper-V servers: The credentials must have access to the server s WMI interface. o VMM servers: The user must be an Administrator on the VMM server. The user must also be added to a role with read rights in Virtual Machine Manager Console on the VMM server (in the console, go to Settings User roles). VMM servers: Make sure that PowerShell Remoting is enabled on the server. Example of PowerShell script: o Enable-PSRemoting Force If the connection fails to a server that is not a member of the domain, or if connection by IP address is used, the server s IP address (or name) might need to be added to TrustedHosts on the local computer. Example of PowerShell script: set-item wsman:\localhost\client\trustedhosts -Value xxx.xxx.xxx.xxx, xxx.xxx.xxx.xxx, NOTE: The recommendation is to either install the Snow Inventory Client for Windows on the virtual machines or gather inventory data from the virtual machines using another SIM connector. The Hyper-V connector does not perform software scan on the virtual machines. Page 26 of 36

27 1. In the Site name text box, enter the site name for this collection of Hyper-V servers. This setting will override the Global site id. 2. To add one or more Hyper-V servers to scan for virtual machines, click Add. 3. In the Server name or IP text box, enter the hostname or IP address of the server (. for localhost). 4. Specify whether this is a single Hyper-V server or a VMM server controlling one or more Hyper-V hosts. For a VMM server, select whether HyperThreading is enabled on the hosts to ensure that the correct processor core count is reported to Snow License Manager. 5. Enter logon credentials (username or DOMAIN\username) in the User and Password textboxes. 6. By default, each virtual machine s name is its Fully Qualified Domain Name (computer name + domain; MYCOMPUTER.mydomain.local). If only the computer name is needed, enable the Remove domain suffix option. 7. To verify the connection, click Test. Page 27 of 36

28 CONNECTOR SPECIFIC OPTIONS MICROSOFT SCCM 2007/2012 The Microsoft SCCM 2007/2012 connector uses a database connection. DATA CONNECTION 1. In the Server text box, enter the SQL server name. 2. Enter user credentials for the SCCM database in the User id and Password text boxes - or Enable the Use integrated security option. 3. In the Database drop-down list, select database. 4. To verify the connection, click Test connection. 5. In the Initial aggregation length field, select number of months for initial aggregation of inventory data. 6. To reset an ongoing incremental aggregation, click Clear Last Aggregation Date. 7. Select Identifier. 8. Optionally, enter a Site id for this connector. Page 28 of 36

29 DATA SOURCE OPTIONS The SCCM data source options gives a better overview of the SCCM setup and what views and fields the Snow Integration Manager is able to aggregate from. It is also possible to apply filters to collections and clients. 1. Collection filter (SiteID) In the Collection filter text box, enter the Site ID s that clients will be aggregated from. Use semi colon as separator. 2. Client filter In the Client filter text box, enter the names of the clients that will be aggregated. Use semi colon as separator. A wildcard (* or %) can be used to match several clients. Example: Enter STO-* for all clients with a name beginning with STO-. 3. Enable Apply software exclusion filters to metering data by enabling this option. 4. To test the filters, click Preview. Select the Use config value checkbox to use the last aggregation date. Note that this will either be the last aggregation date if such a value exists, or todays date subtracted with the number of months specified for initial aggregation. Clear the Use config value checkbox to enter a manual date for the preview. Page 29 of 36

30 CONNECTOR SPECIFIC OPTIONS SNOW DEVICE MANAGER The Snow Device Manager connector uses an API connection. 1. In the SDM Web API URL text box, enter the URL to the Snow Device Manager Web API. 2. In the Domain, User Name, and Password text boxes, enter credentials for a domain user account with administrative privileges in the Snow Device Manager platform. 3. To only include information on registered devices, enable the Include only enrolled devices option. 4. To verify the SDM connection, click Test connection. 5. In the Initial aggregation length field, select number of months for initial aggregation of inventory data. 6. To reset an ongoing incremental aggregation, click Clear Last Aggregation Date. Page 30 of 36

31 CONNECTOR SPECIFIC OPTIONS SNOW INVENTORY ORACLE SCANNER The Snow Inventory Oracle Scanner connector reads data from files in a folder. This connector is used for import of Snow Inventory Oracle Scanner 2.x output xml files. It is also used for processing of inventory result xml files generated by the Snow Inventory Client for Unix. 1. Add one or more folders where Snow Inventory Oracle Scanner will look for xml files. 2. Optionally, enter a Site id for this connector. Page 31 of 36

32 CONNECTOR SPECIFIC OPTIONS SNOW SERVICENOW CONNECTOR The Snow ServiceNow connector uses an API connection. 1. In the SLM Web API URL text box, enter the URL to the Snow License Manager Web API. 2. In the User Name and Password text boxes, enter credentials for a user account with administrative privileges in the Snow License Manager platform. To verify the SLM connection, click Test connection. 3. For SPE platforms only In the Customer dropdown list, select the customer for whom information will be replicated. 4. In the ServiceNow URL text box, enter the URL to the ServiceNow instance. 5. In the User Name and Password textboxes, enter user credentials for an administrative account in the ServiceNow platform. 6. To verify the ServiceNow connection, click Test connection. 7. To exclude replication of inventory information on users, disable the option Include Users (the option is enabled by default). 8. To reset an ongoing incremental import and perform a full import instead, click Clear Last Import Date. NOTE: A user account is required to run the ServiceNow web services. The user account needs to be associated with the soap, import_transformer, and itil roles. Page 32 of 36

33 CONNECTOR SPECIFIC OPTIONS SNOW XML The Snow XML connector reads data from files in a folder. Snow XML is an xml format that enables integration of data from any other hardware and/or software inventory system. The Snow XML connector reads data from a structured xml file and converts it to the standard Snow Inventory format. 1. Enter a folder where Snow XML will look for xml files. 2. Optionally, enter a Site id for this connector. Page 33 of 36

34 CONNECTOR SPECIFIC OPTIONS VMWARE VSPHERE The VMware vsphere connector uses an API connection. 1. In the Site name text box, enter a site name for this collection of vsphere servers. This setting will override the Global site id. 2. To add one or more vsphere servers to scan for virtual machines, click Add. 3. In the Name text box, enter a name for the server. 4. Enable the Use this name as default name for data center option to use the entered name instead of vsphere s default ha-datacenter name. 5. Enter the Webservice url and user credentials to access the server s VMware vsphere Web Services SDK. 6. To verify the connection, click Test. NOTE: To have the complete license key for each vsphere host displayed in Snow License Manager, the entered user account needs to be assigned a vcenter Server Role with the granted privilege License of the Global privilege category. Page 34 of 36

35 LOGGING On the Logging tab specifications can be made on what information to append to the log files, how the files are formatted, where they are located, and allowed number and size of the files (default settings are recommended). Page 35 of 36

36 IMPORT PROVIDER SETTINGS From Snow Integration Manager (named EDP when released) version 4.1 it is possible to import the active provider settings from an earlier External Data Provider 3.x installation, if installed on the same computer. All existing settings on the General tab (company name, site name, schedules) for the Snow Integration Manager will remain the same as in the earlier installation. The Snow Integration Manager Properties application presents the user with an option to import the settings the first time it starts. Note that this message will be displayed only once regardless of the answer being Yes or No. Page 36 of 36