ID

Feature

Description

MO-3968

MO-4026

Support for macOS Ventura.

Added possibility to set default responsible person and location for the asset in the configurations values (System settings) if data is missing for autogenerated and imported assets.

The 32-bit WinPE is no longer supported on ADK for Windows 11 22H2. Initial installation startup scripts CreatePE and CreateUFD skip the 32-bit WinPE if it is not found.

Added Activation date field to the Patch installation status details popup (Asset configuration item > Inventory report tab > Security > Security patch status). The field tells when the installation will be activated for the approved patch.

The previous MMS version (5.7) made it possible to download patches from the Internet when the patches aren't available on the installation points. Now it is also possible to scan the patching status of the device without installation points when the patch catalog can be downloaded from the Internet.

MO-4051

MO-4052

Patcher can now run patch-specific scripts on an asset to check if the patching can be completed. Please contact Miradore Support for detailed instructions on how to use this feature.

Added ability to hide patches via API. For example, MS Preview patches can be hidden using the API by updating the patch and setting the hidden attribute to true.

MO-3790

MO-3764

Now the end-user can see the available patches for asset and start patching the asset from the Self-Service portal.

MO-3757

MO-4081

MO-4009

MO-4030

MO-4022

Short summary of the Web Service improvements:

• Added EndpointBackupReportByDevice-item which gives a report of endpoint backups by device.
• Added Superseded-attribute for the Patch item.
• Added LinuxKeyboard-item added as a child to asset for reporting/updating Linux assets' keyboard layout.
• Added ModelText-attribute for the Asset-item.

See Miradore Management Suite's Web Service API specification for more information and example queries.

ID

Feature

Description

SQL Server restart/shutdown or connection error made the inventory import process hang. Enhanced the inventory import script to detect these exceptions and quit processing the import.

Patch approval rules work now also with OS upgrades.

This fix is included in Miradore 5.7.0 Hotfix 1 package that was released in December 2022.

Possibility for stored XSS in the client messaging has been prevented.

This fix is included in Miradore 5.7.0 Hotfix 1 package that was released in December 2022.

MO-4043

MO-3927

Possibility for stored XSS and illegal creation of configuration item attachments has been prevented.

This fix is included in Miradore 5.7.0 Hotfix 1 package that was released in December 2022.

Possibility for stored XSS on distribution status dialog on the asset page has been prevented.

This fix is included in Miradore 5.7.0 Hotfix 1 package that was released in December 2022.

Improved the encryption of the file upload component.

This fix is included in Miradore 5.7.0 Hotfix 1 package that was released in December 2022.

MO-3066

MO-4017

BitLocker recovery keys are now encrypted in the database and a log event is created when the BitLocker recovery key is viewed from the asset's hardware inventory.

This fix is included in Miradore 5.7.0 Hotfix 1 package that was released in December 2022.

MO-4059

MO-4065

ID

Feature

Description

It is now possible to create dynamic asset groups that are populated automatically from a report builder report.

Thanks to Report builder's advanced filtering options, this allows you to specify more detailed membership rules for assets.

See Populating an asset group from a report builder report and How to create reports using Report builder for more details.

We've created an integration script for importing user data from Azure Active Directory to Miradore Management Suite.

See Azure Active Directory integration for the script and instructions.

This versions contains a new version 2.4.0 of Miradore SNMP Scanner.

The new version uses an open source SNMP library and supports the use of TLS 1.2 for communications.

The SNMP Scanner host must have .NET 4.7.2 installed.

It is now possible to add Custom attributes with unlimited drop-down options for assets. Previously, the number of drop-down options was limited to 20.

Device data can be imported into Miradore using XML files as described in the Asset data import process article.

This version improves the feature by adding support for Custom attributes. 

This means that now you can import device data including custom attributes to Miradore. See Format of the XML import file for details.

Miradore MSP Console connector now replicates more detailed information about device's location (full location name) and operating system (full version and release ID) to the MSP Console.

Miradore Client for Windows 3.5.11.

The new client uses newer OpenSSL 1.1.1m and cURL 7.82.0 libraries which improves the security and robustness of client communications.

Miradore Windows Client now stores the Client - Server connection settings before client upgrade.

This ensures that the client can still connect to the MMS server with the previous settings in case the client would get faulty connection settings during the client upgrade.

Miradore can now use packages from HTTP installation points during an initial installation even if the initial installation was started using a network share installation point.

In previous Miradore Management Suite versions, HTTP packages couldn't be used in initial installations performed from a network share.

Initial installation of Debian devices now allows to add extra files to the initial root file system (initrd).

Devices can now be configured to always download patches from installation points OR directly from the Internet in case the patches are not available on the installation points.

The possibility to download patches from the Internet improves the patch deployment process for example to the remote workers' devices that are not connected to the company network so often.

You can find this new configuration option from the "System settings > Main > Patch management > Attempt downloading patches from".

It is now possible to hide certain patches or patches for certain vendors or product families if they are not relevant to your organization. 

See Hiding specific patches from Miradore views, Choosing vendors whose security patches are shown in Miradore, Hiding patches by product family.

Automatic patch approval rules now support also exclude filters for product families and vendors. This makes it easier to build more accurate rules for the automatic processing of patch approvals.

We added a new Tasks menu option "Install approved patches now" to the Asset page, Asset configurations by name view and Security patch status by asset view.

Users in Administrator, Editor or Security Officer roles can use this task to initiate the installation of approved patches on selected device(s) immediately. This option ignores any possible installation schedules and maintenance windows set for the device(s).

The intention is to give Miradore users a way to take immediate action when devices are unoccupied and ready for patching or when there is a patch or patches that must be deployed urgently.

Patch manager is now more robust as it restarts itself automatically at midnight if it stopped running due to an error situation.

Miradore Client now ensures that Miradore's tray process is running when it tries to show patching related reboot or postpone dialogs to device user.

Previously, Miradore Client failed to show the dialogs to the device user if the tray process was not running on the device. As a result, the device user did not know to restart the device and the patch installations started piling up to the "Pending for reboot" status.

Miradore Clients can now be configured to display a system tray notification to device user when the device starts or finishes patch installations. The benefit of using these notifications is to improve the transparency of patching to the device users.

Administrators can enable/disable this feature and customize the user notification messages at "System settings > Main > Patch management > System tray notification settings".

Miradore installer now checks the existence of required certificates on the Patch manager host computer's certificate stores and notifies the user if any of them is missing.

The certificates are used to validate the digital signature of the downloaded patch data. If any of the certificates is missing, patching won't work correctly.

MO-3917 

MO-3946

For security reasons, Miradore now blocks the use of passwords that contain HTML markup like left-angle (<) and right-angle (>) brackets.

Important: Miradore users should be advised to change their password before upgrading to Miradore 5.7.0 if their password contains left-angle and right-angle brackets. Otherwise, they might not be able to login to Miradore after the upgrade.

Administrators can now enforce Two-factor authentication for user accounts for all users on Miradore login.

This new setting is located in "System settings > Main > Password policy settings > Require two-factor authentication".

When enabled, users will be prompted to setup two-factor authentication for their account when they try to login to Miradore next time.

Miradore users must now include their computer name to the Miradore login username (e.g. "Computer\username") IF they use a local Windows account for the login AND if the account with the same name exists also in the MMS server's AD domain.

The reason for this is that Miradore now primarily tries to to validate the login credentials against AD by default if user enters only username without a domain or computer name preceding it.

MO-1447

MO-3150

MO-3447

MO-3642

MO-3653

MO-3689

MO-3706

MO-3838

Here's a short summary of the Web Service improvements made in this Miradore Management Suite version: 

• Added new items CustomInventoryClass and CustomInventoryAttribute with possibility to read and modify the Custom inventory classes and related Custom inventory attributes of the Miradore Management Suite instance. This easies, for example, exporting and importing created Custom Inventory classes from one instance to another.
• Added new attributes LocalIPAddress and PublicIPAddress for the AgentStatus item. 
• A new execute operation RunNow for the item SystemTask for running enabled system tasks through Web Service.
• Added new attributes TotalInstalledMemory and TotalInstalledMemoryInGB for Asset’s extension item InvComputerSystem. These represent the actual sum of the physical memory modules of a device.
• Encoding information is now included in response headers. Lack of the information might have caused some problems earlier with Nordic letters, for example, with PowerShell scripts used with API.
• Patch and PatchVendor items have a new attribute Hidden for hiding unnecessary patches.
• The Address is a new read-only item to replace the old extension item of the Location. This change enables, for example, you to create asset reports that include address details.

