This page is intended to provided assists for IT staff in monthly maintenance of Miradore. The following table describes the recommended maintenance tasks and gives brief instructions for performing them.
# |
Task name |
How to check |
How to fix |
1. |
Check removed or dysfunctional Miradore clients. |
Navigate to Operations > Software management > Inventory reports > Windows devices > Miradore clients and enter “Unknown” as a search phrase to the Online status column. Check the results for assets with unknown status and consider if the assets are removed assets or is the client dysfunctional. |
Repair dysfunctional client installations or configurations and remove non-existing or redundant assets. Also find out the reason why the assets were removed before removing them from Miradore. |
2. |
Check Miradore client versions. |
Navigate to Operations > Software management > Inventory reports > Windows devices > Miradore clients and open summary tab and select dimension Miradore client version. Check whether the clients are using the latest version of the Miradore client. |
Verify that the latest version of Miradore client is available at the installation points (…\System\Miradore\_Current) and check that the automatic upgrade of Miradore client is enabled from the System settings > Clients > Windows client at the management console of Miradore. Check also the upgrade rules. |
3. |
Check the logs of Miradore client connector. |
Check logs for errors at Miradore installation directory (..\Logs\MDCC_yyyy-mm-dd\...) |
Check the status of Miradore client connector service and database connection or restart the service or Miradore server. |
4. |
Check the logs of system task engine. |
Check logs for errors at Miradore installation directory (..\Logs\MDSTE_yyyy-mm-dd\...) |
Check the status of Miradore Server Scheduled Task Engine service and database connection or restart the service or Miradore server. |
5. |
Remove redundant installation points. |
Navigate to Administration > Installation settings > Installation points in the Miradore management console. Check that the number of bindings is not 0, or the amount of installation during last 30 days is not 0. |
Remove redundant installation points from Miradore and replication automation. |
6. |
Check the following auto-generated items:
|
Navigate to the particular view (listed below) in the Miradore management console and search for items in status AutoGenerated. Asset: Operations > Asset management > Assets Asset model: Operations > Asset management > Models Subnet: Administration > Basic settings > TCP/IP settings > Subnets |
Fill in the missing details and activate the auto-generated item or remove it. Notice that in the implementation phase of Miradore, the auto-generated items should be at least daily. |
7. |
Check the following items waiting for approval:
|
Navigate to the particular view (listed below) in the Miradore management console and search for items in status Waiting for Approval. Asset model: Operations > Asset management > Models Managed software: Operations > Software management > Managed software Package: Operations > Software management > Packages Subnet: Administration > Basic settings > TCP/IP settings Location: Administration > Basic settings > Locations Organisation: Administration > Basic settings > Organisations Group distribution: Operations > Software management > Installation status > Group distributions |
Approve or remove the item using the appropriate view or using the Tasks –menu of the particular item form. Notice that Miradore can be configured to send approval process notifications automatically to defined users whenever a new item is created. The functionality can be enabled/disabled from Administration > System settings > Users and roles > Approval process notifications. |
8. |
Clean up the old drivers. |
Navigate to Administration > Installation settings > Drivers > By folder in the Miradore management console. Search for organisations in status Waiting for Approval. Filter the view with following parameters: Matching assets = o and Status = Active. |
Move driver folders without a matching asset away from hub installation point, but store them for a while before the final deletion. After you have removed the old drivers, run the driver scanner to make sure that any required drivers were not removed. The driver scanner can be found on the following path at Miradore server: “…\drivers\getdrivers.cmd” |
9. |
Clean up the old data from Miradore. |
Check through the views and seek for old data (non-existing / redundant assets, models, packages, locations etc.). |
Remove non-existing / redundant items. |
See also