Miradore supports importing certain configuration items from a comma separated values- or a .csv-file. In a .csv-file the field values are separated with a delimiter character, such as a comma or a semicolon and items are on their own separate rows.
There are many ways that can be used to create a .csv-file for import:
- CSV-files exported from Miradore can be used as import files.
- Most common spreadsheet and database applications support exporting data as CSV-files.
- CSV-files can be created in any text editor.
When dealing with CSV-files not created by Miradore export, one should be careful to format the CSV-file in a correct way to ensure proper import. The simple nature of the CSV-files makes precise verification of the imported data impossible, so special care should be taken to verify the data when importing.
It is good to note, that items with invalid or missing fields will not be imported. Items that already exist in the database are not imported. If the item has too many fields, the extra fields are ignored.
|
Instructions |
Navigate to the view of the configuration item you want to import and choose Tasks > Import.
|
|
Click the "Browse…"-button to select the CSV-file and click the "Preview"-button to preview the file. Click the "Continue" -button to continue.
|
|
Finalize the import by verifying that the items that are selected for import are the correct ones. You can exclude items from the import by unchecking the "Include"-checkbox. Click the "Continue"-button to continue or the "Back"-button to go to the previous step.
|
|
Click the "Finish"-button to import the items. |
It’s common to have certain configuration items already configured before Miradore installation, such as many networking-related items. To make installing as easy as possible, the following items can be imported via CSV:
Configuration item |
Fields |
Required field |
Notes |
Custom inventory data |
Device name IP address Custom field 1 Custom field 2 Custom field 3 Custom field 4 Custom field 5 Custom field 6 Custom field 7 Custom field 8 Custom field 9 Custom field 10 |
Yes No No No No No No No No No No No |
|
Cost center |
Name Description LDAP identification string for users LDAP identification string for computers |
Yes No No No |
|
DNS server |
TCP/IP Address Description |
Yes (IP-address format) No |
|
DNS suffix |
DNS Suffix Description |
Yes No |
|
Install point |
Server Share Type Description |
Yes No No No |
Default value for Type is "Network share for Windows" in case the field is left empty in the CSV import file. |
Location |
Name Short name Description |
Yes No No |
The Name field holds the name and path of the Location separated with ‘>’ . The parent should exist before the import of this item. The parent can be imported on the same time as the item, as long as it is in the import list before the child item. |
Organisation |
Name Short name Description |
Yes No No |
The Name field holds the name and path of the Organisation separated with ‘>’ . The parent should exist before the import of this item. The parent can be imported on the same time as the item, as long as it is in the import list before the child item. |
Subnet |
Address Mask Gateway Public IP Status Description |
Yes (IP-address format) Yes (IP-address format) Yes (IP-address format) No (IP-address format) No No |
For performance reasons the subnet validity, such as overlapping and correct addresses are checked when finalizing the subnet import. Status field is required for compatibility with Miradore CSV exports. Regardless of its contents, the imported items will have status ‘Created’. Address, mask and gateway values must establish a valid subnet. Here is an example line from a Subnet import file: "1.3.199.0","255.255.255.0","1.3.199.1","1.3.199.7,1.3.199.8,1.3.199.9","Created","Subnet description" |
WINS server |
TCP/IP Address Description |
Yes (IP-address format) No |
For importing other items, one should refer to the Command Line Tool documentation.
I can not see any fields
Check that the correct delimiter character is selected
Check that the import file has the correct amount of fields
The field values get split into different fields
Check that the fields do not contain delimiter characters. Choose a different character if needed.