user guide - snow software · 2 installation ... for a detailed description, see user guide,...

USER GUIDEProduct Snow Integration Manager

Version 5.5

Release date 2017-09-27

Document date 2017-10-05

SNOWSOFTWARE.COM

CONTENTS1 Introduction ............................................................................................................................. 4

1.1 Prerequisites ................................................................................................................... 4

2 Installation ............................................................................................................................... 5

2.1 New installation .............................................................................................................. 5

2.2 Upgrade .......................................................................................................................... 5

3 Configuration ........................................................................................................................... 7

3.1 General ........................................................................................................................... 7

3.2 Inventory File handling .................................................................................................... 8

3.3 Connector options ........................................................................................................ 11

3.4 Logging ......................................................................................................................... 12

4 Available integration connectors .......................................................................................... 13

4.1 VMware AirWatch .......................................................................................................... 13

4.2 Symantec Altiris ............................................................................................................ 13

4.3 AWS Discovery .............................................................................................................. 13

4.4 Azure Discovery ............................................................................................................ 13

4.5 BMC Atrium Discovery and Dependency Mapping ......................................................... 13

4.6 Citrix XenServer ............................................................................................................ 13

4.7 Dell KACE 1000 .............................................................................................................. 13

4.8 Discovery data from file ................................................................................................ 14

4.9 FrontRange Discovery ................................................................................................... 16

4.10 HEAT Discovery ........................................................................................................... 16

4.11 HP Discovery & Dependency Mapping Inventory ......................................................... 17

4.12 HP Server Automation ................................................................................................. 17

4.13 IBM BigFix Inventory ................................................................................................... 17

4.14 IBM License Metric Tool (ILMT) .................................................................................... 17

4.15 IBM Tivoli Asset Discovery for Distributed ................................................................... 18

4.16 Inventory File Forwarder ............................................................................................. 18

4.17 iQuate iQSonar ........................................................................................................... 19

4.18 LANDesk ..................................................................................................................... 19

4.19 Microsoft Hyper-V ....................................................................................................... 19

4.20 Microsoft Office 365 .................................................................................................... 19

4.21 Microsoft SCCM ........................................................................................................... 19

4.22 MobileIron .................................................................................................................. 19

4.23 Red Hat Enterprise Virtualization ................................................................................. 20

4.24 ServiceNow Express .................................................................................................... 21

4.25 Snow for ServiceNow .................................................................................................. 21

of 24 SNOWSOFTWARE.COM

4.26 Snow Device Manager ................................................................................................. 21

4.27 Snow Inventory Oracle Scanner ................................................................................... 22

4.28 Snow Xml .................................................................................................................... 22

4.29 VMware vSphere ......................................................................................................... 22

5 Import provider settings ....................................................................................................... 23

6 About Snow Integration Manager ......................................................................................... 24


1 INTRODUCTIONThis document describes how to install and configure Snow Integration Manager.

1.1 PREREQUISITESVery important! Read before beginning the installation.

▪ Verify that the server meets the system requirements for this product; see the documentSystem Requirements for all Snow products, which is available for download at:http://www.snowsoftware.com/int/download

▪ For configuration of the Snow Integration Connectors, a user account with read-only accessrights to the database or on the server is normally required. If additional access rights arerequired for a specific connector, these will be described in detail in the section of thatparticular connector.

▪ Configuration of Snow third party inventory connectors for IBM TAD4D and IBM ILMTrequire that IBM Data Server Driver Package is installed on the server where the SnowIntegration Manager is installed.

▪ Configuration of the Microsoft Office 365 connector requires that the following is installedon the server where the Snow Integration Manager is installed.

◦ Microsoft Online Services Sign-In Assistant (64-bit version):https://www.microsoft.com/en-us/download/details.aspx?id=41950

◦ Windows Azure Active Directory Module for Windows PowerShell (64-bit version):http://go.microsoft.com/fwlink/p/?linkid=236297

▪ Download the latest version of Snow Integration Manager from:ftp://ftp.snowsoftware.com


http://www.snowsoftware.com/int/download

https://www.microsoft.com/en-us/download/details.aspx?id=41950

http://go.microsoft.com/fwlink/p/?linkid=236297

ftp://ftp.snowsoftware.com

2 INSTALLATIONMake sure that the requirements listed in System Requirements for all Snow products are fulfilledbefore continuing with the installation.

NOTERun the installation as Administrator.

2.1 NEW INSTALLATION1. To start the installation, double-click the SetupSIM.exe file.

2. The Snow Integration Manager Setup wizard is started.Click Next.

3. Read and accept the terms of the End User License Agreement.Click Next.

