This page explains the system settings for asset management.
The system settings for asset management can be found from 'Administration > System settings > Main > Asset management'.
Name generation profiles
Attribute |
Description |
Sequential numbering ranges |
Sequential numbering ranges made into Miradore. |
Asset tag generation profiles made into Miradore. Use the arrow icons to change the order of profiles or the trashbin icon to remove a profile. Notice that the built-in profile cannot be modified or removed. |
|
Device name generation profiles made into Miradore. Use the arrow icons to change the order of profiles or the trashbin icon to remove a profile. Notice that the built-in profile cannot be modified or removed. |
Device naming
Attribute |
Description |
Update device names to match inventory |
This field defines whether an asset configuration item's device name should be automatically updated to match to the value that was found in inventory by Miradore client or SCCM connector. Automated device name changes will be logged to the Asset configuration items' event logs. This feature is enabled by default. |
Asset label printing profiles
Attribute |
Description |
Label printing enabled |
Determines whether the asset label printing feature is enabled or not. (Yes/No) |
Profiles |
Asset label printing profiles made into Miradore. Profiles are ordered in alphabetical order. |
Additional attributes
Attribute |
Description |
Asset tag 2 |
Usage of each additional attribute can be configured separately. Use the Disabled: The attribute is hid from asset configuration form. Enabled: The attribute is displayed as optional attribute on asset configuration form. Required: The attribute is displayed as mandatory attribute on asset configuration form.
Inherit from responsible person determines if the cost center of the asset is updated to user's cost center when responsible person for the asset is changed. The setting becomes available when Cost center is enabled. The default value is Yes.
See also Asset configuration item attributes for detailed field descriptions. |
Company name |
|
Cost center |
|
Inherit from responsible person |
|
Cost center 2 |
|
Detailed location |
|
Device monitoring thresholds |
|
Operating system license key |
|
Password |
|
Planned removal date |
|
Remote management |
|
Shared user id |
Financial transactions
Attribute |
Description |
Non purchase contract name |
This field defines display name for the asset related financial transactions that are called "lease contracts" by default in Miradore Management Suite. This field affects to the naming of the attribute in the asset management views and at the asset configuration item page. |
Online status thresholds
Attribute |
Description |
Offline status limit (sec) |
A device is set automatically offline if client polling interval + offline status limit > last seen time. For example, if polling interval = 3600 seconds and offline status limit = 900 seconds, the device status would be automatically set to offline when 4500 seconds has elapsed since the device was last seen online. |
Unknown status limit (days) |
Time limit when an offline device is marked as unknown. |
Asset status definitions
Attribute |
Description |
Detailed statuses |
You can set up detailed statuses for assets. These describe the current status of an asset in higher detail. |
Status change reason |
You can set up reasons for status changes. These describe the event causing the status change of an asset. |
Detailed status required |
If this option is set to 'yes', then detailed status must be given, when a new status is assigned. If set to 'no', then detailed status is optional. If this option is set to 'disabled', detailed statuses cannot be given. Notice that this setting also affects to the asset data import process. If a detailed status is required, then it must be provided also in the XML file that is used to import assets to Miradore Management Suite. |
Status change reason required |
If this option is set to 'yes', then status change reason must be given, when a new status is assigned. If set to 'no', then status change reason is optional. If this option is set to 'disabled', status change reasons cannot be given. |
Withdrawn from service - Status change options
Attribute |
Description |
Field name (Remove device name, Remove contracts, Remove licenses, Remove responsible person, Remove inventory data) |
These fields are shown on the popup window which is displayed when status of an asset configuration item is changed from 'Active' to 'Withdrawn from service'. With the help of the popup window, the user is able to define which data should be removed from the asset configuration item whose status is changed. |
Default (Yes/No) |
This field determines the default setting of the particular field on the popup window which is shown when status of an asset configuration item is changed from 'Active' to 'Withdrawn from service'. If = Yes, the default value of the field is Yes. |
Forced (Yes/No) |
This field determines whether the particular field is locked or not. The field is shown on the popup window when the status of an asset configuration item is changed from 'Active' to 'Withdrawn from service'. If = Yes, the field cannot be edited and the default value of the field is used. |
Workflows
Attribute |
Description |
Asset confirmation requests |
Asset confirmation request workflow is used to validate asset information on a regular basis by requesting the responsible person of asset to check and confirm the information of the asset(s) that have been assigned to his/her responsibility. If asset confirmation request workflow is enabled, the pending requests are shown in the Asset confirmation requests view. When the feature is disabled, Asset confirmation requests view is hid from the navigation console of Miradore. In addition, the tasks related to the asset confirmation request workflow are hid from the user interface of self service portal. For more information: Asset information update and confirmation How to request responsible person to check asset information |
Send request by |
This field determines how responsible person of device is notified about the asset data confirmation request. The request can be shown to user as desktop message, email, or both. Alternatively, it is possible to disable the notification message by selecting 'None' to this field. |
Send reminder |
This field determines how often the responsible person of device is reminded about pending asset data confirmation request (Daily/Weekly/Never). |
Scheduled requests |
This field defines whether Miradore will automatically send asset confirmation requests to devices defined in Restrictions field. If Scheduled requests = Enabled, Miradore will automatically send asset confirmation requests to devices which match with the scope. The request is sent once in a year on the date, which is defined in Start date field. In addition, Miradore will send a reminder about open requests according to the interval defined in Send reminder field. If Scheduled requests = Disabled, Miradore will not automatically send asset confirmation requests, but Miradore users can still send the requests manually from Assets by name view. In addition, Miradore will send a reminder about open requests according to the interval defined in Send reminder field. |
Start date |
The start date of asset confirmation request workflow defines the day when the asset confirmation request is delivered to assets' responsible persons. |
Restrictions |
This field determines the assets whose responsible persons are requested to confirm the asset information. Notice that single user can be the responsible person for multiple devices. You can use asset group, contract, device role, location, and organization to define the target devices. For example, if Device role = Office PC, the asset data confirmation request is sent only to devices of which role is Office PC. |
Asset data update requests |
This field determines whether the asset data update requests feature is enabled or disabled. When the feature is enabled, the end-user is able to report incorrect or missing asset information concerning his/her assets to Miradore using the self service portal. The asset data update requests are shown in the Asset data update requests view. When the feature is disabled, Asset data update requests view is hid from the navigation console of Miradore. In addition, the tasks related to the asset data update requests are hid from the user interface of self service portal. |
Asset data mismatch |
This field determines if asset data mismatch reporting is enabled or not. When the feature is disabled, Asset data mismatch view is hid from the navigation console of Miradore. Mismatching attributes will not be highlighted on the asset configuration item form. In addition, the event monitor and the quality index indicator for asset data mismatches are disabled. |
IMEI Location Phone number Responsible person Serial number UDID |
These fields determine the attributes that are used in asset mismatch reporting. The available attributes have also an effect to event monitoring and quality index indicators. Mismatching attributes are highlighted on the Asset configuration item form. |
Automatically generated items
Attribute |
Description |
Create items based on client inventory |
This field defines whether Miradore should generate configuration items based on the inventory data collected by Miradore clients. If "Create items based on client inventory = Yes", then the following fields can be used to define which type of configuration items should be automatically generated to Miradore based on the inventory data. If "Create items based on client inventory = No", then the inventory-based autogeneration feature is totally disabled and any items will not be generated automatically to Miradore. |
Asset configurations |
This field defines whether Miradore should automatically generate asset configuration items to Miradore based on the inventory data collected by Miradore clients. If removed asset exists: This setting defines what happens if a previously removed device becomes active, and the installed Miradore client starts to communicate with Miradore server again.
|
Asset models |
This field defines whether Miradore should automatically generate asset model configuration items to Miradore for new asset models based on the inventory data collected by Miradore clients. Notice that Miradore can't automatically generate asset model if the needed hardware manufacturer is missing from Miradore. You can add new hardware manufacturers though the Hardware manufacturers view. |
Operating systems |
This field defines whether Miradore should automatically generate operating system configuration items to Miradore for new operating systems based on the inventory data collected by Miradore clients. |
Subnets |
This field defines whether Miradore should automatically generate subnet items to Miradore for new subnets based on the inventory data collected by Miradore clients. |
Create items from asset import |
This field determines whether Miradore should automatically generate configuration items based on the asset data that is imported to Miradore. If "Create items from asset import = Yes", then the following fields can be used to define which type of configuration items should be automatically generated to Miradore based on the imported data. If "Create items from asset import = No", then the import data-based autogeneration feature is totally disabled and any items will not be generated automatically to Miradore. |
Asset configurations |
This field defines whether Miradore should automatically generate asset configuration items to Miradore based on the data that is imported to Miradore. |
Asset models |
This field defines whether Miradore should automatically generate asset model configuration items to Miradore for new asset models based on the asset data that is imported to Miradore. |
Locations |
This field defines whether Miradore should automatically generate location items to Miradore based on the asset data that is imported to Miradore. |
Cost centers |
This field defines whether Miradore should automatically generate cost center items to Miradore based on the asset data that is imported to Miradore. |
Update asset attributes |
When asset data is imported to Miradore, some of the assets in the import file may already have an asset configuration item in Miradore. This field defines what should be done if the import file contains information of already existing asset configuration items. Options:
|
Create items based on AD inventory |
This section determines what configuration items Miradore should automatically generate to Miradore, based on the data, that is imported from Microsoft Active Directory with Miradore connector for Microsoft Active Directory. |
Cost centers |
This field defines whether Miradore should automatically generate Cost center items based on the inventory data that is imported from Microsoft Active Directory. Automatically generated Cost center items are set to "Created" status in the Cost centers view. Notice! After the auto-generation of Cost center items has been enabled, it is highly recommended to navigate to the AD connector item form, and configure the "Custom attribute(s) for cost center identification". If this is not done, the automatically generated cost center items may have obscure names. |
Instance alias name(s) |
This field defines the instance alias name(s) for this Miradore instance. The instance alias names are used in asset data import files (XML) to specify the Miradore instance where the asset data should be imported to. |
Default asset configuration values if data missing |
The following fields can be used to define default values for some asset configuration item fields. |
Default responsible person |
This field definesthe default user for the autogenerated device. |
Default location |
This field defines the default location of the autogenerated device. |
Default warranty |
This field defines, in months the default warranty period for an asset configuration item. |
Financial transaction |
The following fields can be used to define default purchase information for asset configuration items. |
Type |
This field defines the default transaction type for asset configuration items (Lease or Purchase). |
Date |
This field can be used to define the way how the purchase date of an asset configuration item is filled automatically by default. |
Use OS install date if available |
This field defines whether the operating system installation date should be used as a purchase date for the asset configuration item. |
Hardware type specific default values |
This table can be used to define default hardware category, device role, and device usage for different types of devices. The default values are used for automatically generated asset configuration items. |
MAC address blacklists |
Enter here the MAC addresses that should not be captured to asset configuration items. Enter one MAC address per each line. The format is: xx:xx:xx:xx:xx:xx Example: If you use a shared Ethernet adapter to install devices, you probably don't want the adapter's MAC address to be recorded for all asset configuration items that you have installed. Good to know: MAC address is one of the attributes that is used to identify devices. Therefore, it is important not to record the same MAC address for multiple asset configuration items. |
User form
Attribute |
Description |
Lock user form (Yes/No) |
Determines whether the user form is locked after saving or not. If users are locked, the user forms cannot be edited. |
See also