NOTE: Address item does not have LocationID as an attribute meaning that queries (Web Service, Dashboard, Report builder) using Address.LocationID won't work.

• It is now possible to create, update and remove LicenceAllocation item.

See Miradore Management Suite's Web Service API specification for more information and example queries.

ID

Feature

Description

If Miradore's SNMP scanner version 2.3 or earlier was installed in the environment, the installation of 3 Step IT connector accidentally removed the SNMP scanner. This bug has been fixed in the new SNMP scanner 2.4 version.

Data import using Microsoft Active Directory connector generated duplicate cost center items in Miradore if the cost centers already existed in Miradore but didn't have external identifiers configured.

Miradore now checks the external identifiers during the data import and fills in the identifiers from the import data if they are missing from the cost center items in Miradore.

The disk space requirements check sometimes failed before operating system upgrade installations. Therefore, Miradore sometimes attempted to perform the OS upgrade although there wasn't enough free disk space left on the device.

The timeout limit for inventory imports was increased from 15 minutes to 30 minutes.

Previously, Miradore sometimes failed to process all the automatic patch approval rules within the 15 minutes and therefore some patches did not get approved as expected.

Patch management client didn't handle http redirects correctly which could cause patch downloading directly from the Internet to fail during initial installation.

Fix to a vulnerability in Self-service portal that allowed a malicious user to gain unauthorized access to view device and user data.

The vulnerability affects only Miradore Management Suite instances where the Self-service portal is enabled. The exposed information contains device name, device model, serial number, MAC address, warranty information and the device responsible person's name, organization, company name, location and possibly detailed location and cost center information.

This fix is included in Miradore 5.6.0 Hotfix 1 package that was released in April 2022.

MO-3922

MO-3924

MO-3925

MO-3929 

MO-3947

This version fixes some potential security vulnerabilities in Miradore Management Suite and its components.

The vulnerabilities are non-critical and they were detected in a third-party security audit conducted recently. We highly recommend to upgrade any earlier versions of Miradore Management Suite as soon as possible although there isn't any known exploits of these vulnerabilities.

MO-3924

MO-3935

ID

Feature

Description

Miradore Client for Linux 1.6.9.

The new client version supports the management of Debian 11 devices.

The new client uses newer OpenSSL 1.1.1l and cURL 7.69.1 libraries than the previous client versions which improves the client security.

Note that Endpoint backup is not supported for Debian 11 devices.

Miradore Client for macOS 1.6.9.

The new client version supports the management of macOS 12 Monterey devices.

The new client uses newer OpenSSL 1.1.1l and cURL 7.69.1 libraries than the previous client versions which improves the client security.

Miradore Client for Windows 3.5.10.

The new client version officially supports the management of Windows 11 and Windows Server 2022 devices.

The new client uses newer OpenSSL 1.1.1l and cURL 7.79.1 libraries than the previous client versions which improves the client security.

Additionally, the OpenSSL library was also updated for the MDPatcher component.

On Windows devices, end-users can now access the self-service enrollment URL with Edge, Firefox, and Chrome browsers in addition to Internet Explorer.

Get familiar with Device self-service enrollment.

There is now a new setting in "System settings > Main > Patch management > Patch download settings" that allows you to specify how long patches will be in the scope of automatic patch approval rules counting from their release date.

With the help of this setting, you can create rules that apply to the recent patches, but not to the old ones.

You can now use Miradore's patch management to upgrade Windows 10 devices to Windows 11. 

See Managing Windows version updates for more information.

Miradore Management Suite 5.6.0 server now targets .NET Framework version 4.7.2. Miradore installer installs the framework during a fresh or upgrade installation if it is missing. This change enables the use of TLS 1.2 protocol for securing the communications between 1) Miradore server and a dedicated database server 2) Miradore server and Miradore MSP Console. 

ID

Feature

Description

The data queries performed by the Miradore Online connector were slow, and therefore, the data imports occasionally timed out and failed.

New Miradore Online connector version 1.2.0 imports data from Miradore MDM to Miradore Management Suite in multiple smaller queries which improves the reliability of the data imports.

This new connector version will no more import data about possible Windows Phone devices, because the support for Windows Phones is soon about to end on Miradore's MDM product.

There was problems in identifying different releases and language versions of Windows 10 operating system in some situations. Therefore, Miradore sometimes reported the device's installed operating system incorrectly.

Operating system detection and autogeneration didn't work properly with Russian versions of Windows 10 operating system.

If two-factor authentication was enabled for logins, the "Culture" setting under "My account settings" was reset back to the field's default value everytime when the user logged in.

ID

Feature

Description

MO-3198

MO-3704

Improved the performance of the inventory data imports.

The updated inventory data import procedure now skips the processing of earlier inventory files if there is a newer inventory file available. An exception to this is the processing of cumulative inventory data files, such as software usage information, client logs and patch inventories, which are always imported to Miradore without skipping any files.

In addition, we fixed some performance issues that were slowing down the hardware inventory imports.

We have built a customized Miradore Client for Linux which enables the management of some ARM-based Debian 9 and 10 devices.

This customized client is not available in Miradore Management Suite installer nor Miradore support site. Please contact Miradore support if you are interested in managing ARM-based Debian 9 or 10 devices.

Miradore 5.5.0 brings premilinary support for managing devices running Windows Server 2022.

Preliminary support means that we are still in the progress of perfecting some features and details, but you can already test the management of the platform and report your findings to Miradore. Official support for Windows Server 2022 will be released after the official launch of Windows Server 2022.

MO-3203

MO-3736

Windows 10 feature updates can now be performed over HTTP(S) installation points for remote users.

See Managing Windows 10 version updates for details. 

MO-3675

MO-3675

Patch type and software product version can now be used in automatic patch approval rules to define the target patches for the rule.

Now you can, for example, create a rule which applies only to the security patches or define a rule for processing the patches of some certain product version.

MO-3702

MO-3741

There is now a new section on the Patch page "Supported products" which lists the software products and product versions supported by the patch. The Product version is now also available as a filter in the Security patches and Security patch status by patch views.

You can now manage operating system updates for Windows 10 Business devices with Miradore. See Managing Windows 10 version updates for more. Previous versions of Miradore Management Suite are not fully compatible with Windows 10 Business.

Remote assistance and control features which are present in earlier versions of Miradore Management Suite, are no more present on Miradore Management Suite 5.5.0. All views, actions and data regarding remote control have been removed in this version.

Important

• If you want to store the data about past remote control sessions, you should export the data from the "Operations > Remote control > Sessions" view before upgrading your environment.
• The Miradore team has created a package, which can be used to remove remote control clients from your managed devices. You can find the package from Miradore's support site.

Miradore Management Suite 5.5.0 officially supports SQL Server 2019 database platform. 

Notice that earlier versions of Miradore Management Suite are not fully compatible with SQL Server 2019. It is known that, for example, the database backups are not working properly in such settings.

MO-2325

MO-2327

MO-3435

MO-3646

MO-3692

MO-3719

MO-3734

MO-3745

Here's a short summary of Miradore Management Suite's web service improvements and what they mean to you:

• It is now possible to create, update and delete Organisation, Subnet, Model and HWManufacturer items through Miradore Management Suite's web service API.
• There is a new InstallationPoint item which enables to read installation point information through the API. The Installation point item also available in the Report builder, Dashboard widget wizard, and under the Distribution item. The latter means that you can create new distributions over the web service with a selected installation point.
• New asset extension InvPatchingStatus enables to read devices' overall patching status information over the web service. This data is also available in the Report builder and Dashboard widget wizard.
• You can now check the download method of a patch over the web service by reading the new DownloadMethod attribute of the Patch item. 

