user guide - snow software · user guide product snow integration manager version 4.7 release date...

USER GUIDEProduct Snow Integration Manager

Version 4.7

Release date 2016-05-16

Document date 2016-08-30

SNOWSOFTWARE.COM

CONTENTSIntroduction ................................................................................................................................ 4

Prerequisites ........................................................................................................................ 4

Installation ................................................................................................................................. 5

Configuration .............................................................................................................................. 6

General ................................................................................................................................ 6

Inventory File handling ......................................................................................................... 7

Local Inventory server .................................................................................................. 7

Remote Inventory server .............................................................................................. 7

Software filtering .......................................................................................................... 8

Connector options .............................................................................................................. 10

VMware AirWatch ....................................................................................................... 11

Symantec Altiris .......................................................................................................... 12

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

Citrix XenServer .......................................................................................................... 15

Dell KACE 1000 ........................................................................................................... 20

FrontRange Discovery ................................................................................................. 21

HEAT Discovery ........................................................................................................... 22

HP Discovery & Dependency Mapping Inventory ........................................................ 23

HP Server Automation ................................................................................................ 24

IBM BigFix Inventory ................................................................................................... 25

IBM License Metric Tool .............................................................................................. 26

IBM Tivoli Asset Discovery for Distributed ................................................................... 28

Inventory File Forwarder ............................................................................................. 29

iQuate iQSonar ........................................................................................................... 30

LANDesk ..................................................................................................................... 31

Microsoft Hyper-V ....................................................................................................... 32

Microsoft SCCM .......................................................................................................... 34

MobileIron .................................................................................................................. 36

Red Hat Enterprise Virtualization ................................................................................ 37

ServiceNow ................................................................................................................. 38

ServiceNow Scoped Application .................................................................................. 39

Snow Device Manager ................................................................................................ 40

Snow Inventory Oracle Scanner .................................................................................. 41

Snow Xml ................................................................................................................... 42

VMware vSphere ......................................................................................................... 43

Logging ............................................................................................................................... 45

Import provider settings .......................................................................................................... 46

of 47 SNOWSOFTWARE.COM

About Snow Integration Manager ............................................................................................ 47


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

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.

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


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

ftp://ftp.snowsoftware.com

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

1. Uninstall any previous versions of Snow Integration Manager (or Snow External DataProvider).

2. To start the installation, double-click the file SetupSIM.exe.

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

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

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

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

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


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

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


INVENTORY FILE HANDLINGSelect method for handling of inventory data.

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. Specify the incoming folder in the Inventory incoming file folder box.

EXAMPLEC:\Program Files\Snow Software\Snow Inventory\Data\Incoming

REMOTE INVENTORY SERVERWhen sending the inventory data to a remote inventory server (i.e. 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.

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.


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.


VMWARE AIRWATCHThe AirWatch connector uses an API connection.

1. In the API URL (Host) box, type the URL to the AirWatch Web API.

EXAMPLEhttps://de.airwatch.net/snowsoftware

2. In the User Id and Password boxes, type credentials for a user account with access to theAirWatch Web API. The account needs to have the API role assigned.

3. Type the token for AirWatch authentication in the Authentication token box.

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

5. To verify the connection, click Test connection.

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.

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


SYMANTEC ALTIRISThe Symantec Altiris 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 Symantec Altiris database in the User id and Passwordboxes.

■ Click the Use integrated security check box.

3. In the Database list, select database.






BMC ATRIUM DISCOVERY AND DEPENDENCY MAPPINGThe BMC ADDM connector uses an API connection.

DATA CONNECTION

1. Click the Data connection tab.

2. In the Server box, type the server URL.

EXAMPLEhttps://192.168.5.2

3. Type user credentials for the server connection in the User id and Password boxes.






FILTERING

1. Click the Filtering tab.

2. To include or exclude computers, define a filter based on a computer attribute. Multiplecriteria can be used in the filter.

3. To add the created filter, click Add.

4. To test the filter and check the result, click Preview.

5. To remove a created filter, click Remove.


CITRIX XENSERVERThe Citrix XenServer connector uses an API connection.

1. Type a Site name for this collection of XenServer servers.

2. To add one or more XenServer servers to scan for virtual machines, click Add.The Citrix XenServer dialog box appears.

3. Type the Name of the server.

4. To use the typed name of the server instead of the default name, click the Use this name asdatacenter name checkbox.

5. Select whether HyperThreading is enabled on the hosts to ensure that correct processorcore count is reported to Snow License Manager.

6. Type IP address, Port, User account, and Password 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 box.

9. Click OK to save the settings.


NOTETo configure the Citrix XenServer connector for a scenario where the Pool Master is changedregularly; add all XenServer hosts, use the same Name for all hosts, and select the Use thisname as datacenter name check box for all hosts.

When SIM goes through the list of hosts, it will only collect information from the current PoolMaster.

XENSERVER TOOLS

The connector will be able to extract more information from virtual machines with XenServer Toolsinstalled. 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 runningthat 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 isused:

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 startinghost).

3. If the host could not be inferred, the VM is ignored.

