You can use the enterprise-aggregator import wizard to import data from an enterprise database into inventory, where you can apply the features of Data Analytics to make the data far more useful for reporting and auditing purposes. For each enterprise database, you need to do the following:
l Configure a rule that provides a way to connect to the enterprise database.
l Update attribute mappings between the enterprise and inventory 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.)
l Run the rule to import the enterprise data into the inventory database.
When importing data, no changes are ever made to the existing enterprise databases.
For information about configuring a rule for an enterprise aggregator, select one below.
AirWatch Import
Enter your login information to the AirWatch site server database.
l Server: The SQL server instance for the site server. Enter the server name or
<server>\<instance>,<port>.
l Database: The name of the site server database, normally SMS <site code>.
l Use integrated security: Select if you're accessing the SQL server using Windows integrated security.
l User: The SQL server username.
l Password: The password for the SQL server username.
Click the Finish button. Your new rule will appear in the Enterprise Aggregators > AirWatch Import
If you customized any 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 LANDesk 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 LANDesk 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:
l 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.
l You can also use a VBScript to modify the value coming from the AirWatch database.
BigFix Import
Enter your login information to the BigFix site server database.
SQL
l Server: The SQL server instance for the site server. Enter the server name or
<server>\<instance>,<port>.
l Database: The name of the site server database, normally SMS <site code>.
l Use integrated security: Select if you're accessing the SQL server using Windows integrated security.
l User: The SQL server username.
l Password: The password for the SQL server username.
OBDC
l 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.
l User: The username, if needed.
l 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 customized any 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 LANDesk 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 LANDesk 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:
l 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.
l You can also use a VBScript to modify the value coming from the BigFix database.
JAMF Import
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.
Set up MySQL client on the core server
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 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, use this page to enter your MySQL connection information to the JAMF site server database.
l Server: The MySQL instance for the site server you want to connect to.
l Port: The MySQL server port number. By default, it's 3306.
l Schema: The MySQL schema you want to connect to.
l User: The MySQL username.
l Password: The password for the MySQL username.
Page 2:
This page shows a listing of all the 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.
l Perform import now: Performs an import immediately after you click the Finish button.
Page 3:
This page enables you to update attribute mappings between the JAMF and inventory databases if necessary. If you haven't customized data in either database, you can skip this process.
The LANDesk 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 LANDesk 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.
Page 4:
Use this page to set more options for an attribute mapping.
l 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.
l 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.
SCCM Import
Use this page to enter your login information to the SCCM site server database.
l Server: The SQL server instance for the site server. Enter the server name or
<server>\<instance>,<port>.
l Database: The name of the site server database, normally SMS <site code>.
l Use integrated security: Select if you're accessing the SQL server using Windows integrated security.
l User: The SQL server username.
l Password: The password for the SQL server username.
Page 2:
This page shows a listing of all the 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.
l Perform import now: Performs an import immediately after you click the Finish button.
Page 3:
This page enables you to update attribute mappings between the SCCM and inventory databases if necessary. If you haven't customized data in either database, you can skip this process.
The LANDesk 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 LANDesk 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.
Page 4:
Use this page to set more options for an attribute mapping.
l 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.
l 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.