See Miradore Management Suite's Web Service API spesification for more information and example queries.

ID

Feature

Description

Email delivery was broken on the "Custom tools > Run software catalog scanner" task, located on the Asset configuration item. This task can be used to send software inventory details to the Miradore support team for analysis.

Miradore login failed with the default administrator account if the account password was set to contain a quotation mark when setting up the environment with Miradore installer.

ID

Feature

Description

MO-3487

Asset management

Close button was added back to the Asset page. The close button is disabled while the asset page is in edit mode. Notice that the Close button doesn't work on Firefox browser after clicking Edit - Save or Edit - Cancel.

MO-3490 & MO-3647

Asset management

Miradore Management Suite 5.4.0 and MacOS Client 1.6.7 fully support the management of ARM-based systems and Macs running the macOS Big Sur. Notice that older versions of Miradore Management Suite do not support the management of macOS Big Sur devices.

The Client version 1.6.7 is compatible with macOS 10.12, 10.13, 10.14, 10.15 and 11.

If you wish to manage devices running macOS version 10.9 - 10.11, you should use macOS Client 1.6.6.

Also the functionality of the "Collect client logs" action has been improved to utilize the systems logs in this new client version.

See Client upgrade instructions from Upgrading Miradore client for OS X / macOS.

 MO-3505

Asset management

Active Directory connector version 2.8.5 contains a bug fix for SSL certificate handling. This connector version was released in september on our support site.

 MO-3607

Asset management

Linux Client 1.6.6 partially supports the management of devices running Ubuntu 20.04 LTS. Initial installation and endpoint backup features are not supported.

 MO-3637

Asset management

Miradore Client for Windows 3.5.9 adds support for patching the device during initial installation. Previous Client versions didn't support this feature.

MO-3498

Documentation

Upgrade of the tools used for authoring and publishing the Product Guide.This improvement will improve the product guides browser compatibility and enable further development of the Product Guide in the future.

Documentation

There is now an article how to use Miradore with a reverse proxy.

A reverse proxy can be used to open a Miradore Management Suite instance to the internet for clients also when the are not in the internal network.

-

Integrations

There is now a new integration available for exporting data from Miradore to ServiceNow.

Read more from: Integration to ServiceNow.

ID

Feature

Description

MO-3485

 Asset management

 Client installation and running the hardware scan failed on some Microsoft Windows Server platforms. This fix was also included in the Miradore 5.3.0 Hotfix package.

 MO-3407

Patch management 

Managing Windows 10 operating system upgrades with Miradrore requires to have network share installation points. The OS upgrades cannot be deployed using HTTP installation points.

In the previous version, Miradore incorrectly stopped applying software patches to devices where OS upgrade had failed, because any network share installation points were not available.

ID

Description

MO-3391

Miradore Client for Windows 3.5.8 contains security improvements and changes to client-server communication. It is now possible to choose which certificate store the Client uses for HTTPS connections.

Upgrade all Miradore Windows Clients to this new version. This is easiest using the automatic client upgrade. Go to "System settings > Clients > Enrollment and upgrade" in Miradore, and make sure that "Client version = 3.5.8" and "Automatic upgrade enabled = Yes".

MO-3395

Miradore Client for macOS 1.6.6 contains security improvements and changes to client-server communication.

Upgrade all macOS Clients to this new version. This is easiest using the automatic client upgrade. Go to "System settings > Clients > Enrollment and upgrade" in Miradore, and make sure that "Client version = 1.6.6" and "Automatic upgrade enabled = Yes".

MO-3438

Miradore Client for Linux 1.6.6 contains security improvements and changes to client-server communication.

Upgrade all Linux Clients to this new version. This is easiest using the automatic client upgrade. Go to "System settings > Clients > Enrollment and upgrade" in Miradore, and make sure that "Client version = 1.6.6" and "Automatic upgrade enabled = Yes".

MO-3365

Endpoint Backup Server 1.4.2 adds support for using TLS 1.2 on Miradore server connection..

Earlier Endpoint Backup Server versions could not connect to Miradore instances requiring TLS 1.2.

You can upgrade your Endpoint Backup Servers using the Endpoint Backup Server 1.4.2 installer.

MO-3322

New version 2.8.4 of Microsoft Active Directory Connector adds the possibility to connect the AD Connector to Active Directory using LDAPS connection.

You can find settings for configuring the LDAPS connection from the AD Connector page in Miradore system settings.

Bug fix: Earlier Microsoft Active Directory connector versions failed to import AD objects to Miradore successfully if there was special characters, line breaks or html tags included in the AD objects.

Upgrade AD Connector using the connector installer which is available at: <Miradore server installation directory>\Connectors\Active Directory.

MO-3327

New version 4.1.1 of 3 Step IT Connector fixes a bug that caused problems if user tried to set up multiple connector configurations using the connector configurator utility.

Upgrade 3 Step IT Connector using the connector installer which is available at: <Miradore server installation directory>\Connectors\3 Step IT.

MO-3342

New version 2.0 of Offline Domain Join Connector contains significant improvements to the connection between the connector and Miradore server.

Offline Domain Join Connector 2.0 can now be configured to use Secure LDAP (LDAPS) connection to Active Directory. You can configure LDAPS using the "Use LDAPS" and "Domain controller" fields which are located on the Connector item page in Miradore.

Offline Domain Join Connector 2.0 now uses WebSockets for connecting to Miradore server, which improves the reliability of the connection. Miradore 5.3.0 server still supports also the older connector versions using different connection method.

Troubleshooting possible connector issues is now easier, because Miradore writes more detailed logs about the connector to the \Logs\OfflineDomainJoin directory. Miradore also shows more detailed error descriptions in the user interface of Miradore if problems occur when performing the offline domain join for a computer.

Bug fix: Earlier connector versions failed to perform the offline domain join if the computer object already existed in Active Directory and target OU was not configured on the connector page. This caused problems when reinstalling computers.

Upgrade ODJ Connector using the installer available at: <Miradore server installation directory>\Connectors\ODJ.

MO-3360

New version 1.6.0 of F-Secure Policy Manager Connector supports F-Secure Policy Manager up to version 14.41.

Older connector versions are not compatible with the latest F-Secure Policy Manager versions.

Upgrade the connector using the connector installer which is available at: <Miradore server installation directory>\Connectors\F-Secure Policy Manager

MO-3384

Miradore Connector for Microsoft SCCM 1.3.6 contains security improvements and changes to the communication with Miradore server. Older connector versions do not work with Miradore 5.3.0.

Upgrade Microsoft SCCM Connector to the latest version using the connector installer which is available at: <Miradore server installation directory>\Connectors\SCCM .

MO-3436

New version 1.2.1 of Miradore Connector for F-Secure Protection Service for Business fixes bugs regarding connector status reporting and in the method how connector saves its configuration settings to registry.

Upgrade F-Secure PSB Connector to the latest version using the connector installer which is available at: <Miradore server installation directory>\Connectors\F-Secure PSB.

ID

Feature

Description

MO-2844

Asset management

Miradore now shows Windows-provided inventory information about device's security products on the Asset configuration item's Security inventory tab.

Notice that the information is not available for devices running server version of Windows. Windows desktop versions are supported starting from Windows 7.

MO-2981

Asset management

Administrators can now configure which certificate store Miradore Clients should use as a reference for HTTPS connections with Miradore server. The Clients can be configured to use a local rootCerts.pem container file, operating system's certificate store, or both of the before mentioned stores to obtain a trusted certificate for secure connections.

For more information, read Certificate store for Miradore Client connections.

MO-3380

Asset management

WebSocket connections between Miradore Clients and Miradore server now support IPv6.

MO-3369

Documentation

Miradore product guide now advices administrators to avoid giving excessive user permissions to the user accounts that are used to read/write installation point contents. See Installation point sharing and permissions for more information.

We recommend to check the permissions of the user accounts that are used in your environment. You can find the user accounts from the following places in Miradore:

• Default account: System settings > Main > Installations management > Installation point authentication

• Installation point specific accounts: Administration > Feature settings > Installation settings > Installation points > Installation point form > Read authentication

MO-3326