XENSERVER CONNECTOR AND SSLConfigure the connector to communicate over HTTPS by specifying port 443 in the server settings.

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 atrusted certificate authority, or add XenServer’s self-signed certificate to the client machine’s


trusted certificate store. For information on how to replace XenServer’s default certificate, refer tothe XenServer documentation.

To trust the self-signed certificate, perform the following steps on the machine that the connectoris 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 then click View certificates.


6. In the Certificate dialog, click Install Certificate...

7. The Certificate Import Wizard is started.

8. Select Local Machine, and then click Next.


9. Select Place all certificates in the following store.

10. Click Browse, and then 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 overHTTPS without getting a certificate warning.


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

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


■ Type user credentials for the Dell KACE 1000 database in the User id and Passwordboxes.


3. Type the name of the Database.






FRONTRANGE DISCOVERYThe FrontRange Discovery connector uses a database connection.



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




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.





HEAT DISCOVERYThe HEAT Discovery connector uses a database connection.



■ Type user credentials for the HEAT Discovery database in the User id and Passwordboxes.








HP DISCOVERY & DEPENDENCY MAPPING INVENTORYThe 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 riskthat the HP DDMI aggregation will underperform.


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

1. In the Server box, type the server URL.


2. Type user credentials for the server connection in the User id and Password boxes.




6. Optionally, type a site Id for this connector

KNOWN LIMITATIONS

When gathering inventory data from HP Server Automation (HPSA) using this integrationconnector the actual servers running the HPSA software itself will not be included and presentedin Snow License Manager.

This is due to a limitation in the HPSA API that excludes these servers from the list of devicesmanaged by HPSA.


IBM BIGFIX INVENTORYThe IBM BigFix Inventory connector uses an API connection, and can be used for gathering datafrom both BigFix Inventory and ILMT version 9 (based on BigFix).

1. In the BigFix Web API URL box, type the URL to the BigFix Web API.


2. In the User Id and Password boxes, type credentials for a user account with access to theBigFix Web API. Use the credentials of a valid Console operator.

3. The BigFix inventory port and BigFix platform port boxes show the default ports set byIBM. The ports can be changed.






IBM LICENSE METRIC TOOLThe IBM License Metric Tool connector can either use a database connection or import reportsthat have been exported from IBM ILMT.

DATABASE CONNECTION

1. In the Input Source section, select the DB2 database option.

2. In the Server text box, type the DB2 server name.

3. Type user credentials for the IBM License Metric Tool database in the User id and Passwordboxes.

4. In the Database box, type the name of the database.

5. In the Port box, type the database server port.


7. In the Period for peak capacity reporting box, type the number of days to be included inthe period for Sub Capacity Reporting.





CSV FILES

1. In the Input Source section, select the CSV files option.

2. In the Folder text box, type the folder where the connector will look for inventory files.

3. In the Mappings section, select ILMT version; ILMT v 7.x or ILMT v9.x.

4. Map the Target fields to the Source fields in the ILMT file.Either type the Source fields manually, or click Get headers from file to use the header ofan import file as template. Then click on each Source row and select a field from the list thatis shown.





IBM TIVOLI ASSET DISCOVERY FOR DISTRIBUTEDThe IBM TAD4D connector uses a database connection.

1. In the Server text box, type the DB2 server name.

2. Type user credentials for the IBM TAD4D database in the User id and Password boxes.

3. Type the name of the Database.

4. Type the Port of the database server.


6. In the Period (days) field, select the number of days to be included in the period for SubCapacity Reporting.





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


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

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

6. 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.


IQUATE IQSONARThe iQSonar connector uses a database connection.



■ Type user credentials for the iQSonar database in the User id and Password boxes.








LANDESKThe LANDesk connector uses a database connection.



■ Type user credentials for the LANDesk database in the User id and Password boxes.








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

1. Type 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.The Microsoft Hyper-V Server dialog box appears.

3. In the Server name or IP box, type the hostname or IP address of the server (type “.” forlocalhost).

4. Specify whether this is a single Hyper-V server or a VMM server controlling one or moreHyper-V hosts.For a VMM server, select whether HyperThreading is enabled on the hosts to ensure thatthe correct number of processor cores is reported to Snow License Manager

5. Type logon credentials in the User (username or DOMAIN\username) and Password boxes.

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, click theRemove domain suffix… check box.



SYSTEM REQUIREMENTS

■ When running SIM from Windows 7 or Windows Server 2008, Windows ManagementFramework 3.0 must be installed.

■ Logon credentials:

○ Standalone Hyper-V servers:

■ The credentials must have access to the server’s WMI interface.

○ 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 MachineManager Console on the VMM server (in the console, go to Settings|Userroles).

■ VMM servers: Make sure that PowerShell Remoting is enabled on the server.Example of PowerShell script:

Enable-PSRemoting -Force

If the connection fails to a server that is not a member of the domain, or if connection by IPaddress is used, the server’s IP address (or name) might need to be added to “TrustedHosts” onthe local computer. Example of PowerShell script:

set-Item wsman:\localhost\Client\TrustedHosts -Value “xxx.xxx.xxx.xxx, xxx.xxx.xxx.xxx, …”

