The following guide is designed to give you a detailed overview of each tab of the integration and the tab’s intended purpose. After installing Cisco Meraki MDM and running your first sync. Your next steps are to:
Enable how your assets are created and updated within iiQ under the General Settings Tab.
Map the location of assets under the Location Mapping Tab.
Map the model for your assets under the Model Mapping Tab.
Run a full sync under the Overview Tab.
Incident IQ Academy:
Visit the Incident IQ Academy for in-depth training and how-to videos on Configuring Asset Management Integrations
You can access the Cisco Meraki MDM Integration app by selecting Incident IQ Apps > Apps Management when installed. This will take you to your Installed Apps page, where you can select the Manage button to access the Cisco Meraki MDM Integration management page.
Overview Tab
The Overview Tab allows you to quickly review the status of the most recent sync between Incident IQ and Cisco Meraki MDM. While syncs will automatically run overnight, you have three additional options:
Start Full Sync - manually start a new sync.
Re-Run Last Sync - re-runs the last sync.
Additionally, you can use the View Details button to take you directly to the Sync History tab where you can review the count of assets updated, added, or skipped over during the most recent sync.
General Settings Tab
The General Settings tab has the settings that control when information is brought in or updated automatically, as well as field mappings between the Cisco Meraki MDM and Incident IQ. As such, you can find the following settings here:
Authentication fields to enter the Cisco Meraki MDM Network ID and API Key.
Options that control if assets are automatically created, updated, and deleted during system syncs.
The ability to turn on automatic room assignment for assets if storing this data in Cisco Meraki.
Custom field asset mapping options to pull in additional data for use in asset filters and custom view columns
Control additional Meraki-iiQ integration settings with Automatic asset assignment
An option to enable the use of remote asset features available in Cisco Meraki directly on an asset detail’s page by administrators and agents with the correct permissions
The Authentication section is where you enter the following fields for Cisco Meraki MDM authentication information:
API Key
Network ID
The Mapping section manages what data is created and updated in Incident IQ based on data coming from Cisco Meraki. This includes:
Create Asset: Selecting this will automatically create assets in iiQ to match any new device discovered in Cisco Meraki during a sync.
Update Asset: Selecting this will automatically update assets in iiQ to match any updates to a device’s data discovered in Cisco Meraki during a sync.
Update Custom Fields: This option will only allow new information being pulled into custom fields to update during a sync.
Delete Asset: Selecting this will automatically delete assets in iiQ to match any assets deletions that have occurred in Cisco Meraki during a sync.
Next, under the Import Options section, you can enable the Create Rooms option. This will automatically create rooms associated with assets in Cisco Meraki MDM if these rooms do not already exist in Incident IQ.
The Matching Rules section controls how devices are matched between the Cisco Meraki and Incident IQ.
These options are read-only for customers and editable by iiQ Admin Employees. This includes the ability to do the following:
Only use the serial number when matching assets between Cisco Meraki and iiQ
When matching assets between Meraki MDM and iiQ, prefer serial number instead of asset tag
Skip creation of assets in iiQ when the asset in merakiMdm does not have a serial number
Only allow one asset for each serial number to be imported
Restore a deleted asset in iiQ if an asset in merakiMdmcan be matched
The Map custom values section allows you to select additional values you want to be imported and map them to default or custom fields in iiQ. This will enable you to pull custom data fields and view column options. Click on the Add button.
Next, fill out the following field mapping options:
Please note that there may be pre-configured mapping, and they can not be changed.
Select the custom value
Select the iiQ field the custom value should map to. You can map to the default field or map to a custom field.
If you map to a Custom Field, you need to set a field name, select a field type (text, number, or date), and set whether the field information needs to be searchable through filters.
Next are the Meraki MDM options, where you can control additional Meraki-iiQ integration settings. This includes the ability to do the following:
Automatically update asset owner in iiQ
Remove existing owner in iiQ for assets that have an empty owner field in Meraki MDM
Remove existing owner in iiQ for assets where the owner field in Meraki MDM can't be matched to a valid user
The last section is the Remote Device Actions. In Incident IQ, you can enable remote device actions that administrators and agents with the correct permissions can access directly on an asset’s details page. These options include:
Cisco Meraki MDM: Remote Wipe Device: Allow a user to wipe a Cisco Meraki MDM managed device remotely.
Cisco Meraki MDM: Remote Lock Device: Allow a user to remotely lock a Cisco Meraki MDM-managed device.
Please see the section below for more details on enabling device actions based on users’ roles.
Location Mappings Tab
This tab allows you to select or modify your current location mappings between iiQ and Cisco Meraki MDM. You can choose to automatically assign a device to a default location in Incident IQ if it does not match any location mappings set. This is especially important if you are using the Cisco Meraki MDM integration to create assets because assets must have a location set automatically.
Location is required for an asset to be created in iiQ. The way this works during a sync is as follows:
If an asset matches the location mapping, then the asset will get created and assigned to the corresponding location the mapping is set to.
If an asset does not match a location mapping, or no location mappings are present, and a default location is selected, then the asset will get created and assigned to the default location.
If an asset does not match a custom mapping, or no custom mappings are present, and there is no default location set, then the asset will not be created during a sync.
The Custom Mapping Options allow you to choose how you would like devices to map in iiQ. You can choose to match by Location Names or by Owner’s location between Cisco Meraki MDM and iiQ.
When Location Name is selected, you will be presented with a list of locations currently in the system. You can choose Auto-Map Location Names to match location names between iiQ and Cisco Meraki MDM. Alternatively, you can manually search for and select your location assignments if needed.
When mapping, if the full name is not visible, simply hover over the name to view the complete name
Map by Owner’s Location will only be available if you enable one of the following Site Options. If you select Map by Owner’s Location this will automatically assign an asset location to the owner's location. Navigate to Site Options to enable the different settings:
Model Mappings Tab
This tab allows you to select or modify your current model mappings between iiQ and the Cisco Meraki MDM. Unmapped models will not be imported into iiQ. You can use the Auto-Map Models button to automatically attempt to match models in your list of devices with existing models in iiQ.
Alternatively, you can manually select what model your device should map to using the drop-down menus to the right of each listed device.
If your device will not auto-map and is unavailable from the drop-down options, it most likely does not currently exist in iiQ. In this case, select the Create New Model button on the right of the device mapping to create and activate this model during your data sync automatically.
Sync History Tab
This tab lets you view your sync history between iiQ and the Cisco Meraki MDMs. Every sync, whether completed successfully or not, is logged for reference purposes and available for review in the View details of a sync list.
Clicking on any sync, in particular, will open that sync’s details. You can review the list of what devices were updated, created, deleted, or skipped during the sync. Additionally, you can narrow down your view by using the filter options at the top of the list.
Asset History Tab
The Asset History tab allows you to search for basic information on any device in your Cisco Meraki MDM. Enter a valid serial number in the Search for asset field to begin your search.
Once you’ve selected a device, you’ll be able to see the following Cisco Meraki MDMs information:
External ID
Model
Owner Email
Organizational Unit
Serial Number
Location Name
You’ll also see a list of actions applied to this device during recent system syncs.
Remote Device Actions
Under the General Settings tab at the bottom of the page, you can enable remote device actions that administrators and agents with the correct permissions can access directly on an asset’s details page in Incident IQ. These options include:
Cisco Meraki MDM: Remote Wipe Device: Allow a user to wipe a Cisco Meraki MDM-managed device remotely.
Cisco Meraki MDM: Remote Lock Device: Allow a user to lock a Cisco Meraki MDM-managed device remotely.
Please note that administrators are given full access to all remote feature permissions by default. However, each of the remote features listed above is controlled by individual permission. This makes it possible to customize which permissions an agent has access to without needing to give them full access to all of the remote features. These permissions can be found underneath the App-Specific section on policies and individual user permissions pages.
You will have access to perform these actions on the asset details page.
---
Reesa Azar- Community Manager