Patch management

Reboot behaviour was improved for those cases when reboot is initiated without showing a reboot dialog. The improved reboot heuristic now skips unnecessary patch inventory scan before the reboot which saves time.

MO-3394

Reporting

Updated widget gallery contains bug fixes for two existing widgets and also adds twelve new widgets that you can use to build dashboards:

New dashboard widgets in Miradore 5.3.0:

• Patches not installed

• # Assets with full patch retry count

• Failed patch installations last 7 days

• Windows 10 versions

• Computer OS

• Windows Client versions

• Linux Client versions

• Mac Client versions

• BitLocker status on C: drive

• Software with most licenses missing

• Software licenses missing

• Assets with slowest last boot times (seconds)

You can find a description for each widget from the widget gallery.

MO-1058

MO-2844

MO-3111

MO-3122

MO-3242

MO-3252

MO-3363

Reporting

The following new items and attributes were added to Report builder and Dashboard widget builder:

• InitialInstallationEnabled attribute under the OS item. This attribute tells whether the operating system has initial installation enabled or not. We recommend to include also OSCategory attribute in reports, because there can be both Windows and Linux devices which have initial installation enabled.

• MediaFolder attribute under the Package item. This attribute contains the file path to the package's media folder.

• New Asset extensions EndpointBackupJobConfiguration and EndpointBackupReport which can be used, for example, to create reports and dashboard widgets for showing the endpoint backup jobs performed on a device or to find devices which are not backed up.

• New Asset extension InvLastLoggedInUser contains the username of the last user who has logged into the device according to the device inventory data.

• New Asset extension InvSecurityProduct contains Windows-provided information about device's security products such as firewall and antivirus solutions. Notice that this inventory data is not available for server versions of Microsoft Windows. Windows desktop versions are supported starting from Windows 7.

• AssetSpecificPackage item, containing information about asset-specific packages attached to the initial installation.

• SystemTask item, containing information about Miradore system tasks and their status.

Check Widget example - Monitoring Miradore systems tasks to learn how to monitor the execution of Miradore system tasks.

MO-3362

System internal

Logging was improved for inventory data imports. Now the logs contain information from a longer period of time.

MO-3387

System internal

Removed "Run inventory" feature. This means that clientless inventory is no longer supported.

MO-3331

System security

Miradore now shows a warning and a blinking red icon on the bottom-right corner of the user interface if your Miradore instance is configured to ignore SSL errors or if Miradore Clients in your environment are allowed to connect to Miradore server using regular HTTP instead of HTTPS/SSL.

You can get rid of the warnings by disabling the ignore SSL errors and by enabling the use of HTTPS for client connections.

MO-1920

System usability

Configuration of Windows Client enrollment rules is now easier as the deployer account selection was simplified.

MO-3373

MO-3374

System usability

Improved the usability of the Asset form.

• User may now easily see the required information on the form, since the mandatory fields are better highlighted.
• The Close button was removed to clarify the actions on the Asset form. The form can be closed from the browser's close button.

MO-3330

System usability

Renamed the Save and schedule -button of the Report builder in order to make clearer its functionality. With "Save and schedule actions" user may create automation task, for example, to schedule the report for email delivery, automate patch deployment or change status of the assets in the report. Read more about what possibilities Automation tasks offers.

MO-1058

MO-2844

MO-3111

MO-3122

MO-3242

MO-3252

MO-3363

Web service API

Multiple new items and attributes were added to Miradore Management Suite API.

See the API specification for more details and example queries.

ID

Feature

Description

MO-3367

Asset management

Inventory data import got stuck in certain situations due to lack of file permissions. Now the inventory import skips files that it cannot process.

MO-3381

Asset management

Import of Add/remove programs inventory data from managed devices to Miradore server failed in certain scenarios. Error handling was improved to address this type of issues.

MO-3417

Asset management

If the user ended editing the asset form by changing the asset status, the other modifications on the form were discarded. Now the modifications are saved when user clicks the button for changing the status.

MO-3432 & MO-3436

Asset management

New version 1.2.1 of F-Secure Protection Service for Business Connector fixes two bugs.

Due to the bugs, connector status was incorrectly reported in Miradore if user had specified multiple connector configurations using the connector configurator. Connector settings were also saved under a wrong registry key, because the connector configurator ran in 32-bit mode also on 64-bit computers.

MO-3350

Installations management

Miradore started operating system upgrades in managed devices also outside maintenance windows which should not happen.

MO-3351

Installations management

Windows 10 1903 or 1909 didn't become selectable for initial installation in Miradore if the provided installation media contained only one edition of Windows.

This rare error situation was fixed by improving the operating system detection in the GetOSInfo.cmd script.

MO-3356

Installations management

Static TCP/IP settings configured to the asset form didn't get applied to some devices during initial installation. This bug happened only with certain device models.

MO-3418

Installations management

BitLocker activation failed sometimes during initial installation because Miradore didn't check the to-be-installed operating system correctly and that's why the BitLocker activation package was not included in the initial installation sequence.

MO-3445

Installations management

The status of file replication was sometimes incorrectly reported for installation points when file exclusion rules had been specified for the replication. Due to this bug, installation points sometimes seemed to be out-of-sync even when the replication had succeeded.

MO-3359

MSP Console

On Miradore 5.2.0 HF2 environments, the system task "Process MSP Console jobs" failed due to insufficient permissions while trying to access Miradore server's registry.

MO-3366

System internal

Configuration changes were not recorded to the Offline Domain Join connector's Event log in Miradore.

MO-3426

System internal

Connector page didn't show any Created date for installed connectors.

ID

Description

MO-3071

Miradore Client for Windows 3.5.6 fixes a scheduling bug regarding maintenance windows for patching.

MO-3178

Miradore Client for Linux 1.6.5 adds support for managing Debian 10 devices.

See Client upgrade instructions for Linux here.

MO-3195

Miradore Client for macOS 1.6.5 adds support for managing macOS Catalina (version 10.15) devices.

The new client version is notarized by Apple.

Support for some older macOs versions is discontinued. You can continue managing the previous macOS versions with the previous Miradore Clients.

This client supports versions starting from OS X Mavericks (10.9).

MO-3222

The new version 1.1.8 of Miradore Online Connector is compatible with TLS 1.2 and TLS 1.3. The connector host is required to have .NET Framework version 4.7.2 installed. Also error logging was improved for the connector.

We recommend to upgrade if you're using the connector.

MO-3272

F-Secure PSB Connector 1.2.0.

New connector version contains a fix to a bug which prevented the connector from releasing F-Secure PSB licenses in situations where many devices were retired from use in Miradore Management Suite at the same time. From now on, the connector will release the licenses in smaller batches if there are a lot of retired devices in Miradore.

This version also adds simple retry logic for the connector authentication with PSB management API and improves connector error logging.

ID

Feature

Description

MO-1988

Asset management

In the previous versions of Miradore, devices were sometimes incorrectly identified as the same asset when they were installed using an external Ethernet adapter. This happened because MAC address is one of the device identifiers that Miradore uses, and the external adapter's MAC address was automatically recorded for the assets during the installation.

We have now added a new field, for blacklisting the MAC addresses of the shared network adapters, to the "System settings > Main > Asset management > Automatically generated items > MAC address blacklist". Enter here the MAC addresses that should not be automatically recorded to asset configuration items.

MO-3187 & MO-3256

Asset management

Improvements to the data export features of 3 Step IT and Nordea Finance Connectors:

- It is now possible to export custom attributes from Miradore to Nordea and 3 Step IT.

- Administrators can now configure on the connector page if they want the connector to export empty attribute values from Miradore to the target system. This option is unchecked by default, which means that the connector clears the value of an attribute in the target system if its value is empty in Miradore.

MO-3078

Documentation

Updated the list of URLs that Miradore's Patch manager component needs to be able to access to in order to function normally. See the Patch manager article for details.

Updated the list of products and platforms supported by the patch management. See the attached Application support for Miradore Patch Management document.

MO-3134

Documentation

Added a new Help article which describes how to create a desktop shortcut to Self-service portal.

MO-3220

Documentation

