Software-license import wizard
You can use this wizard to create a rule that imports software licenses from .CSV files, Excel files, and other data sources into Management Suite's software license monitoring (SLM) console. For more information about importing software licenses using DTS, see Software-license importing overview.
DTS also has a licensed software wizard; don't confuse that wizard with this one. Licensed software rules detect the software installed on your devices and group related products by shared licenses.
Open the wizard by right-clicking Software license import in the DTS tree and selecting New rule. Enter a unique name and description for this rule, then select the database where the rule will store the data it gathers. On the continuing pages, enter the following information:
Type: The data-source type. If your data source is not listed, you can connect using the ODBC driver from your software provider. The options on this page will change, depending on the data source you select:
- Filename: The full path of the file to import.
- Headers in the first row: If column headers (names) are in the first row, select this check box.
- Delimiter: The column delimiter used in the .CSV file, such as a comma or tab. By default, the delimiter is a comma.
- Use column numbers instead of names: Select this option if the column names may change, but the data in them stays the same. This is useful if the file headers become localized.
- Character set: The format of the file's character set. U.S. English normally uses the default, which is ANSI. Other languages may need a different set to support their characters.
- Filename: The full path to the Excel file to connect to.
- Sheet: The name of a single sheet in the Excel file to read data from. Each rule will read from only one sheet.
- 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.
- TNS server: The name used to connect to the Oracle server.
- User: The user or schema used to log in to the Oracle server.
- Password: The password for the user.
- Server: The instance to connect to.
- Database: The database to use.
- User: The SQL username to use to connect.
- Password: The SQL username password.
If you selected ODBC, Oracle, or SQL as your data source, this page appears. From here, you can select a table in the remote database that you want to import from.
Table: The name of the database table you want to import data from. Click the ellipsis (…) button to browse tables in the remote database.
Where statement: Use a where statement if you want to limit the table rows that will be imported.
This page lists all columns found in the selected .CSV file, Excel file, or remote database table. You must map at least two columns to attributes in the inventory database—one column must determine uniqueness (along with the product name) and the other must determine the license quantity. Click the Add button to create the mappings.
This page shows the following information:
- Column: All columns in the remote database table, .CSV file, or Excel file.
- Type: The data type of the column (STRING, DATE, and so on).
- Import key: The column(s) used to determine software product uniqueness; for example, the purchase order number is often a good choice. You must mark at least one column as the import key; each one must also be mapped to an attribute. Click the Set import key button to give a column this status.
- License field: The attribute mapping for a column. At least one of the columns must be mapped to the Software.License.Quantity attribute.
- Product key: The column(s) used to determine the software product that the license maps to. If multiple columns are selected, the columns are concatenated with spaces between them. You must mark at least one column as the product key, and the manufacturer's SKU is recommended. Click the Set product key button to give a column this status.
- Description: The column used to describe the software product (for exception handling only). Click the Set description button to give a column this status.
Click the Finish button. Your new rule will appear in the Software License Import > All Rules folder.
If you're importing from a .CSV or Excel file, this page will look different, but the information you need to enter remains the same. You essentially need to map a column in the table or file to a database attribute, while also specifying some details.
Ivanti attribute: The attribute in the inventory database to map to.
Don't overwrite existing value: If a value for the attribute is already in the database, this option prevents it from being overwritten.
Remote database information:
- Column: The column in the table to map to.
- Data type: The data type of the column (STRING, DATE, and so on).
- Instead of column use static value: You can import a number of columns, but set one attribute to a constant value. By selecting this option, you can enter a static value, such as the name of the vendor, and ignore the remote database table.
VBScript: You can use VBScript to modify the incoming data (optional). Click the Test button to verify that the VBScript works.