4. In the Custom setup step, select which connectors to install, and select Location for theinstallation files.Click Next.

5. In the Ready to install Snow Integration Manager step, click Install to start theinstallation.

6. After the installation has completed, click Finish to exit the Snow Integration ManagerSetup wizard.

2.2 UPGRADEThe settings of the active integration connectors are stored in the registry. They will be kept intactwhen SIM is uninstalled.

2.2.1 INSTALL NEW VERSION

1. Uninstall the existing version of Snow Integration Manager (or Snow External Data Provider)from Programs and Features in the Control Panel.

2. Install the new version of Snow Integration Manager.For details, see New installation.


2.2.2 TEST THE CONNECTORSAfter installation, start Snow Integration Manager to test settings and aggregation of theconnectors.

1. Click the Inventory file handling tab.

2. Verify the settings for the incoming folders.For details, see Local Inventory server.

3. Click the Connector options tab.

4. To test the settings for each Active connector:

a. Click the connector name, and then click Settings.

b. In the Properties dialog box, click Test connection.

c. If applicable, click Clear Last Aggregation date.

d. Close the Properties dialog box.

5. To test aggregation for each Active connector:

a. Click the connector name, and then click Aggregate selected.When the aggregation runs, the Aggregate selected button is blue.

b. Wait until the aggregation is completed and the Aggregate selected button turnsgrey.

6. After aggregation is completed, check the logs for any errors or exceptions.(normally in C:\Program Files\Snow Software\Logs\Snow Integration Manager)

7. For each connector, verify that the correct Schedule is set.

2.2.3 TROUBLESHOOTINGIn case the connector fails to work, try to remove the connector, and then add and configure itonce again.

Do the following:

1. Click the connector in the Active connectors list, and then click Remove.

2. Click the connector in the Available connectors list, and then click Add.

3. In the Properties dialog box, configure the connector.

4. Test the connector settings.For details, see Test the connectors.

5. Test aggregation of the connector.For details, see Test the connectors.

If the connector still fails to work, also try to remove the registry entries of the connector. Do thisafter the first step in the procedure described above.

In case none of these actions makes the connector work, contact Snow support. Set Log level toALL and send the result along with the defect description. For details, see Logging.


3 CONFIGURATIONTo configure the Snow Integration Manager, open the Snow Integration Manager Propertieswhich is located in the start menu.

3.1 GENERALSelect global settings for Site id and aggregation scheduling. The global Site id setting can beoverridden using the Site id setting in the connector specific options.

NOTEThe global setting for aggregation scheduling will affect all connectors. If connectors are to bescheduled separately, do not enable this setting.

1. In the Site id box, type the site 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).


3.2 INVENTORY FILE HANDLINGSelect method for handling of inventory data.

3.2.1 LOCAL INVENTORY SERVERWhen Snow Inventory Server is running on the same server as the Snow Integration Manager, dothe following:

1. Click the Save to local inventory server check box.

2. In the Inventory incoming folder box, specify the folder where the integration connectorswill put the inventory files.The default folder is C:\Program Files\Snow Software\Snow Inventory\Server\Incoming\data\processing.

3. In the Announcement incoming folder box, specify the folder where the Discovery datafrom file , the AWS Discovery, and the Azure Discovery connectors will put the discovery(announcement) files.The default folder is C:\Program Files\Snow Software\Snow Inventory\Server\Incoming\announcements\processing.

3.2.2 REMOTE INVENTORY SERVERWhen sending the inventory data to a remote inventory server (such as a Snow Inventory MasterServer, a Snow Inventory Service Gateway, or a Snow Inventory Data Receiver), do the following:

1. Click the Save to remote inventory server check box.


2. Type the complete URL in the Url box.

EXAMPLEhttp://myserver.com

3. To activate and use proxy functionality, click Proxy.The Proxy settings dialog box appears.

4. Click the Use proxy check box.

5. In the Settings section, use the default proxy configured in Internet Explorer by clicking theUse default proxy check box, or configure manual proxy settings in the boxes.

3.2.3 SOFTWARE FILTERINGThe Software filtering section lists folder paths and file types, which by default are excludedfrom/included in the inventory.

NOTESoftware filtering is only applicable for the Microsoft SCCM 2007/2012 and LANDeskconnectors.

EXAMPLEUsing the filter in the image below, all content of the folder _:\WINDOWS\* will be excludedexcept 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 beadded.

1. To remove a filter, select filter in the list and then click Remove.

2. To create a new filter, click Add.The Add software filter dialog box appears.

▪ To exclude a folder, type a path in the Filter box, and the click the Excluding checkbox.

Click Save.