Updated the documentation regarding the creation of Windows PE startup images.

Earlier the Windows Preinstallation Environment was included in Windows Assessment and Deployment Kit, but nowadays you need to download the Windows PE add-on from the Microsoft site and install it separately before creating the images.

MO-3290

Documentation

Added a new Help article about computer health monitoring / pre-emptive maintenance.

MO-2936

Installations management

Earlier it was possible to give device users only up to 99 minutes of time to defer the start of software installations that are part of a group distribution.

The limitation for the countdown timer was increased to 9999 minutes for the postpone dialog on the Group distribution item page.

For more information, see Postponing group installations.

MO-3085

Installations management

The install/postpone dialog of a group distribution now mentions if a device reboot is required to finalize the installation.

MO-3110

Patch management

The maximum allowed value of the patch management reboot timer was increased from 480 minutes (8 hours) to 1440 minutes (24 hours).

The reboot timer defines the time how long Miradore Client waits, showing the "Restart required" dialog to the device user before it automatically reboots the device. During this time, user can choose to restart immediately or postpone the reboot.

MO-3239

Patch management

The size of the patcher.log.old was increased from 8 megabytes to 32 megabytes so that the log can withhold more information about the past patch scans. Also some unnecessary log entries were filtered out from the log.

MO-3103

Reporting

Automation engine now reads also the "Ignore SSL errors" setting from the default client connection settings defined in the system settings of Miradore Management Suite. This change simplifies the configuration of the automation engine for environments using a self-signed SSL certificate.

MO-3237

System internal

New Miradore Management Suite instances installed with the Miradore 5.2.0 installer now use the WebSocket protocol as the default protocol to send Miradore Client wake-up signals.

MO-3274

System internal

Improved support for SMTP encryption methods which also expands the support for third-party SMTP servers.

Miradore sends automated email messages, such as notifications, enrollment messages and scheduled reports, over SMTP protocol.

In this version, we have renewed Miradore's SMTP/email engine which now supports encryption and the use of third-party SMTP servers, such as Gmail.

You can configure the SMTP settings at System settings > Main > SMTP settings.

There is also a button for testing the email configurations on the header row of that settings table.

MO-3064

System performance

The Asset page's loading time was improved by moving the data regarding endpoint backup jobs from the "Main" to the "Inventory report > Endpoint backup jobs" tab.

The backup data will no more be loaded when opening the main tab of the asset page.

ID

Feature

Description

MO-1981

Asset management

Macs with iBridge feature were identified incorrectly in certain scenarios because iBridge creates a network interface with the same MAC address in all devices.

MO-3225

Asset management

There was a corrupted installer of Nordea Finance Connector included in the Miradore Management Suite 5.1.0 installer package. The installer failed to start the installation when attempted.

MO-2900 & MO-3288

Asset management

Previous version of Miradore Management Suite was not always able to identify Windows 10 versions correctly. For example, Windows 10 version 1909 was incorrectly identified as 1903.

MO-3247

Command line tool

Command line tool gave an error when it was used to read system settings.

MO-3208

Installations management

Manual installation point selection didn't work when distributing an installation package to a Linux or Mac device. If user attempted to modify the default installation point for the package distribution, Miradore complained that it wasn't able to queue the package for installation.

MO-3226

Installations management

Miradore installer misconfigured the installation point to use HTTP when it was used to set up a new instance of Miradore Management Suite with an installation point on the same server and "Use HTTPS" and "Require HTTPS" options were both enabled.

MO-3275

Installations management

Boot order was incorrectly configured for some device models during initial installation. As a result of this issue, the misconfigured devices tried to boot primarily from a network boot (PXE) server after the initial installation.

MO-3284

Installations management

BitLocker activation failed on some Windows computers when it was attempted using the "Miradore Enable BitLocker~1" package. The package returned "Invalid XML content" as the error output.

MO-3071

Patch management

A maintenance window for patch installations got skipped if a patch scan was still running when the maintenance window started.

This problem is fixed in Miradore Client for Windows 3.5.6

The new default behavior is that Miradore will stop a patch scan if a maintenance window for patch installations is starting, and continue the patch scanning again after the maintenance window has ended.

MO-3199

Patch management

Earlier versions of Miradore displayed Windows 10 1903 upgrade patches with an incorrect name.

This fix is also included in Miradore Management Suite 5.1.0 hotfix package.

MO-3200

Patch management

Upgrading managed device's operating systems from Windows 10 version 1809 to Windows 10 1903 with Miradore's Patch management failed.

This fix is also included in Miradore Management Suite 5.1.0 hotfix package.

MO-3204

Patch management

The “Show matching patches” task didn't work properly on the “Security patch automatic approval rule” page if the "Product" filter was empty.

This fix is also included in Miradore Management Suite 5.1.0 hotfix package.

MO-3207

Patch management

Fixed a bug which sometimes caused a patch to appear multiple times in the user interface of Miradore.

Contact to Miradore support if you ever see duplicate patches in your environment.

This fix is also included in Miradore Management Suite 5.1.0 hotfix package.

MO-3217

Patch management

A wrong date was sometimes shown in the "Next scheduled date" field for the patch installation schedules. The problem was, however, only in the user interface and the patches actually were installed on correct dates according to the intended schedule.

MO-3235

Patch management

Miradore's patch management client didn't work with HTTPS installation points and valid SSL certificates which complicated the patch management for the devices on field.

After this fix, the patch management client will use the same PEM file with Miradore Client.

MO-3236

Patch management

The status of Windows 10 feature upgrades was sometimes reported incorrectly as "Installed pending for reboot" although the feature upgrade had actually failed. Rebooting devices again didn't change the status either which prevented from retrying the upgrade.

MO-3244

Patch management

Miradore stores patch installers at the media master installation point for some time (90 days by default) even if the patch wouldn't be used at all. After the specified time, the patch data will be removed to conserve disk space.

There was a bug, however, which caused Miradore to delete and re-download the patch installation media again and again if the patch wasn't installed in between the daily patch download and removal tasks.

MO-3262

Patch management

Automatic downloading of patch payloads failed if any operating system media hadn't been imported to the Miradore Management Suite instance earlier.

MO-3287

Patch management

Upgrading older Windows versions to Windows 10 1903 with Miradore's patch management failed if the "Max bandwidth for file copying" setting was enabled for the device locations on Miradore.

MO-3241

Reporting

Custom quality index indicator's value didn't get updated for quality index reports if the new indicator value was zero.

MO-3214

System internal

Asset inventory data imports failed in environments where the use of TLS 1.2 was enforced if Miradore server had too old database drivers installed.

The installer of Miradore Management Suite 5.2.0 has been improved so that it checks the database driver version and installs the required utilities if necessary.

MO-3206

System performance

Miradore server suffered extremely high CPU load if Websocket was used as the primary method to wake up Miradore clients and there were incorrectly installed (cloned) Miradore Clients in the environment. As a symptom of this issue, the CPU usage on IIS Application pool got exceptionally high and caused Miradore server to slow down or stop responding completely.

This fix is also included in Miradore Management Suite 5.1.0 hotfix package.

MO-3248

System usability

Data filtering in views didn't work correctly by multiple locations or organisations.

Now you can create a filter which shows you the view items in several locations or organisations at once. For example, assets in Paris or London.

ID

Description

MO-64

MO-3050

MO-3091

MO-2898

MO-3180

Miradore Client for Windows 3.5.5 includes the following improvements:

• Adds support for Windows Server 2019 management.

• Supports the use of HTTP installation points for package deployments.

• Improves support for HTTPS certificates issued by internal certificate authority. For more information, please contact to Miradore support.

Fixed bugs:

• Self service portal connection failed with Windows client if Miradore instance was using a non-standard HTTP or HTTPS port.

• The client didn't work properly on computers with non-ASCII characters in their device name. This resulted in the following problems:

  • The client reported a garbled device name to Miradore server.

  • The client failed to upload file scan inventory results to Miradore server.

  • The self service portal didn't open for the device user.

  • The dialogs related to remote assistance displayed a garbled device name to the device user.

Notice: There might still be issues with custom inventories and forwarding wake-up messages to computers whose device name contains non-ASCII characters.

