Enterprise aggregators

You can use DTS to import device data from various enterprise databases into Management Suite inventory. By aggregating the data in one place, it becomes much easier to use for reporting and auditing purposes. DTS imports the data without making any changes to the enterprise database.

Under the Enterprise Aggregators folder in the DTS tree view, you'll find folders for currently supported enterprise databases. This list will continue to grow with new releases of Data Analytics.

Importing data from an enterprise database is a two- or three-step process, depending on whether you have customized any of your data. For each enterprise database from which you want to import data, do the following:

•Configure a rule that provides a way to connect to the enterprise database.

•Update attribute mappings between the databases in order to move data accurately from one to the other. (This step is only necessary if you've customized data in either the enterprise or inventory database; otherwise, you can skip this process.)

•Run the rule to import the enterprise data into the inventory database.

You can accomplish several tasks related to importing enterprise-database data by accessing the right-click menus from the individual enterprise-database folders.

Add group: Creates a group folder that you can use for organizing rules; drag and drop the rules from other folders into this new one. Grouping is useful for running a series of rules together.

Import group: Imports a group folder from an .XML file. This action doesn't import the group's rule configurations, just the definition of which rules are in the group. You must import the rule configuration files separately into the target databases; otherwise, you'll be importing an empty group folder.

New rule: Opens a wizard for creating a new rule configuration.

Update attribute mappings: Enables you to connect to the enterprise database and then update the attribute mappings between the inventory and enterprise databases to ensure data is moved accurately across them. It may be necessary to update the mappings if you've changed the naming conventions for attributes or stored them in different areas. By default, the most commonly used attributes in both schemas are already mapped.

Once you connect to the enterprise database, a dialog will open that displays two tree views: one view (labeled "Internal") lists all Ivanti attributes defined in the Management Suite schema, and the other lists all attributes defined in the enterprise database's schema. From here, you can update the attribute mappings.

Import attribute mappings: Imports the attribute mappings between an enterprise database and the inventory database from an .XML file, which is useful in a multi-core environment.

Export attribute mappings: Exports the attribute mappings between an enterprise database and the inventory database to an .XML file, which is useful in a multi-core environment.

Supported enterprise databases

For details on configuring a rule for a supported enterprise database, select one below.

Under Enterprise Aggregator in the DTS tree, right-click AirWatch Import and select New rule to open the wizard. After naming the rule, enter the login information for your AirWatch database:

  • Server: The SQL server instance for the site server. Enter the server name or <server>\<instance>,<port>.
  • Database: The name of the SQL server database.
  • Use integrated security: Select if you're accessing the SQL server using Windows integrated security.
  • User: The SQL server username (needed when Windows integrated security isn’t used).
  • Password: The password for the SQL server username (needed when Windows integrated security isn’t used).

Click the Finish button. Your new rule will appear in the Enterprise Aggregators > AirWatch Import > All Rules folder.

If you have customized data in either the AirWatch or inventory databases, you need to update the attribute mappings between them before running the rule. Right-click AirWatch Import and select Update attribute mappings. Select settings to connect to the correct database, then click the Connect button.

The dialog that appears will show a Internal tree view listing all attributes defined in the Management Suite schema, and a AirWatch tree view listing all attributes defined in the AirWatch schema. By default, most attributes in both schemas are already mapped.

To map an attribute, select an attribute in the Internal tree and one in the AirWatch tree and click the Add button. This action will add the attribute to the bottom list. Click the Remove button to delete the highlighted entries from the mapping list.

You may need to set more options for an attribute mapping:

  • Set as auto-incrementing value: Use for one-to-many attributes where the key field is a number. This option sets the value of that attribute to an incrementing number.
  • You can also use a VBScript to modify the value coming from the AirWatch database.

Under Enterprise Aggregator in the DTS tree, right-click BigFix Import and select New rule to open the wizard. After naming the rule, enter the login information for your BigFix database:

For SQL:

  • Server: The SQL server instance for the site server. Enter the server name or <server>\<instance>,<port>.
  • Database: The name of the SQL server database.
  • Use integrated security: Select if you're accessing the SQL server using Windows integrated security.
  • User: The SQL server username (needed when Windows integrated security isn’t used).
  • Password: The password for the SQL server username (needed when Windows integrated security isn’t used).

For OBDC:

  • DSN: The name of the DSN created. The name must be a System DSN for the rule to work as a scheduled task or at scan time.
  • User: The username, if needed.
  • Password: The password, if needed.

Click the Finish button. Your new rule will appear in the Enterprise Aggregators > BigFix Import > All Rules folder.

If you have customized data in either the BigFix or inventory databases, you need to update the attribute mappings between them before running the rule. Right-click BigFix Import and select Update attribute mappings. Select settings to connect to the correct database, then click the Connect button.

The dialog that appears will show a Internal tree view listing all attributes defined in the Management Suite schema, and a BigFix tree view listing all attributes defined in the BigFix schema. By default, most attributes in both schemas are already mapped.

To map an attribute, select an attribute in the Internal tree and one in the BigFix tree and click the Add button. This action will add the attribute to the bottom list. Click the Remove button to delete the highlighted entries from the mapping list.

You may need to set more options for an attribute mapping:

  • Set as auto-incrementing value: Use for one-to-many attributes where the key field is a number. This option sets the value of that attribute to an incrementing number.
  • You can also use a VBScript to modify the value coming from the BigFix database.

Under Enterprise Aggregator in the DTS tree, right-click HEAT Import and select New rule to open the wizard. After naming the rule, enter the login information for your HEAT database:

  • Server: The SQL server instance for the site server. Enter the server name or <server>\<instance>,<port>.
  • Database: The name of the SQL server database.
  • Use integrated security: Select if you're accessing the SQL server using Windows integrated security.
  • User: The SQL server username (needed when Windows integrated security isn’t used).
  • Password: The password for the SQL server username (needed when Windows integrated security isn’t used).

Click the Finish button. Your new rule will appear in the Enterprise Aggregators > HEAT Import > All Rules folder.

If you have customized data in either the HEAT or inventory databases, you need to update the attribute mappings between them before running the rule. Right-click HEAT Import and select Update attribute mappings. Select settings to connect to the correct database, then click the Connect button.

The dialog that appears will show a Internal tree view listing all attributes defined in the Management Suite schema, and a HEAT tree view listing all attributes defined in the HEAT schema. By default, most attributes in both schemas are already mapped.

To map an attribute, select an attribute in the Internal tree and one in the HEAT tree and click the Add button. This action will add the attribute to the bottom list. Click the Remove button to delete the highlighted entries from the mapping list.

You may need to set more options for an attribute mapping:

  • Set as auto-incrementing value: Use for one-to-many attributes where the key field is a number. This option sets the value of that attribute to an incrementing number.
  • You can also use a VBScript to modify the value coming from the HEAT database.

Before you can import JAMF database information into inventory, you must first install MySQL drivers on the core server. Do this by setting up a custom install of MySQL client.

At your core server, access the MySQL website. Navigate to the page where you can download and run the installer package file mysql-installer-community-5.6.14.0.msi. It's important that you install this version of the .MSI file, not a newer version.

Open the MySQL installer and follow these steps:

  1. MySQL Installer Welcome page—Click Install MySQL Products.
  2. Find Latest Products page—Select the Skip the check for updates (not recommended) option. Click the Next button.
  3. Setup Type page—Select the Custom option and click the Next button.
  4. Feature Selection page—In the Product Catalog drop-down box, select MySQL 5.6 Community Edition to install. Clear all options on the page except for MySQL Connectors > Connector/NET 6.7.4. Click the Next button.
  5. Check Requirements page—Click the Next button.
  6. Installation page—Click the Execute button. After installation success, click the Next button.
  7. Complete page—Click the Finish button. Copy MySQL.Data.dll from \program files\MySQL\Connector NET 6.7.4\Assemblies\RT\v2.0 to the \program files\landesk\Management Suite directory.

After completing the MySQL client install, start the import wizard. Under Enterprise Aggregator in the DTS tree, right-click JAMF Import and select New rule. After naming the rule, enter the MySQL login information for your JAMF database:

  • Server: The MySQL instance for the site server you want to connect to.
  • Port: The MySQL server port number. By default, it's 3306.
  • Schema: The MySQL schema containing the data to import.
  • User: The MySQL username.
  • Password: The password for the MySQL username.

On the next page of the wizard is a list of all collections found in the JAMF database (in the Available Targets pane). For collections that you want pulled into inventory, use the arrow keys to move them to the Selected Targets pane. Click the Perform import now button to start an import immediately after you finish the wizard.

The next page enables you to update attribute mappings between the JAMF and inventory databases if necessary. (If you haven't customized data in either database, skip this process.) The Internal tree view lists all attributes defined in the Management Suite schema, and the JAMF tree view lists all attributes defined in the JAMF schema. By default, most attributes in both schemas are already mapped. To map an attribute, select an attribute in the Internal tree and one in the JAMF tree and click the Add button. This action will add the attribute to the bottom list. Click the Remove button to delete the highlighted entries from the mapping list.

Finally, you may need to set more options for an attribute mapping:

  • Set as auto-incrementing value: Use for one-to-many attributes where the key field is a number. This option sets the value of that attribute to an incrementing number.
  • You can also use a VBScript to modify the value coming from the JAMF database.

Click the Finish button. Your new rule will appear in the Enterprise Aggregators > JAMF Import > All Rules folder.

Under Enterprise Aggregator in the DTS tree, right-click SCCM Import and select New rule to open the wizard. After naming the rule, enter the login information for your SCCM database:

  • Server: The SQL server instance for the site server. Enter the server name or <server>\<instance>,<port>.
  • Database: The name of the SQL server database, normally SMS <site code>.
  • Use integrated security: Select if you're accessing the SQL server using Windows integrated security.
  • User: The SQL server username (needed when Windows integrated security isn’t used).
  • Password: The password for the SQL server username (needed when Windows integrated security isn’t used).

On the next page of the wizard is a list of all collections found in the SCCM database (in the Available Targets pane). For collections that you want pulled into inventory, use the arrow keys to move them to the Selected Targets pane. Click the Perform import now button to start an import immediately after you finish the wizard.

The next page enables you to update attribute mappings between the SCCM and inventory databases if necessary. (If you haven't customized data in either database, skip this process.) The Internal tree view lists all attributes defined in the Management Suite schema, and the SCCM tree view lists all attributes defined in the SCCM schema. By default, most attributes in both schemas are already mapped. To map an attribute, select an attribute in the Internal tree and one in the SCCM tree and click the Add button. This action will add the attribute to the bottom list. Click the Remove button to delete the highlighted entries from the mapping list.

Finally, you may need to set more options for an attribute mapping.

  • Set as auto-incrementing value: Use for one-to-many attributes where the key field is a number. This option sets the value of that attribute to an incrementing number.
  • You can also use a VBScript to modify the value coming from the SCCM database.

Click the Finish button. Your new rule will appear in the Enterprise Aggregators > SCCM Import > All Rules folder.

Under Enterprise Aggregator in the DTS tree, right-click Solarwinds Import and select New rule to open the wizard. After naming the rule, enter the login information for your Solarwinds database:

  • Server: The SQL server instance for the site server. Enter the server name or <server>\<instance>,<port>.
  • Database: The name of the SQL server database.
  • Use integrated security: Select if you're accessing the SQL server using Windows integrated security.
  • User: The SQL server username (needed when Windows integrated security isn’t used).
  • Password: The password for the SQL server username (needed when Windows integrated security isn’t used).

On the next page of the wizard, select to import your Solarwinds device data into both Asset Control and inventory, or just one of those databases.

  • Import devices into Asset Control: For device records going into Asset Control, you can select to import all device types (excluding computers), or specify specific device types (such as routers, switches, printers, and so on) by clicking the Add button.
  • Import the following types as computers: To import certain computer types into inventory, click the Add button. Windows servers are imported by default.

Click the Finish button. Your new rule will appear in the Enterprise Aggregators > Solarwinds Import > All Rules folder.

If you have customized data in either the Solarwinds or inventory database, you need to update the attribute mappings between them before running the rule. Right-click Solarwinds Import and select Update attribute mappings. Select the settings to connect to the correct database, then click the Connect button.

The dialog that appears will show an Internal tree view listing all attributes defined in the Management Suite schema, and a Solarwinds tree view listing all attributes defined in the Solarwinds schema. By default, most attributes in both schemas are already mapped.

To map an attribute, select an attribute in the Internal tree and one in the Solarwinds tree and click the Add button. This action will add the attribute to the bottom list. Click the Remove button to delete the highlighted entries from the mapping list.

Under Enterprise Aggregator in the DTS tree, right-click WinMagic Import and select New rule to open the wizard. After naming the rule, enter the login information for your WinMagic database:

  • Type: Select SQL.
  • Server: The SQL server instance for the site server. Enter the server name or <server>\<instance>,<port>.
  • Database: The name of the SQL server database.
  • Use integrated security: Select if you're accessing the SQL server using Windows integrated security.
  • User: The SQL server username (needed when Windows integrated security isn’t used).
  • Password: The password for the SQL server username (needed when Windows integrated security isn’t used).

Click the Finish button. The rule will appear in the Enterprise Aggregators > WinMagic Import > All Rules folder. From the All Rules folder, you can run the rule by right-clicking it and selecting Run Now.

As the rule runs, it will connect to your WinMagic database and import the device data into Management Suite inventory. During the import process, no changes will be made to your WinMagic database.

If you want to run this rule periodically, right-click it and select Schedule to create a scheduled task.

The following inventory data will display for your WinMagic-enabled devices under the Computer.Security.Data Protection component in the console:

  • Encryption Status
  • Encryption Type
  • Installed
  • Last Sync Time
  • Product Version
  • Profile Name
  • Protected Date