▪ To include a folder in an already excluded path, type a path in the Filter box, and thenleave the Excluding check box cleared.

Click Save.

▪ To include a new file extension, type the extension in the Filter box, and then click theIs extension check box.

Click Save.


3.3 CONNECTOR OPTIONSSelect which connectors to configure. For details of the specific configuration options for eachconnector, see the sections that follow.

1. To add connectors, select connector in the Available connectors list and then click Add >>.

2. To remove connectors from the Active connectors list, select connector and then click <<Remove.

3. To configure connector specific options, click SettingsFor each specific connector, 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 then click Rename.

6. To start an immediate aggregation for a selected connector, click Aggregate selected. Thisoption is mostly used for test purposes.

7. In the Missing metadata reporting level list, select how to handle reporting of missingmetadata.

8. To include software that lacks description, click the Include software with missingmetadata check box. The filename will be used as placeholder for the description.


3.4 LOGGINGOn 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).


4 AVAILABLE INTEGRATION CONNECTORSA number of integration connectors are available within the Snow Integration Manager.Information on how to configure each connector is either available in separate user guides, ordescribed in the sections that follow.

4.1 VMWARE AIRWATCHThe AirWatch connector uses an API connection.

For a detailed description, see User guide, AirWatch connector.

4.2 SYMANTEC ALTIRISThe Symantec Altiris connector uses a database connection.

For a detailed description, see User guide, Altiris connector.

4.3 AWS DISCOVERYThe Amazon Web Service Discovery connector uses an API connection.

For a detailed description, see User guide, AWS Discovery connector.

4.4 AZURE DISCOVERYThe Azure Discovery connector uses an HTTPS connection.

For a detailed description, see User guide, Azure Discovery connector.

4.5 BMC ATRIUM DISCOVERY AND DEPENDENCYMAPPING

The BMC ADDM connector uses an API connection.

For a detailed description, see User guide, BMC ADDM connector.

4.6 CITRIX XENSERVERThe Citrix XenServer connector uses an API connection.

For a detailed description, see User guide, Citrix XenServer connector

4.7 DELL KACE 1000The Dell KACE 1000 connector uses a database connection.


https://snowprod.service-now.com/support/support?id=kb_article_view&sys_kb_id=7fa37cea0f06a2002944f88ce1050eeb

https://snowprod.service-now.com/support/support?id=kb_article_view&sys_kb_id=37ec12750f266e402944f88ce1050e5f

https://snowprod.service-now.com/support/support?id=kb_article_view&sys_kb_id=1322aa7037ff724067ff861754990eee

https://snowprod.service-now.com/support/support?id=kb_article_view&sys_kb_id=d7de56f837bf724067ff861754990e9b

https://snowprod.service-now.com/support/support?id=kb_article_view&sys_kb_id=ee9ea86937b8fa0067ff861754990e0a

https://snowprod.service-now.com/support/support?id=kb_article_view&sys_kb_id=15a0e2f90f266e402944f88ce1050e50

For a detailed description, see User guide, Dell KACE connector.

4.8 DISCOVERY DATA FROM FILEThe Discovery data from file connector reads data from files in a folder, and then delivers the datato the Announcement incoming folder in Snow Integration Manager.

1. To add a source folder with discovery data files, click Add.

2. The Source File Folder dialog box appears with the two tabs Configuration and FieldMappings.

3. After settings have been made on the Configuration and Field Mapping tabs, click Previewto view the result of an import and to verify that the mappings are correct.

4. Optionally, type a site Id for this connector.

4.8.1 CONFIGURATION

1. Click the Configuration tab.

2. In the File folder box, type the folder where the connector will look for files.

3. If applicable for the file, select the Has headers checkbox.


https://snowprod.service-now.com/support/support?id=kb_article_view&sys_kb_id=298d3e6f0fba32005d079acae1050ec7

4. Select file Type in the list.

5. Select data Delimiter in the list.

4.8.2 FIELD MAPPINGS

1. Click the Field Mappings tab.

2. Select one of the following:

a. In the Mappings table, click to type the name of the Source file columns thatcorresponds to each Target field.

b. Select the Map by index check box.In the Mappings table, click to type the index number of the Source file columns thatcorresponds to each Target field.

c. Click Get headers from file to load the headers from a source file.In the Mappings table, select a header in the Source list for each Target field.

NOTEIf the Has headers check box is cleared on the Configuration tab, the Map by indexcheck box is automatically selected and mandatory.

3. Click OK to save the changes and close the Source File Folder dialog box.


4.9 FRONTRANGE DISCOVERYThe FrontRange Discovery connector uses a database connection.