MO-3129

Remote Control Administrator Client 1.0.5 renews the client's license for the next three years. The new license key expires 2022/02/11.

Upgrade the Remote Control Administrator Client to the latest version on all your remote control administrator computers using the latest Remote Control Administrator Client installer. You can find the installer from our support site or from your installation points at: _System\Miradore\RemoteControl\Install\RemoteControlAdminClient.msi.

MO-3042

Miradore Client for macOS 1.6.4

Fixed bugs:

• If client's server polling interval value was less than 60 seconds, the startup of a client failed. Now invalid polling interval values are reset to the default value (= 3600 s).

MO-3019

MO-3042

Miradore Client for Linux 1.6.4

Improvements:

• Miradore Client for Linux adds support for specific Debian 8 ARM devices. Please contact to Miradore support for more details.

Fixed bugs:

• If client's server polling interval value was less than 60 seconds, the startup of a client failed. Now invalid polling interval values are reset to the default value (= 3600 s).

MO-3015

MO-3055

MO-3063

MO-3164

Miradore connector for 3 Step IT 4.1.0 includes the following changes:

• You can now connect one connector to multiple Miradore Management Suite instances. See instructions from 3 Step IT connector page.

• The latest connector version requires .NET Framework 4.6.2 and supports TLS 1.2.

Fixed bugs:

• Terminated assets and assets with public status 50 were not previously matched with Miradore assets, but now they are.

• Connector version 4.0.0 failed to import data when the data was in unexpected form.

• The connector failed to update financial transactions if there was duplicate data in an asset's financial inventory information.

MO-3146

Several Miradore connectors were recompiled with .NET Framework 4.7.2 to ensure compatibility with TLS 1.2 and 1.3 protocols.

New versions of the updated connectors are:

• Miradore connector for Blancco Management Console 1.3.3

• Miradore connector for F-Secure Protection Service for Business 1.1.1

• Miradore's Offline Domain Join connector 1.0.1

• Miradore connector for Microsoft SCCM 1.3.5

• Miradore connector for Microsoft WSUS 2.3.2

Make sure to install .NET Framework 4.7.2 or newer to the computer(s) hosting any of these connectors.

MO-3119

This Miradore Management Suite version introduces a new connector for exporting and importing asset data between Miradore Management Suite and Nordea Finance Asset Advantage.

For more details, refer to Miradore connector for Nordea Finance Asset Advantage data sheet.

MO-3090

New version 1.4.1 of the Endpoint Backup Server fixes a bug which occasionally caused backups to fail due to an authentication issue on the Endpoint Backup Server.

It is recommended to upgrade all Endpoint Backup Servers to this latest version.

ID

Feature

Description

• Asset form (BitLocker enabled -link)
• Inventory reports > Logical disks
• Report builder
• Web service API of Miradore Management Suite

MO-64

Installation management

You can now deploy packages to Windows computers outside the company network because the newest Miradore Client for Windows supports the use of HTTP installation points for package deployments. You can choose the installation point type (network share / HTTP) at the Package item page using the "Map installation point" field.

New package action "Download file from installation point" adds a possibility to download a file from an installation point to a Windows computer. This feature supports both HTTP and network share installation points and it requires the Miradore Client for Windows version 3.5.5 or newer. For more details, please refer to Package actions for Windows.

The package action "HTTP download" for Windows was reprogrammed to improve the reliability of the action because users had reported issues in the previous implementation.

Miradore Management Suite now supports patch management on assets running Microsoft Windows Server 2019. See Applications and platforms supported for Miradore patch management for more details.

You can add Windows 2019 Server operating system to the scope of Miradore patch management in "Administration > System settings > Main > Patch management > Operating systems to support". After that, Miradore patch manager also retrieves metadata about Windows 2019 Server patches to your Miradore.

MO-3074

System internal

Added support for installing Miradore Management Suite on a server running Microsoft Windows Server 2019.

Added support for reading the PatchInstallationStatus item's "RetryCount" attribute through the web service API.

ID

Feature

Description

MO-3089

Asset management

Inventory information about local administrators was incorrectly reported as empty on the asset configuration item if the computer had exactly one member in the local administrators group.

MO-3073

Installations management

Package distribution failed on Windows 10 1809 computers if the package tried to run an executable from a network drive using the "start" command. This happens because in Windows 10 1809 Microsoft changed the way how the start command works.

MO-3112

Installations management

Configuration of a static IP address in the initial installation console didn't work when computer had only one network adapter active in WinPE.

MO-3165

Installations management

Disabling installation point replication didn't work on Linux installation points.

There were some columns which disappeared if a user modified a report opened through a dashboard widget.

MO-3108

Reporting

Miradore's report builder didn't handle child item correctly if there were more than ten thousand child items in the report. Because of this, some asset attributes were shown as empty when the report was exported into an Excel file.

MO-3097

System internal

Miradore client connections didn't always work reliably over WebSocket protocol in environments with a large number of devices.

MO-3107

System performance

Processing of the software usage import data caused high CPU usage on the SQL server which slowed down the user interface of Miradore Management Suite.

ID

Description

MO-2202

MO-2192

MO-2666

MO-2751

MO-2799

MO-2824

MO-2833

Miradore client for Windows 3.5.3 contains the following improvements:

• Support for WebSocket communication protocol in sending Miradore client wake-ups

• The binaries of Miradore Windows client were recompiled against a newer version of Client URL Request Library (v. 7.59.0). This client version also uses OpenSSL library version 1.1.0h.

Fixed bugs:

• Earlier device end-users had to start remote assistance sessions manually by clicking the Start button in Miradore client's tray application. This client version opens the remote assistance session automatically when administrator launches the session from Miradore Management Suite.

• The client failed to run scheduled tasks, such as patch management tasks, with certain scheduling settings.

• The client failed to process inventory data from computers whose name included non-ASCII characters.

• The client didn't have access to logged in user's environment variables when executing package installations in the context of the logged in user.

• There were layout problems in some popup windows shown by the client.

See Upgrading Windows clients for more instructions on how to upgrade the client for Windows devices.

MO-2706

MO-2980

MO-2994

MO-2996

MO-2997

Miradore client for Linux 1.6.3 contains the following improvements:

• Support for WebSocket communication protocol in sending Miradore client wake-ups (not supported for Red Hat Enterprise Linux 6)

• Support for managing Linux Ubuntu 18.04 LTS Bionic Beaver (no support for initial installation)

• In order to improve the client-server communication over SSL, OpenSSL and libcurl libraries and the rootcerts.pem certificate file were included in the Miradore Linux client instead of using the libraries and files included in different Linux distributions.

• This new client clears scheduler job status during the client uninstallation and upgrade. This speeds ups the running of scheduler jobs such as inventory scans after client upgrade or reinstallation.

Fixed bugs:

• Miradore client didn't start on some distributions, for example on openSUSE 42.3.

See Upgrading Linux clients for more instructions on how to upgrade Miradore clients for Linux devices.

MO-2821

MO-2828

MO-2878

MO-2979

Miradore client for macOS 1.6.3 contains the following improvements:

• Support for WebSocket communication protocol in sending Miradore client wake-ups

• Support for managing devices with macOS 10.14 Mojave

• In order to improve the client-server communication over SSL, OpenSSL and libcurl libraries and the rootcerts.pem certificate file were included in the Miradore's macOS client instead of using the libraries and files included in different macOS versions.

• Miradore Client logging didn't work as expected on all MacBook Pro computers. The problem was resolved by updating the Miradore Client's logging configuration.

More information about supported operating systems can be found from the article Miradore Management Suite features by platforms.

MO-2964

Miradore client deployer was using an outdated HTTP/SSL library which caused the following error when connecting to Miradore Management Suite server with certain configurations: "HTTPHandler: 35. SSL connect error: Unknown SSL protocol error".

The problem is fixed in Miradore client deployer version 1.4.4. It is recommended to upgrade older Miradore client deployers to this version.

MO-2754

MO-2556

Miradore connector for 3 Step IT 4.0.0 contains the following improvements:

