25.2.0 - Release Notes - Micetro

Micetro Release Notes
ft:locale
en-US
Product name
Micetro

November 13, 2025

Important: The Men&Mice Management Console was deprecated in version 25.1.0. It is not supported in version 25.2.0 and will not work, because the code has been removed. If you have any questions about features from the Management Console that are critical to your operation which you don’t currently see replicated in the Micetro Web Application, please contact BlueCat Support at support@bluecatnetworks.com.

New features

  • Multi-account discovery using AWS organizations: AWS multi-account discovery now reads account information from the AWS organization, supporting role-based access and ignore lists. It's now possible to authenticate with AWS instance credentials, aligning with best practices for credential management. For more information, refer to Set up Micetro to discover AWS Organizations.
  • Standardized BlueCat design: A new standardized UI with consistent typography, colors, and icons improves usability and visual cohesion across devices. As a result, Micetro's UI and user experience align with other products in the BlueCat catalogue.
  • Support for overlapping Cisco Meraki networks: Micetro now supports overlapping IP ranges across multiple locations and services for Cisco Meraki networks. As a result, address spaces have been renamed to organizations. For more information, refer to Separating and reintegrating networks and Managing organizations.
  • Threat Protect for MDDS appliances: Micetro's new DNS threat intelligence feature adds real-time detection and the ability to block user traffic to malicious domains on MDDS appliances. Additionally, improved support for response policy zones (RPZs) on BIND servers. For more information, refer to Threat Protect.

Improvements

  • API and functionality migration: The following API commands and functions that were previously available in the Management Console are now available in Micetro and/or the Micetro API:
  • DHCP policies: The ability to manage DHCP policies for Microsoft servers at both the server and scope level has been migrated from the Management Console, enabling more granular control over network beahvior, e.g., when managing different device types. For more information, refer to Managing DHCP policies
  • Documentation migration and improvements: The Micetro documentation has moved to the BlueCat Documentation Portal and has been revised for improved navigability and clarity. Documentation for older versions will continue to exist on https://docs.menandmice.com until they are no longer supported.
  • Management of cloud networks and services: Cloud network and service management has been added to the Web Application as part of the public cloud improvements described below. This is a partial migration of functionality that was previously available in the Management Console. For more information, refer to Cloud and cloud-managed services.
  • Quick command: Improved the quick command by adding an uninformed search in all DNS records and the ability to search for fully legal client identifer strings, such as MAC Address. For more information, refer to Searching with the quick command.
  • Public cloud improvements: IPAM data is now pulled through the DHCP Agent instead of Micetro Central. By default, the upgrade to version 25.2.0 assumes that the DNS and DHCP Agents are running locally on the same server as Micetro Central. As a result, no changes to ports or firewalls are needed in order to keep cloud functionality working. A local DHCP agent must be running on existing installations to ensure that IPAM cloud functionality works correctly after updating to version 25.2.0. It's possible to move the agents to other servers if a customer's environment requires it, but this may require infrastructural changes to ensure communication with the public clouds. For more information, refer to Integrating cloud services.
  • Reverse zone management: The ability to create and manage reverse zones for IPv4 and IPv6 in Micetro has been migrated from the Management Console. For more information, refer to Creating reverse zones.

Bug fixes

  • Added a more descriptive warning in case of TLS certificate errors on older version of Windows (KI-026678)
  • Added the option to add a CAA record with the issuemail type (KI-026430)
  • Changed the default behavior of scripts for DNS record changes so that they only run when changes are made through Micetro and not as the result of external changes. If users want to change this function so the scripts run upon external changes, they can set the RunExternalScriptsOnDNSZoneSync preference value to true (KI-026054)
  • Fixed issue that prevented the client from establishing a connection with the given credentials when trying to update the AWS multi-account access key ID (KI-026265)
  • Custom properties for IP addresses, DNS records, and change requests are now reloaded when manual failover is performed to a server that was previously active in a High Availability setup (KI-026576)
  • Fixed a bug that did not execute a configured DNS service change when adding an AuthServe DNS service to Micetro (KI-026108)
  • Fixed the filtering of IP ranges in the Reports module, so the correct filters are applied when reporting on all IP addresses that have the selected attributes or are in the database (KI-025593)
  • Fixed an issue affecting version 11.1.1 that prevented the ability to change the session timeout value if under 20 minutes (KI-026677)
  • Fixed an issue in which DHCP superscopes could not be assigned to a failover relationship (KI-026350)
  • Fixed an issue in which the statuses of MDDS appliances did not update correctly (KI-026405), which fixes a similar issue with DHCP agents (KI-026437)
  • Fixed an issue that did not clear DHCP leases when an active reservation is deleted (KI-026233)
  • Fixed the message provided in the Linux installer when updating the mm-authserve-agent so it now displays the correct path (KI-026301)
  • Fixed an issue that prevented replication of user classes on Microsoft servers when in DHCP failover (KI-026170)
  • Fixed an issue that prevented users from adding Cisco IOS devices to Micetro by enabling all HMAC algorithms supported by libssh (KI-026619)
  • Fixed an issue that prevented users from changing a DNS record in Azure DNS (KI-026607)
  • Meraki scope utilization is now displayed correctly for ranges associated with a single Meraki network (KI-026422)
  • Updated documentation for xDNS redundancy to note that xDNS synchronization does not include SOA records (KI-026436)
  • Updated documentation of XML schemas for change events (KI-026679)
  • Updated the retry strategy for AWS to better conform to AWS best practices
  • Users can now select to download scheduled reports as XML, CSV, JSON, or SYLK files (KI-026389)

Deprecation announcements

Note: When a feature deprecation is announced, the version upon announcement will be the last version in which that feature is officially supported. A feature may continue to work in future versions as long as the code is present within Micetro but this is not guaranteed, as the code is not officially maintained.
  • The GetCloudServiceInfo API method is no longer needed after changes were made for cloud network management and is therefore deprecated.
  • The mmwebext software component has been deprecated. This component was an IIS extension used for single sign-on and was, essentially, a wrapper around mmxmlint.dll. mmwebext is no longer needed, as this functionality is now handled directly within Micetro. Customers that are using an older client that relies on this component should update their API clients accordingly. For reference, a sample Python client can be downloaded here and a PowerShell client can be downloaded here.
  • Support for Python 3.9 has been deprecated, as it reached its end of life in October 2025.
Note: Before updating, we highly recommend deleting the following unsupported cloud types from your Micetro setup:
  • OpenStack: The current implementation in Micetro is outdated and no longer supports modern OpenStack.
  • Dyn: Dyn cloud DNS has reached its end of life and is no longer supported.