1. In the Server box, type the SQL server name.

2. Select one of the following:

▪ Type user credentials for the FrontRange Discovery database in the User id andPassword boxes.

▪ Click the Use integrated security check box.

3. In the Database list, select database.

4. To verify the connection, click Test connection.

5. In the Organizations that start with box, specify an organization filter which will be usedto select computers that are connected to those organizations. Use % as a wildcardcharacter.

6. In the Initial aggregation length field, select number of months for initial aggregation ofinventory data.

7. To reset an ongoing incremental aggregation, click Clear Last Aggregation Date.


9. To optimize handling of network adapter information, select the current version of SnowInventory Server.

4.10 HEAT DISCOVERYThe HEAT Discovery connector uses a database connection (SQL).

For a detailed description, see User guide, HEAT Discovery connector.


https://snowprod.service-now.com/support/support?id=kb_article_view&sys_kb_id=59e5d9fa37a18bc09262cea954990e6f

4.11 HP DISCOVERY & DEPENDENCY MAPPINGINVENTORY

The HP DDMI connector reads data from files in a folder.

The HP Discovery & Dependency Mapping Inventory (HP DDMI) connector opens each of the HPDDMI scan files (.xsf) and converts the inventory data to a standard Snow inventory file that can beintegrated with the Snow database.

1. In the XSF scan file folder box, type the folder where the HP DDMI connector will look forHP DDMI XSF scan files.

2. Optionally, type a Site id for this connector.



NOTEDue to high CPU and memory usage the recommendation is to use a server with higherperformance than the recommended minimum SIM server requirements, or there is a risk thatthe HP DDMI aggregation will underperform.

4.12 HP SERVER AUTOMATIONThe HP Server Automation connector uses an API connection.

For a detailed description, see User guide, HP Server Automation connector.

4.13 IBM BIGFIX INVENTORYThe IBM BigFix Inventory connector uses an API connection.

For a detailed description, see User guide, IBM BigFix connector.

4.14 IBM LICENSE METRIC TOOL (ILMT)The ILMT connector can either use a database connection for ILMT version 7.x or import reportsthat have been exported from ILMT version 7.x or version 9.x.

For a detailed description, see User guide, IBM License Metric Tool connector.


https://snowprod.service-now.com/support/support?id=kb_article_view&sys_kb_id=13ab3b9c0f9b3a405d079acae1050e6c

https://snowprod.service-now.com/support/support?id=kb_article_view&sys_kb_id=c225782e0f06a2002944f88ce1050e64

https://snowprod.service-now.com/support/support?id=kb_article_view&sys_kb_id=971f16790f266e402944f88ce1050ecc

NOTEFor integration with ILMT version 9.x, use the IBM BigFix Inventory connector.

4.15 IBM TIVOLI ASSET DISCOVERY FOR DISTRIBUTEDThe IBM TAD4D connector uses a database (DB2) connection.

For a detailed description, see User guide, IBM TAD4D connector.

4.16 INVENTORY FILE FORWARDERThe Inventory File Forwarder connector reads data from files in a folder.

1. In the Inventory file folder box, type the folder where the connector will look for inventoryfiles.

2. In the Data receiver url box, type the complete URL to the Inventory Data Receiver.

EXAMPLEhttp://idr.snowsoftware.com/Inventory.asmx

3. To verify the connection, click Test.

4. To activate the proxy functionality, click the Use proxy check box.

5. In the Settings section, use the default proxy configured in Internet Explorer by clicking theUse default proxy check box, or configure manual proxy settings by using the boxes.

NOTEThe Inventory File Forwarder does not support client-side certificates.

If an Inventory 5 Server is configured to require client-side certificates, install an Inventory 5Service Gateway on the same server where the Snow Integration Manager is installed.Configure the Inventory File Forwarder to deliver the data to the Service Gateway instead of theInventory Data Receiver (IDR). The Service Gateway will then forward the data to the InventoryMaster Server (or another Service Gateway).


https://snowprod.service-now.com/support/support?id=kb_article_view&sys_kb_id=ec47203a37a94bc09262cea954990ed3

4.17 IQUATE IQSONARThe iQuate iQSonar connector uses a database connection.

For a detailed description, see User guide, iQuate iQSonar connector.

4.18 LANDESKThe LANDesk connector uses a database connection.

For a detailed description, see User guide, LANDesk connector.

4.19 MICROSOFT HYPER-VThe Microsoft Hyper-V connector uses an API connection.

For a detailed description, see User guide, Microsoft Hyper-V connector.

4.20 MICROSOFT OFFICE 365The MS Office 365 connector uses an API connection.