NOTEThe recommendation is to either install the Snow Inventory Client for Windows on the virtualmachines 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


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

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

https://www.poweradmin.com/help/faqs/how-to-enable-wmi-for-remote-access/

MICROSOFT SCCMThe Microsoft SCCM connector uses a database connection.

DATA CONNECTION

1. Click the Data connection tab.



■ Type user credentials for the SCCM database in the User id and Password boxes.






8. Select Identifier.



DATA SOURCE OPTIONS

The SCCM data source options gives a better overview of the SCCM setup and what views andfields the Snow Integration Manager is able to aggregate from. It is also possible to apply filters tocollections and clients.

1. Click the Data source options tab.

2. Collection filterIn the Collection filter (Site ID) box, type the Site ID’s that clients will be aggregated from.Use semi colon as separator.

3. Client filterIn the Client filter box, type the names of the clients that will be aggregated.Use semi colon as separator.A wildcard character (* or %) can be used to match several clients.

EXAMPLEType STO-* for all clients with a name beginning with “STO-“.

4. Enable Apply software exclusion filters to metering data by clicking the check box.

5. To test the filters, click Preview.

■ Select the Use config value check box to use the last aggregation date.Note that this will either be the last aggregation date if such a value exists, or todaysdate subtracted with the number of months specified for initial aggregation.

■ Clear the Use config value check box to select a manual date for the preview.


MOBILEIRONThe MobileIron connector uses an API connection.

1. In the Core Admin Portal URL box, type the URL to the MobileIron Core Admin Portal.

EXAMPLEhttps://de.mobileiron.net/snowsoftware

2. In the User Name and Password boxes, type credentials for a user account in theMobileIron Core Admin Portal. The account needs to have the API role assigned.






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.



SERVICENOWThe ServiceNow connector uses an API connection.

NOTE

■ Use the ServiceNow connector for the ServiceNow releases Dublin, Eureka, and Fuji (upto patch 8).

■ Prior to configuring the ServiceNow connector, apply the Snow CMDB Integrationupdate set to the ServiceNow instance.

■ A user account is required for ServiceNow web services authentication. The useraccount needs to be associated with the soap, import_transformer, itil, and samroles.

1. In the SLM Web API URL box, type the URL to the Snow License Manager Web API.

2. In the User Name and Password boxes, type credentials for a user account withadministrative privileges in the Snow License Manager platform.

3. To verify the SLM connection, click Test connection.

4. For SPE platforms onlyIn the Customer list, select the customer for whom information will be replicated.

5. In the ServiceNow URL box, type the URL to the ServiceNow instance.

6. In the User Name and Password boxes, type user credentials for an administrative accountin the ServiceNow platform.

7. To verify the ServiceNow connection, click Test connection.

8. To exclude replication of inventory information on users, clear the Include Users check box(the check box is selected by default).

9. To reset an ongoing incremental import and perform a full import instead, click Clear LastImport Date.


SERVICENOW SCOPED APPLICATIONThe ServiceNow Scoped Application connector uses an API connection.

NOTE

■ Use the ServiceNow Scoped Application connector for the ServiceNow releases Fuji(from patch 9) and Geneva.

■ Prior to configuring the ServiceNow Scoped Application connector, install the SnowCMDB Integration scoped application from the ServiceNow Store.

■ A user account is required for ServiceNow web services authentication. The useraccount needs to be associated with the x_snsab_snow_cmdb.snw role.

1. In the SLM Web API URL box, type the URL to the Snow License Manager Web API.

2. In the User Name and Password boxes, type credentials for a user account withadministrative privileges in the Snow License Manager platform.

3. To verify the SLM connection, click Test connection.

4. For SPE platforms onlyIn the Customer list, select the customer for whom information will be replicated.

5. In the ServiceNow URL box, type the URL to the ServiceNow instance.

6. In the User Name and Password boxes, type user credentials for an administrative accountin the ServiceNow platform.

7. To verify the ServiceNow connection, click Test connection.

8. To exclude replication of inventory information on users, clear the Include Users check box(the check box is selected by default).

9. To reset an ongoing incremental import and perform a full import instead, click Clear LastImport Date.


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 .






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.



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.



VMWARE VSPHEREThe VMware vSphere connector uses an API connection.

1. Type 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.The vSphere Server dialog box appears.

3. Type the Name of the server.

4. To use the typed name instead of vSphere’s default “ha-datacenter” name, click the Use thisname as default name for data center check box.

5. Type the Webservice url and user credentials to access the server’s VMware vSphere WebServices SDK.



https://www.vmware.com/support/developer/vc-sdk/

https://www.vmware.com/support/developer/vc-sdk/

NOTE

■ The user account that is used for access should be assigned the vCenter Server RoleRead-only (minimum requirement) or higher.

■ To have the complete license key for each vSphere host displayed in Snow LicenseManager, the user account needs to be assigned a vCenter Server Role with the grantedprivilege Licenses of the Global privilege category.


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


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.


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 · user guide product snow integration manager version 4.7 release date...

Documents