This page lists all the required actions to upgrade Miradore server from an older version. Please note that upgrade notes are cumulative: When upgrading a very old version of Miradore server, be sure to go through all the upgrade notes beginning from the upgraded version to the latest version.
Miradore installer can be used both to install new Miradore server and to upgrade existing servers.
Normal version of the Miradore installer (Miradore580.exe) downloads needed prerequisites from Miradore support site. If some of the prerequisites are missing, the installer will download them from the Internet.
Full version of the Miradore installer (Miradore580_Full.exe) includes all the prerequisites needed to install Miradore server (.NET framework 4.7.2, SQL Server 2017 Express, and Report Viewer 2012). Internet connection is not required during the installation.
In case your master installation point is not located on the Miradore server, you must update the master installation point separately.
Before upgrading, make sure that you have a good database backup available!
Check out the latest versions of Miradore clients and connectors.
Before starting upgrade, it is recommended to read and prepare a rollback plan for Miradore instance upgrade.
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. We highly recommend upgrading any earlier versions of Miradore Management Suite as soon as possible although there aren't any known exploits of these vulnerabilities.
Miradore Client for Windows 3.5.12. Check Release history for changes.
We recommend upgrading all 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 the "Windows Client version = 3.5.12" and "Automatic upgrade enabled = Yes".
WithSecure Elements connector replaces F-Secure PSB connector. Please upgrade the old connector by installing the new connector on the same machine, it will uninstall the old before proceeding with the installation.
After the connector upgrade, get the client id, secret and organization id from the WithSecure Elements UI and reconfigure the new connector in the System settings > Connectors > WithSecure Elements Connector.
Managing the credentials is made more secure on package installation that is configured, in the software package settings, to be done via installation points.
It is recommended to update actions "HTTP download" and "Connect network drive" on software packages with the new versions released with the latest Miradore Management Suite 5.8.0.
This version adds several new items and attributes to Web Service API.
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.
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.
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.
Miradore Client for Windows 3.5.11. Check Release history for changes.
We recommend to upgrade all 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 the "Windows Client version = 3.5.11" and "Automatic upgrade enabled = Yes".
SNMP scanner 2.4.0 supports communication using TLS 1.2.
Starting from this version, only user accounts with Administrator or Editor privileges are allowed to run Miradore Command line tool.
In addition to a new execute operation RunNow for SystemTask item, this version adds several new items and attributes to Web Service API.
Good to know: Miradore Management Suite 5.6.0 can be hosted on Windows Server 2022
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.
Miradore Client for Windows 3.5.10. Check Release history for changes.
We recommend to upgrade all 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 the "Windows Client version = 3.5.10" and "Automatic upgrade enabled = Yes".
Miradore Client for macOS 1.6.9. Check Release history for changes.
We recommend to upgrade all 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 the "Mac OS X Client version = 1.6.9" and "Automatic upgrade enabled = Yes".
Miradore Client for Linux 1.6.9. Check Release history for changes.
We recommend to upgrade all 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 the "Linux Client version = 1.6.9" and "Automatic upgrade enabled = Yes".
Miradore Online connector 1.2.0
This new connector version improves the reliability of data queries from Miradore MDM to Miradore Management Suite. In the previous connector versions, the data queries were lately troubled with slowness and timeouts.
In case you have had the connector in use already, it is recommended to remove and re-create the connector's Windows Scheduled task in the connector host computer's Windows Scheduler, because in this new version we have optimized the scheduling for running the connector.
Support for Windows Phones is about to end on Miradore's MDM product, and therefore, this connector no more imports data about Windows Phone devices.
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 will be removed during the upgrade.
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.
Remote Control Administrator Clients need to be uninstalled manually, there is no package for that.
After the upgrade, you can manually uninstall Remote Control server from your environment.
Miradore 5.4.0 contains major changes to the Patch management features. Make sure to read the How to upgrade MMS 5.3.0 or earlier version to MMS 5.5.0 or higher before upgrading your environment.
Only change in Miradore Client for Windows 3.5.9 is that it adds support for patching the device during initial installation. Previous Client versions didn't support this feature.
Miradore Client for macOS 1.6.7 adds support for macOS Big Sur and ARM-based systems. Miradore 5.3.0 or older instance versions do not support the management of macOS Big Sur devices.
Miradore Client for Linux 1.6.6 adds support for managing devices with Ubuntu 20.04.
Active Directory connector 2.8.5 fixes a bug in the handling of SSL certificates. Use this connector version if you want to use HTTPS connection between the connector and Miradore server.
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".
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".
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".
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.
Support for Windows Server 2008 and 2008 R2 has been dropped. See How to install Endpoint Backup server for server requirements.
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.
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 now 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 the target OU was not specified on the connector form. This caused problems when reinstalling computers.
Upgrade ODJ Connector using the installer available at: <Miradore server installation directory>\Connectors\ODJ.
Microsoft SCCM Connector version 1.3.6 contains security improvements and changes to the communication with Miradore server. Old connector versions will not work with Miradore 5.3.0.
Upgrade the SCCM connector using the new connector installer. The installer can be found from <Miradore server installation directory>\Connectors\SCCM directory.
New version 1.6.0 of F-Secure Policy Manager Connector supports F-Secure Policy Manager up to version 14.41. Notice that 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
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.
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.
Miradore Client for Windows 3.5.6 fixes a scheduling bug regarding maintenance windows for patching
Miradore Client for Linux 1.6.5 adds support for managing devices running Debian 10
Miradore Client for macOS 1.6.5 is notarized by Apple and it adds support for managing macOS Catalina (version 10.15) devices. Support for OS X Mountain Lion (10.8) or older versions is discontinued
Connector for F-Secure Protection Service for Business 1.2.0 containing bug fixes
Miradore Online Connector 1.1.8 is compatible with TLS 1.2 and TLS 1.3. The connector host is required to have NET Framework version 4.7.2 installed
Good to know: This is the last version of Miradore Management Suite which can be hosted on Microsoft Windows Server 2008 or 2008 R2. The support will be dropped in the next version due to Microsoft ending its support for these operating systems on January, 2020
Miradore client for Windows 3.5.5 contains the following improvements:
Collects inventory data about boot duration.
Adds support for Windows Server 2019 management.
Supports the use of HTTP installation points for package deployments.
This client version improves support for HTTPS certificates issued by internal certificate authority. For more information, please contact to Miradore support.
Several bug fixes.
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.
Miradore's Remote Control Server component was recompiled, because the remote control session reporting didn't work over TLS 1.1. and 1.2 with the previous Remote Control Server version.
New version 1.0.4 of the Remote Control Server supports TLS 1.1. and TLS 1.2 encrypted connections to Miradore server.
Miradore client for Linux 1.6.4 contains the following improvements:
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).
Miradore client for macOS / OS X 1.6.4 contains the following improvements:
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).
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.
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.
Several other 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.
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.
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)
OpenSSL and libcurl libraries and the rootcerts.pem certificate file were included in the Miradre 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.
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.
See Upgrading macOS clients for more instructions.
A new version of Miradore Patch manager component has been released. If your media master installation point is not located on the Miradore server, you need to upgrade the Patch manager component separately on the media master installation point server using Miradore installer.
The previous version of Miradore client deployer uses an outdated HTTP/SLL library, which may cause connectivity issues between the deployer and Miradore server. The problem is fixed in Miradore client deployer version 1.4.4 and it is recommended to upgrade older Miradore client deployers to this version.
Miradore Endoint Backup client 6.2.7 contains one usability improvement and two bug fixes. See Upgrading Endpoint Backup clients for upgrade instructions.
Miradore connector for Microsoft Active Directory 2.8.1 contains updated SSL/HTTP libraries and certificate container file.
Miradore connector for F-Secure Protection Service for Business 1.1.0 fixes a bug which caused the connector's data imports to fail since July 2018.
Miradore connector for 3 Step IT 4.0.0 contains a few improvements and it uses REST API to connect to 3 Step IT Asset Management. More information about the improvements in release history.
How to upgrade:
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.
Miradore client for Windows 3.5.2 fixes the following bugs found in earlier client versions:
Previous client version ignored the package setting "Hide messages". This means that, regardless of what had been configured in the package settings, Miradore client always displayed the tray messages to the user when a package installation started or ended on a managed Windows computer.
Miradore Windows client versions 3.5.0 and 3.5.1 failed to perform package installations on a domain controller. The issue is fixed in the newest client. Notice that domain controllers having Miradore client version 3.5.0 or 3.5.1 need to be upgraded to client version 3.5.2 manually because the installation of the automatic upgrade package fails.
It was not possible to configure proxy in the installation wizard of the earlier client versions, because the proxy configuration dialog was not shown to the user.
Miradore client for Linux 1.6.1 fixes two separate issues which could cause the client to get stuck or stop working unexpectedly on Linux devices.
Miradore client for macOS / OS X 1.6.1 fixes the following bugs found in earlier client versions:
There were two separate issues which could cause the client to get stuck or stop working unexpectedly on Mac OS X or macOS devices.
Miradore client's tray app crashed on some macOS computers when user tried to open Miradore Self-service portal and prevented the use of the Self-service portal.
Miradore connector for F-Secure Policy Manager was recompiled with newer SSL/HTTP libraries, and therefore, a new F-Secure Policy Manager connector version 1.5.4 is released with Miradore Management Suite 4.7.0.
If you are using Miradore Management Suite's web service API, we strongly recommend to check all web service queries where "GroupBy" query setting is used, because a small change has been made to the response returned. Earlier, the <Items> element unnecessarily appeared twice in the web service response when "GroupBy" option was used in the query. Starting from Miradore Management Suite 4.7.0, the <Items> element will be included in the web service response only once.
Miradore Management Suite 4.6.0 no longer supports the TCP connection method between Miradore clients and Miradore server. Make sure that all Miradore clients in your managed environment are using the HTTP connection method to connect to the Miradore server. For instructions, please read Configuring client - server connectivity.
We're also releasing Miradore client for Windows version 3.5.0. Like we mentioned in the release notes of Miradore Management Suite 4.5.0, all features related to the TCP connection method have been dropped from this client version. The HTTP(S) connection method should be used instead. Miradore Windows Client 3.5.0 also adds the support for running packages in a specific context. Older client versions don't support this feature.
The new version 1.6.0 of Miradore client for Mac OS X and macOS introduces three major improvements: It enables to manage macOS 10.13 High Sierra computers, it adds the possibility to use Miradore Self service portal on Apple Macs having some of the supported operating system versions installed, and it sets tighter user permissions for the Miradore client configuration file which was earlier subject to unauthorized reading
Miradore client for Linux 1.5.8 sets tighter user permissions for the Miradore client configuration file which was earlier subject to unauthorized reading.
Miradore's Endpoint Backup Client for Windows was recompiled with the latest OpenSSL libraries, and the Endpoint Backup Client version was therefore incremented to 6.2.5.
Miradore's Endpoint Backup Client for Macs was also incremented to version 6.2.5 and recompiled with the latest OpenSSL libraries, because the endpoint backup client's background process crashed on Macs with the old libraries.
Miradore Online connector 1.1.6 adds a filter for ignoring Windows 10 computers from the asset data that is imported from Miradore Online to Miradore Management Suite, because Windows 10 computers were causing a lot of warning entries to the connector's log file. We recommend to upgrade your Miradore Online connector especially if you have or plan to enroll any Windows 10 computers on to your Miradore Online site.
Miradore connector for Blancco Management Console 1.3.0 adds support for the HTTPS connection method between the connector and BMC. The new connector version requires .NET framework 4.5.
The XML file format was slightly updated for the asset data import process by adding support for a new XML file element <DetailedStatus>. Please make sure to provide the detailed status within the XML in your integrations and asset data imports, especially if you have configured the detailed status to be required in your Miradore environment, because otherwise, the asset data imports may fail. You can check whether the detailed status is required in your Miradore instance from System settings > Asset management > Asset status definitions.
Miradore Management Suite 4.6.0 fixes two possible SQL injection vulnerabilities. No exploits have been reported, but we recommend all of our customers to upgrade their Miradore Management Suite instances to the version 4.6.0 in order to control security risks.
Miradore client for Windows 3.4.4 improves the patch scanning and installation process during maintenance windows. When used in conjunction with the Miradore Management Suite 4.5.0, the new Miradore Windows Clients now re-scan the patching status after a reboot and perform more patch installations during the same maintenance window if there still is time left and packages to install. In earlier versions, the patch scan was not performed again after a reboot during the same maintenance window, which slowed down the patching process if there was more patches waiting for installation.
Miradore client for Windows 3.4.4 also fixes one security vulnerability in the client's installation directory plus two bugs in the client's user messages. Firstly, the group distribution's postpone option was not always correctly shown to the user, and secondly, some characters were not showing correctly in certain user messages or popup windows.
Miradore client for Linux 1.5.7 adds support for managing Debian 9 devices, and also improves the runtime configuration for scheduler jobs.
Miradore client for OS X / macOS 1.5.7 fixes a major bug in the custom inventory feature.
Miradore Endpoint Backup Client 6.2.4 fixes major bugs in the endpoint backup feature. For further reading, please read How to upgrade Miradore Endpoint Backup clients.
The new version 3.0.0 of Miradore connector for 3 Step IT can now be configured to synchronize data between Miradore Management Suite and multiple customer instances of 3 Step IT. This can be done by configuring the IDs of the desired 3 Step IT instances to the Customer ID field in the connector settings in Miradore. Separate multiple customer IDs with commas.
According to SQL Server best practices, it is recommended to set the built-in system administrator (SA) account as the default owner for all databases. Therefore, the installer of Miradore Management Suite 4.5.0 was modified to set the SA account as the database owner when installing new or upgrading the existing Miradore Management Suite instances.
Earlier the user account, who executed the Miradore Management Suite installer, was assigned as the database owner, but that was problematic if the user account was removed later.
Subnet item's attribute Public IP was changed as Public IPs which means that multiple public IP addresses can now be saved for a Subnet item.
If you had used the Subnet item's Public IP attribute in previous Miradore Management Suite versions to build custom view reports or report builder reports, please check the data columns, filtering settings, and data sorting settings of the reports. The Public IPs attribute in its current form contains a bit differently formatted data, and thus it may break any existing reports or web service integrations containing the Public IP information.
This is the last Miradore Management Suite version which supports the TCP connection method between the Miradore clients and Miradore Server. Therefore, it is recommended to configure your Miradore clients to use the HTTP connection method as soon as possible if you haven't already done so.
Remote Control Administrator Client was upgraded to version 1.0.4.0. The new version renews the Remote control administrator client's license key. Notice that Remote Control Administrator Client 1.0.3.4 stopped working on 4th February 2017 due to the expired license, which means that all Miradore Remote Control Administrator Clients in the managed environment should be upgraded to the latest version as soon as possible. The renewed license will be valid until 20th February, 2019.
Miradore's Patch manager component downloads patch metadata from the internet and therefore it must be allowed to pass through the firewall to certain URL addresses. Notice the following changes in the download addresses:
http://miradore.cdn.heatsoftware.com --> http(s)://absolute.cdn.heatsoftware.com
https://a248.e.akamai.net/ (Not required anymore - will be retired on May 31, 2017 )
Miradore connector for F-Secure Policy Manager was upgraded to version 1.5.2. The new connector version adds support for the new F-Secure database structure introduced in F-Secure Policy Manager 12.1. The connector also supports F-Secure Policy Manager 12.2. Support for the old 9.x versions is discontinued. Also, earlier, the administrator had to define the F-Secure version manually during the connector installations, but this new connector detects the F-Secure version automatically.
Good to know about client upgrades:
The upgrade process has been improved for Miradore Windows Client, Endpoint Backup Client for Windows, and also for the Miradore's Remote Control Client.
Earlier, the needed upgrade files were copied to the devices from a network share or installation point, but the upgrade failed if those were not accessible from the devices. Therefore, the upgrade process has now been improved to lastly copy the upgrade files directly from the Miradore Management Suite server if network shares or installation points are not accessible at the moment. This enhancement should improve the reliability of the client upgrades.
Two possible security vulnerabilities were identified from Miradore Management Suite server in an independent security audit. Both vulnerabilities are potentially exploitable from a remote computer, and these both security issues are fixed in Miradore Management Suite 4.4.0. We highly recommend to upgrade earlier Miradore versions as soon as possible, although we haven't heard of any occurrence of anyone exploiting these vulnerabilities. For more information, please read the release history.
Miradore Windows client was upgraded to version 3.4.3. The new client fixes a bug in device identification, and therefore it is recommended to upgrade all Windows clients to the latest client version. The new Miradore Windows client also fixes a scheduling problem in installation point replication why all installations points should be also upgraded to use the latest client version.
Miradore client for Linux was upgraded to version 1.5.5. The new version adds support for the management of devices running Red Hat Enterprise Linux 7 and Community Enterprise Operating System 7.
Miradore client for OS X and macOS was upgraded to version 1.5.5. The new version adds support for the management of macOS Sierra (10.12) devices.
Earlier it was possible to set Miradore Windows client and scheduler startup delays freely, but it was found out that problems may arise if Miradore Windows client startup delay is greater than scheduler startup delay. Therefore, it is now required to use greater startup delay for the scheduler than what is used for Miradore Windows client. If you upgraded to Miradore Management Suite 4.4.0 from a previous version with upgrade installation, please check the startup delay settings. To do this, navigate to "Administration > System settings > Clients > Windows" and make sure that the startup delays have been properly configured.
Miradore Management Suite 4.4.0 introduces new settings for the bandwidth management of package distributions. There are, for example, two new fields at the Package item, which can be used to enable/disable the bandwidth limitations for each package separately. Important: These settings are enabled by default for all new and existing packages when Miradore Management Suite is upgraded from a previous version to Miradore Management Suite 4.4.0. However, the settings don't have any effect on anything before you configure the bandwidth limitation settings to the Location items.
Miradore connector for Blancco Management Console was upgraded to version 1.2.0. Old connector versions didn't anymore work with Blancco Management Console 3.6.0 or newer versions. The latest connector version supports Blancco Management Console up to the version 3.7.2.
Miradore MSP Console connector was upgraded to version 1.5.6 and the Miradore MSP Console was upgraded to version 1.5.4. Most significant changes in these components consider the management of Miradore licenses, because Miradore Management Suite 4.4.0 introduces some changes to the licensing terms. In short, installations management feature and remote control feature must be enabled with Miradore license from now on, before they can be enabled for use in the Miradore Management Suite instance. The Miradore MSP Console is a special tool for IT Service providers for managing multiple instances of Miradore Management Suite through a single console.
Miradore client for Windows 3.4.2 adds support for patch maintenance windows. The patch maintenance windows are used in patch management process to define time slots when Miradore clients can perform security patch installations.
Miradore connector for Microsoft Active Directory version 2.8.0 is released with Miradore Management Suite 4.3.1, including multiple improvements. For more information, see connector datasheet.
Miradore client for Windows version 3.4.1 contains three bug fixes regarding the client's default settings, IPv6 connection method, and error handling. For more information, see MO-1273, MO-1362, and MO-1365.
The handling of client wake up requests was improved for Miradore Linux and Mac OS X clients. A new version 1.5.3 was released from both of the Miradore clients. The latest Miradore client for OS X also fixes a bug in the reporting of self-service device enrollments.
Miradore Online connector was modified to support the changed identification logic of Android devices. The latest Miradore Online connector version is 1.1.0. Miradore Management Suite 4.3.0 doesn't allow any connections from the previous connector versions, and therefore it is mandatory to upgrade Miradore Online connectors when moving to use Miradore Management Suite 4.3.0.
New Miradore Endpoint backup client version 6.2.2 fixes a bug (MO-1314) and )improves the status reporting of endpoint backup jobs. See the description of MO-1352 minor improvement from the release history for more details.
Remote Control Administrator Client was upgraded to version 1.0.3.4. The new version renews the Remote control administrator client's license key.
Miradore connector for F-Secure Policy Manager was upgraded to version 1.5.1. The new version was modified to use the latest file transfer library "libcurl".
Miradore connector for 3 Step IT was upgraded to version 2.9.0. The new connector version can be configured to import and export data regarding owned assets. Also, it is now possible to configure multiple 3 Step IT connectors for one instance of Miradore Management Suite.
Miradore client for Windows was upgraded to version 3.4.0.
Miradore client for Linux was upgraded to version 1.5.2. The new version fixes a bug in forwarding wake-up messages to other computers.
Miradore client for Mac OS X was upgraded to version 1.5.2. The new version fixes a bug in forwarding wake-up messages to other computers.
The security patch download URL for Patch manager component changes. Check that Patch manager is allowed to access http://miradore.cdn.heatsoftware.com
Remote control client 1.0.3.4, including a bug fix, was released together with Miradore Management Suite 4.2.1.
Endpoint Backup Server was improved to use support SQL Server Express 2014 and .NET framework 4.5. New component version is Endpoint Backup Server 1.4.0.
Endpoint backup client was upgraded to support new endpoint backup features, such as backup window and backing up with local system account. New Endpoint Backup Client version is 6.2.0.
Miradore connector for Blancco Management Console was upgraded to version 1.1.0, adding support for BMC 3.x versions.
Command line tool was upgraded to version 1.4.1.
Miradore client for Windows was upgraded to version 3.3.9. The new version uses the latest libcurl library for file transfers. It is highly recommended to upgrade the client in all managed Windows computers.
Miradore client for Linux was upgraded to version 1.5.1. The new client fixes multiple bugs, and it is highly recommended to upgrade the client in all managed Linux computers.
Miradore's TCP client connector was upgraded, and it can be used normally with Miradore again. In Miradore 4.1.1, the TCP client connector was not supported.
Miradore connector for F-Secure Policy Manager was upgraded to version 1.5.0, adding a support for Policy Manager version 12.
Miradore connector for SCCM was upgraded to version 1.3.1. The latest version fixes a bug (MO-901).
Miradore connector for 3 Step IT was upgraded to version 2.8.0, adding support for importing "EndingOptionInfo" attribute from 3 Step IT to Miradore.
Support for multiple Miradore front-end servers was discontinued.
Miradore connector for Microsoft Active Directory (upgrade required. Earlier AD connector versions don't work with Miradore 4.0 or later.)
If you want to use the new patch management feature, make sure to install Patch manager with Miradore installer, and also ensure that you have installation points in place.
Upgrade Miradore client deployer
Miradore client for Mac OS X
If you are upgrading to Miradore 4.x.x, you must first upgrade to Miradore 4.0.0, because Miradore 3.x.x versions cannot be directly upgraded to Miradore 4.x.x versions.
If you're using Miradore's remote control feature, it is recommended to check that you are using the latest remote control components. Miradore Remote Control Administrator Client 1.0.3.2 was released with Miradore 4.0.0.
Miradore 3.8.0 contained an old, broken version of Miradore Push notification engine. Make sure that you update the Push Notification Engine to version 1.0.2 if you're managing Apple iOS devices in your environment.
Miradore connector for WSUS was updated to version 2.3.0 with this release of Miradore. The updated connector allows to import security update information to Miradore from SCCM.
If you are upgrading to Miradore 4.x.x, you must first upgrade to Miradore 4.0.0, because Miradore 3.x.x versions cannot be directly upgraded to Miradore 4.x.x versions.
If you are upgrading to Miradore 4.x.x, you must first upgrade to Miradore 4.0.0, because Miradore 3.x.x versions cannot be directly upgraded to Miradore 4.x.x versions.
Miradore 3.7.0 introduced some changes to the Miradore endpoint backup client. Therefore, it is recommended to update the latest version of Miradore endpoint backup clients to the installations points if the endpoint backup feature is used in the environment. This update is not necessary if the endpoint backup feature is not used. The latest endpoint backup client version is 6.1.2 and it can be also downloaded from Miradore support site. Also remember to update the Endpoint backup related settings in Miradore system settings when you move the updated endpoint backup clients to the installation points.
If you are upgrading to Miradore 4.x.x, you must first upgrade to Miradore 4.0.0, because Miradore 3.x.x versions cannot be directly upgraded to Miradore 4.x.x versions.
If you are upgrading to Miradore 4.x.x, you must first upgrade to Miradore 4.0.0, because Miradore 3.x.x versions cannot be directly upgraded to Miradore 4.x.x versions.
Initial installation of Windows 8.1 devices requires WinPE version 5.0 which means that any existing startup images need to be upgraded to WinPE 5.0. See Initial installation startup methods for instructions to Create the WinPE 5.0 startup images.
If you are upgrading to Miradore 4.x.x, you must first upgrade to Miradore 4.0.0, because Miradore 3.x.x versions cannot be directly upgraded to Miradore 4.x.x versions.
Miradore 3.6.0 requires Windows Server 2008 R2 SP1 or newer as the server operating system and SQL Server 2008 or newer as the database. Support for Windows Server 2003, Windows Server 2008 and SQL Server 2005 are discontinued. The reasons for the new minimum requirements include the adoption of the .NET 4.5 framework which is required for some of the new features. See the updated System requirements.
Miradore 3.6.0 installer requires that the database is upgraded to Microsoft SQL Server 2008 or newer prior to installation.
If you are upgrading to Miradore 4.x.x, you must first upgrade to Miradore 4.0.0, because Miradore 3.x.x versions cannot be directly upgraded to Miradore 4.x.x versions.
In order to connect Miradore 3.5.4 server (or newer) with Miradore MSP Console, the MSP Console must be version 1.3.0 or newer. It is highly recommended to upgrade all existing MSP Console installations to the latest available version. More about Miradore MSP Console.
If you are upgrading to Miradore 4.x.x, you must first upgrade to Miradore 4.0.0, because Miradore 3.x.x versions cannot be directly upgraded to Miradore 4.x.x versions.
Sampo connector v 1.5.0 released, upgrade recommended.
Starting from Miradore 3.5.0, it is no more possible to define location or organization based user permissions on the Location and Organisation item forms. Instead, it is possible to define Miradore user permissions (read/write) based on asset configuration item’s properties (device role, location, organisation) in Administration > Permissions > Item permissions view. All existing location and organization based Miradore user permissions will be automatically converted to a new configuration item based permissions model during the Miradore instance update.
If you are upgrading to Miradore 4.x.x, you must first upgrade to Miradore 4.0.0, because Miradore 3.x.x versions cannot be directly upgraded to Miradore 4.x.x versions.
If you are upgrading to Miradore 4.x.x, you must first upgrade to Miradore 4.0.0, because Miradore 3.x.x versions cannot be directly upgraded to Miradore 4.x.x versions.
After upgrading to Miradore 3.3.0, it is also required to renew the license for Miradore within 14 days from the upgrade. Refer to Miradore product guide for more information.
If the new partition-based system recovery feature is taken into use, a new WinPE image must be created.
See also