For a detailed description, see User guide, Microsoft Office 365 connector.

4.21 MICROSOFT SCCMThe Microsoft SCCM connector uses a database connection.

For a detailed description, see User guide, Microsoft SCCM connector.

4.22 MOBILEIRONThe MobileIron connector uses an API connection.

For a detailed description, see User guide, MobileIron connector.


https://snowprod.service-now.com/support/support?id=kb_article_view&sys_kb_id=1a83a4fe37694bc09262cea954990e69

https://snowprod.service-now.com/support/support?id=kb_article_view&sys_kb_id=8a9f41283746fac09262cea954990e1e

https://snowprod.service-now.com/support/support?id=kb_article_view&sys_kb_id=617e12390f266e402944f88ce1050e3c

https://snowprod.service-now.com/support/support?id=kb_article_view&sys_kb_id=b610b4410f3936805d079acae1050e88

https://snowprod.service-now.com/support/support?id=kb_article_view&sys_kb_id=a1e1b0210f023ec05d079acae1050ece

https://snowprod.service-now.com/support/support?id=kb_article_view&sys_kb_id=d7d5fc2e0f06a2002944f88ce1050e75

4.23 RED HAT ENTERPRISE VIRTUALIZATIONThe Red Hat Enterprise Virtualization connector uses an API connection.

1. Type a Site name for this collection of Red Hat Enterprise Virtualization servers.This setting will override the Global site id.

2. To add one or more Red Hat Enterprise Virtualization Manager connections to scan forphysical and virtual machines, click Add.The RHEV Server dialog box appears.

3. Type the Name of the data center.

NOTEThis name will only be used for reference in the Snow RHEV Scanner Configurator list.The actual data center name is collected via the API.

4. Type the Webservice url for the Red Hat Enterprise Virtualization Manager API.

EXAMPLEhttps://172.16.7.176/api

5. In the User and Password boxes, type user credentials for an account with access to theRed Hat Enterprise Virtualization Manager API.

6. To verify the connection, click Test.


4.24 SERVICENOW EXPRESSThe ServiceNow Express connector uses an API connection.

For a detailed description, see User guide, ServiceNow Express connector.

4.25 SNOW FOR SERVICENOWSnow for ServiceNow populates and maintains ServiceNow with information from Snow LicenseManager.

The ServiceNow CMDB connector populates ServiceNow with information on all hardware andsoftware assets, and relationships between hardware, software, and users whle the ServiceNowCatalog connector populates ServiceNow with hardware and software models. Both theServiceNow CMDB connector and the ServiceNow Catalog connector use API connections.

For detailed information, see User guide, Installation and configuration of Snow for ServiceNow.

4.26 SNOW DEVICE MANAGERThe Snow Device Manager connector uses an API connection.

1. In the SDM Web API URL box, type the URL to the Snow Device Manager Web API.

2. In the Domain, User Name, and Password boxes, type credentials for a domain useraccount with administrative privileges in the Snow Device Manager platform.

3. To only include information on registered devices, click the Include only enrolled devicescheck box .

4. To verify the connection, click Test connection.





https://snowprod.service-now.com/support/support?id=kb_article_view&sys_kb_id=58851ca70f9876c02944f88ce1050e33

https://snowprod.service-now.com/support/support?id=kb_article_view&sys_kb_id=747e6d2a0f0726002944f88ce1050e56

4.27 SNOW INVENTORY ORACLE SCANNERThe 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 alsoused 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.


4.28 SNOW XMLThe 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/orsoftware inventory system. The Snow XML connector reads data from a structured xml file andconverts it to the standard Snow Inventory format.

1. Browse for a folder where Snow XML will look for xml files.


4.29 VMWARE VSPHEREThe VMware vSphere connector uses an API connection.

For a detailed description, see User guide, VMware vSphere connector.


http://snowprod.service-now.com/support/support?id=kb_article_view&sys_kb_id=ffbf56b90f266e402944f88ce1050ea6

5 IMPORT PROVIDER SETTINGSFrom Snow Integration Manager (named EDP when released) version 4.1 it is possible to importthe active provider settings from an earlier External Data Provider 3.x installation, if installed onthe 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 importthe settings the first time it starts.

Note that this message will be displayed only once regardless of the answer being Yes or No.


6 ABOUT SNOW INTEGRATION MANAGERTo check the version of the installed Snow Integration Manager:

1. In Snow Integration Manager Properties, press F1 on your keyboard.The About – Snow Integration Manager dialog box appears.

2. Click OK to close the About – Snow Integration Manager dialog box.


user guide - snow software · 2 installation ... for a detailed description, see user guide,...

Documents