• The connector now requires .NET 4.5 Framework and it uses REST API to connect to 3 Step IT asset management.

• The connector now imports "ReceivedDate" attribute from 3 Step IT to Miradore and the attribute is shown at the Financial inventory tab of Asset configuration items. The received date attribute indicates the day when 3 Step IT received a returned device.

• It is now possible to export information from Miradore Management Suite to the "Extra date 1 - 5" attributes in 3 Step IT with the connector. Extra date 1 - 5 attributes are now selectable in connector's export settings.

• The support for exporting "Ending option info" attribute from Miradore to 3 Step IT was removed.

• The new connector version doesn't support the showing of the custom names of 3 Step IT attributes in the connector's export settings in Miradore.

Upgrade instructions:

Use the latest connector installer to upgrade your existing connectors. After the upgrade installation, let the connector run once and then go to the connector settings in Miradore Management Suite and configure the "Client ID" and "Client secret" fields. Make sure to request these from 3 Step IT before performing the connector upgrade. Notice that the new connector version requires .NET 4.5 Framework.

MO-2969

A new version (2.8.1) of the Miradore connector for Microsoft Active Directory was compiled using newer SSL/HTTP libraries and certificate container file.

MO-2897

Data imports from Miradore connector for F-Secure Protection Service for Business started to fail since July 2018, because F-Secure made some unexpected changes to their web API. This problem was fixed in the connector version 1.1.0 by modifying the import procedure.

MO-2077

MO-2082

MO-2822

A new version of Endpoint Backup client (6.2.7) has been released with the following improvements:

• It's now easier to analyze deleted files in the Endpoint Backup client, because the showing of deleted files can now be enabled simultaneously with the "All files" and "Files modified in last 7 days" options.

Fixed bugs:

• File restoration through the Endpoint Backup client  failed without error message if the backup had been taken of a folder which has a restricted access  After this fix, the Endpoint Backup client will report the success of the file restoration attempts.

• Previous versions of the Endpoint Backup client generated excessive temporary files to the backup location if network issues occurred when files were being backed up to a network share. The fixed client always creates only one temporary file per backup. All temporary files, including the unnecessary files created in the past, will be cleaned up from the backup folder when a backup job completes successfully next time.

Refer to Upgrading Endpoint Backup clients if you need instructions on how to upgrade the Endpoint Backup client for your managed devices.

ID

Feature

Description

MO-1448

Asset management

Users, who have a permission to activate configuration items, can now activate the items directly without having to first request the activation. This usability improvement simplifies and speeds up the process of creating new asset models, group distributions, managed software, locations, organisations, packages and subnets.

See System permissions by user roles article to learn which users can create and/or activate different items.

MO-1878

Asset management

A new task for importing assets from file to asset groups was added to the Asset group item's Analyze > assets tab.

This task takes a list of device names, separated by line breaks, as input and adds the assets to the asset group. Notice that the device names need to be unique, and there must be an asset configuration item for each device name in Miradore Management Suite already before the import.

For more information and instructions, please refer to Modifying members of an asset group.

MO-2018

Asset management

There is a new automation task action for asset status change. With this new action it is possible to automatically set the status for the specified group of assets. This improvement makes the asset status update more effective since less manual work is required. Find more information and instructions from the article "Status change of the assets with the automated task".

MO-2747

Asset management

Miradore users with Helpdesk role can now create Self-service enrollment items for the end-users at the Self-service enrollment view.

MO-2828

Asset management

Miradore client wake-up now supports WebSocket communication protocol for all supported device platforms (Linux, macOS, Windows). When WebSocket is used, it is enough for all client - server communications if the client can access server HTTP(S) port.

By default, Miradore Management Suite still uses TCP with port number 32227 to send the client wake-ups, but administrators can now configure the system to use WebSocket as the primary communication protocol for client wake-ups in "Miradore System settings > Clients > General > Server network configurations" if they want to.

For more details, please read Miradore client wake-up.

MO-2930

Asset management

The possibility to add new connector configurations through Miradore system settings was removed for most connectors, because the connector configurations will appear in the system settings automatically when the connectors are installed using the installers as instructed in the product guide. Only exception is the connector for Miradore MSP console, which is intended to be added through the system settings instead of running the connector installer.

MO-2775

Dashboards

The configuration of dashboard widgets was made easier by adding a gallery of ready-made widgets to the dashboard widget wizard. The widget gallery contains a selection of widgets for different purposes and users can simply pick any of the widgets to the dashboards without having to create the widgets by themselves.

Also the reuse of users' custom widgets was made easier, because now it is possible to copy widgets between dashboards which saves users from having to recreate the same widgets again.

MO-2711

Documentation

Added field descriptions for the "Randomize start time" and "Run after every boot" fields in the product guide. These setting fields are located at the Custom scheduled task item under System settings > Clients > General. See field descriptions from the Custom scheduled task item attributes page.

MO-2809

Documentation

A new help article explaining the inventory information collected from the hard drives in managed devices was added to product guide. The added article explains which SMART attributes Miradore clients try to collect and what their values actually mean.

MO-3005

Documentation

The Product guide of Miradore Management Suite now supports Google Chrome browser.

MO-2429

Installation management

Information fields "Miradore client version", "Package run as" and "Package status" were added to the report builder, web service API and also in the following pages in the user interface of Miradore Management Suite:

• Software management > installation status > Package distributions view

• Asset form > Distribution status

• Distribution status pop up in Asset form > Distribution status tab > Status column link

MO-2630

Installation management

Device users couldn't see the name of the supervisor(s) responsible for software approval requests in the Self-service portal. This was problematic, because the users didn't know whom to approach if there was a long delay in processing the software approval requests. Now the name of the supervisor is added to the Self-service portal and the device users know to contact their IT-support if the defined supervisor is not available.

See article How to request for a software using Self-service portal for more information.

MO-2953

Installations management

Initial installation setup scripts were improved to support a few new variables: Location full name (Location), Location short name (LocSN), Organization full name (Organization), Organization short name (OrgSN), Windows user ID (EndUserID). The variables can be used within the operating system specific VBScripts to customize initial installation.

MO-2603

Patch management

Miradore's patch management feature now supports the management of Windows 10 version updates. This means administrators can monitor and control the installation of Windows 10 version updates for managed devices.

See Managing Windows 10 version updates for more information.

MO-2653

Patch management

Clarified the logging of Miradore Management Suite's patch management client by rearranging the log entries.

MO-2917

Patch management

The performance of Miradore's Patch manager component was improved by reordering the patch manager's tasks. This shortens the running time of the Patch manager when it delivers metadata about new patches to Miradore Management Suite.

MO-2918

Patch management

Miradore's Patch manager component was changed to periodically clean up useless patch files from the media master installation point to save disk space.

MO-1966

Reporting

Two new data columns (Child asset, Parent asset) were added to the Report builder under the Asset item. This improvement enables to build a report or dashboard which shows the child-parent relationships of managed assets.

MO-2479

Reporting

The readability of some numeric asset configuration item inventory attributes was improved by converting the values into more appropriate units. For example file size and disk capacity attributes are now presented with less decimals in megabytes or gigabytes instead of showing the values in bytes.

MO-1873

System internal

Added a database cleanup task which removes duplicate Miradore system tasks during Miradore upgrade. All system tasks can be seen on the System tasks tab in the system settings of Miradore.

MO-2501

System internal

SQL Server 2017 Express edition is now installed with the Miradore Management Suite installation by default.

MO-2750

System internal

Telerik UI for ASP.NET AJAX was upgraded to the latest version (R2 2018). The user interface of Miradore Management Suite uses Telerik UI controls.

The update addresses multiple usability issues and improves the browser compliance for the latest browser versions.

MO-2573

System security

Added possibility to export GDPR related user data to an XML format in Operations > Users > User >Tasks. Further information can be found from the article "Exporting GDPR related user data".

MO-2347

System usability

Miradore Management Suite 5.0.0 makes the setup process of new Miradore instances easier as it comes with default user, location, organization, and asset model items and with the possibility to install a Miradore client to Miradore server with the installer of Miradore.

This means that you no more have to create user, location, organization and asset model items as a first thing when you set up new instances. Instead, you can start managing devices immediately and assign them to the default location, user and organization at first. You can then modify or rename the default items later if you want to.

As said, during the setup Miradore installer now also asks whether administrator wants to install a Miradore client on the Miradore server. This makes it easy to start managing the server with Miradore, and helps you see how managed assets look like in the system when you log in for the first time. The server asset is assigned to the default user and location.

MO-2904

System usability

Miradore Management Suite installer now automatically suggests to use the fully qualified domain name of the server in the instance settings when installing new instances. In earlier versions the installer suggested the host name only which sometimes caused problems to the client connections.

MO-2925

System usability

In some item forms the selected user attribute couldn't be removed even the field was optional. Added the possibility to clear the value if the field is not mandatory.

MO-2244

MO-2429

MO-2479

MO-2872

Web service API

Here's a list of improvements to the web service API in Miradore Management Suite version 5.0.0:

• Support for reading asset extension "InvFinancialData". This asset extension contains information about the financial information related to the asset. All available attributes and their data types are listed in the web service API specification.

• Added support for reading three new attributes ("ClientVersion", "PackageStatus" and "PackageRunAs") of Distribution item or asset extension "DistributionStatus" through the web service API.

• Added several new attributes for asset inventory extension items in order to improve the readability of numeric inventory attributes.

• Fixed a bug which caused data formatting issues when the "showother" grouping option was used in querying boolean or datetime data.

For more information, read Miradore web service API specification.

ID

Feature

Description

MO-1952

Asset management

The changes made by the 3 Step IT connector weren't written to event logs in Miradore. From now on, the changes to financial transactions, contracts and suppliers made by the connector are updated to the corresponding event logs in Miradore.

MO-1954

Asset management

Device name generation failed during initial installation if the device had multiple usages selected and the naming profile utilized the device usage information for generating the device name.

MO-2116

Asset management

Display resolution was almost always reported incorrectly as 1024x768 for managed assets. The inventoried display resolution can be found from the Asset configuration item's Hardware inventory report tab.

MO-2125

Asset management

Asset auto-generation failed for some macOS and Linux devices when the devices were imported to Miradore Management Suite using asset data import. In fact, Miradore managed to generate asset configuration items for the devices and activate the assets too, but the operating system was not identified correctly. Therefore, the operating system field at the asset configuration item showed "Unknown OS version".

MO-2683

Asset management

Removal of dynamic asset groups was complicated because it was not possible to remove dynamic asset groups and its bindings directly.

MO-2763

Asset management

The performance of the Asset model item's "PnP device and drivers" analyze view was improved.

MO-2804

Asset management

Possible error messages weren't shown to user at the Asset model form when the user tried to activate the asset model item. If an error occurred, the activation just failed without any explanation.

MO-2808

Asset management

Most inventory data imports failed if SQL Server 2008 was used to host the database of Miradore Management Suite 4.7.0 because the inventory import script couldn't find the correct Bulk Copy Program utility. This problem didn't affect earlier versions of Miradore Management Suite.

MO-2861

Asset management

Subnet field was hidden at network device's asset configuration item what made the editing of the field complicated. After this fix the subnet field is visible also assets with the role "Network Device" when the DHCP value is not enabled.

MO-2883

Asset management

In certain scenarios, Miradore generated a duplicate asset configuration item for a device while running an initial installation. As a result, also the package installation attached to the initial installation got skipped.

MO-2893

Asset management

In some cases Windows 10 Education version was not recognized in asset auto-generation's OS identification process and the value of the OS was marked as "Unknown".

MO-2950

Asset management

Asset data import updated warranty information for existing asset configuration items even though the warranty information was not provided in the import XML file.

MO-2975

Asset management

Assets' contract information didn't get updated when importing asset data from XML to Miradore although the "Update asset attributes" setting was enabled from the system settings of Miradore.

MO-2977

Asset management

Miradore failed to set asset's location/cost center during asset data import if there were multiple items with the same name in the system. This fix changes the asset data import process so that now Miradore uses also the item hierarchy in addition to the item name in determining the correct location/cost center for the imported assets.

MO-2540

Automation engine

Automation engine failed to run automation tasks if special characters were used in the report filters within the automation task configuration.

MO-2557

Automation engine

Automation engine can be configured to send reports to users as email attachments according to a schedule.

There was a bug in this feature, which caused the automation engine to send empty email attachments to the users if certain extended ASCII characters were used in the report filters.

MO-2771

Installations management

There was an issue with the driver detection in the initial installation feature of Miradore. Due to the bug, driver detection sometimes failed during the initial installation with the error message "Could not query device names and drivers from the server".

MO-2800

Installations management

There was a bug in the "debian_dvd_to_repository.sh" script which caused the downloading of netboot modules to fail when user was adding the installation media of a Debian Linux to installation points. After this fix, the script asks user to select a suitable mirror where the files should be downloaded if the download would fail.

MO-2806

Installations management

An inaccurate error message was shown when a user tried to edit a package which was waiting for approval. The error message was reviewed.

MO-2866

Installations management

All files were deleted from child installation points if a timeout occurred when the master installation point was performing a file scan. This could happen for example if the file scan exceeded the allowed time frame defined for the file scans.

MO-2901

Installations management

Package deployment failed often if either "Message window" or "User message" action was placed as the first package action. This happened because there was a bug in computing the return code of those package actions.

MO-2921

Installations management

Initial installation console hung when showing the "Scanning PNP devices..." message if driver rules were in place and the length of the driver folder's path exceeded 200 characters.

MO-3025

Installations management

Driver import failed without error messages when the "GetDrivers.cmd" was executed if the driver's inf-file contained unexpected characters like trailing dots in the TargetOSVersion. The fixed script removes the unnecessary characters.

MO-2934

Patch management

Miradore's Patch manager component failed to run if certain run time dll file was missing. This fix eliminates the dependency on that file.

MO-2958

Patch management

"Status change date" column was removed from the Security patch status view.

MO-2963

Patch management

Inventory and status information about patch installations is shown on the Asset configuration item's Security tab. This includes also showing the error message for failed patch installations.

Unfortunately, there was a bug in showing the error message if multiple errors occurred because the field didn't update. Instead, the field kept on showing the error message which appeared first.

MO-2970

Patch management

Miradore's patch management client couldn't connect from managed devices to installation points if the "miradore.xml" file was missing from the installation points. This problem concerned new installation points that had been installed using Miradore Management Suite 4.7.0 installer, because the installer didn't create that file as expected.

MO-3013

Patch management

In certain scenarios Miradore's patch management client misidentified the managed computer's operating system version.

MO-2666

Remote control

Earlier computer end-users had to launch remote assistance sessions by clicking the "Start" button. This was problematic because if the end-user clicked the button too early, the remote assistance session failed.

This fix changes the functionality so that the remote assistance session is now opened automatically when administrator launches the remote control session. The end-users don't need to click the "Start" button anymore to launch the remote assistance sessions.

For more information, please see the article "How to use Remote assistance".

Notice

If you had customized the contents of the remote assistance window header and description fields, please make sure to review the texts in "System settings > Main > Remote control > General".

MO-2244

Reporting

Fixed a bug which caused inconsistency in the data formatting of date and boolean values when the option "Show rest as Other" was selected on the dashboard.

MO-2815

Reporting

A JavaScript error occurred when user tried to drill down in a history data widget through a shared dashboard.

MO-2888

Reporting

Members of the Report builder group weren't able to create or edit reports in Miradore Management Suite 4.7.0.

MO-2770

System internal

Upgrading a Miradore Management Suite instance with the installer sometimes failed if there were multiple Miradore Management Suite instances with almost identical names running on the same server. The upgrade failed with the installer telling that the installer doesn't support upgrading from the current version.

MO-2922

System internal

Under system settings there is this setting which defines how Miradore behaves when auto-generating asset configuration items for devices that already have a removed asset configuration item in the database. Any changes to this setting were recorded in the system settings' event log with an incorrect field name.

MO-2966

System performance

Data export from Report builder to Excel crashed when trying to export thousands of rows of data with child items. This fix improves the performance of the reporting engine significantly.