Each component for Microsoft Windows is downloadable separately. For installer files, double-clicking the file will launch the installer using the Windows installer engine. Note that it is also possible to install from the command line using the msiexec command.

Step 1: Install Men & Mice Central

Running Men & Mice Central under a privileged user account

Running Central as a specific service account affects a few functions when it talks to the Active Directory, such as Integrated Security communications with an SQL server database, communications with AD Sites and Services, authentication of AD users, and ability to ping.

When creating a service account for Central, make sure the user is in the local "administrators" group on the Central machine. Otherwise it will not be able to utilize the ping functionality.

Step 2: Install the Men & Mice DNS Server Controller

Active Directory Integrated Zones and Other Dynamic Zones

In order to open a dynamic zone, Men & Mice Suite must read it from the DNS service rather than from a file. The way this is done is via zone transfer. On Windows Server 2003 and later, the zone transfer restriction setting in the zone's options window must be set to allow transfers to an explicit list of IP addresses that includes the server's own address. The default setting of allowing zone transfers to any server listed in the zone's NS records will not suffice.


In some cases, Men & Mice DNS Server Controller will also need to be told specifically which interface to use when requesting zone transfers. If you have trouble opening a dynamic zone after setting the zone's transfer restrictions appropriately, check the Event Log / Application Log for messages from Men & Mice DNS Server Controller. If there is a message indicating that it was unable to get a zone transfer, note the address it tried to use; you can either add that IP address to the transfer restrictions list, or else edit a configuration file for Men & Mice DNS Server Controller.
To configure the DNS Server Controller to use a different address, edit the service's preferences.cfg file on the DNS server computer. The file is located in one of the following two locations, where {Windows} is probably C:\Windows:

If the file does not exist, create it. The file is a text file in a simple XML-based format. Add the following element, replacing the dummy address here with the server's correct network address:

<DNSServerAddress value="192.0.2.1"/> 

Save the file, and then restart Men & Mice DNS Server Controller using "Administrative Tools > Services" in Windows. Then also restart Men & Mice Central, so that it can cache the zone's contents.
Note that for Active Directory-integrated zones, other domain controllers running Microsoft DNS do not need to get zone transfers. This is because the zone data is replicated through LDAP, rather than through zone transfers. Thus, for an AD-integrated zone, the zone transfer restriction list might need only the server's own address.

Running Men & Mice DNS Server Controller under a privileged user account / Server type: "Microsoft Agent-Free"

Normally, Men & Mice DNS Server Controller is installed on one host in an Active Directory forest, or one copy per site. That installation can then manage all MS DNS servers in the forest, or in the site, using Microsoft's own DNS management API. In order for this to work, the service needs to run as a user that has DNS management privileges (i.e. the AD service account must be a member of the DNSAdmins group of the domain).
To configure Men & Mice DNS Server Controller to access DNS servers on remote computers, do the following:

If Men & Mice DNS Server Controller is run as a local system service (the default), then it will only be able to manage the MS DNS service on the same host.

Enable the Generic DNS Server Controller functionality

If the Controller should be configured to run a connector script in order to interface with other DNS servers than the natively supported Windows DNS/Unix BIND DNS, the script interpreter and the connector script must be configured in the controllers preferences.cfg file.
The file is a text file in a simple XML-based format. Add the following element, replacing the dummy script interpreter and script:

<GenericDNSScript value="python /scripts/genericDNS.py" />

Configure the DNS Server Controller to work with Microsoft Azure DNS

For information on configuring Microsoft Azure DNS, seeĀ Configure Azure DNS.

Where to install Men & Mice DNS Server Controller

If Men & Mice Central is installed on a Windows host, then one option is to install Men & Mice DNS Server Controller on the same host. If this is not done, then the system will need to be told where to find the DNS Server Controller when adding a new DNS server to the system. This will be presented as connecting via proxy.


The Men & Mice communication protocol used to control a DNS server is more efficient than the Microsoft protocol. This means that if a DNS server is separated from Men & Mice Central by a slow network link, it is more efficient to install a copy of the Men & Mice DNS Server Controller in the same local network (the same site, typically) as the DNS server.

Men & Mice DHCP Server Controller

Running Men & Mice DHCP Server Controller under a privileged user account / Server type: "Microsoft Agent-Free"

Normally, Men & Mice DHCP Server Controller is installed on one host in an Active Directory forest, or one copy per site. That installation can then manage all MS DHCP servers in the forest, or in the site, using Microsoft's own DHCP management API. In order for this to work, the service needs to run as a user that is a member of the Active Directory DHCP Administrators group.
Please note that for the management of the DHCP failover in Windows Server 2012 R2 the service account must also be a member of the local Administrators group of the DHCP servers in order to be able to fetch/manage the failover configuration.
To configure Men & Mice DHCP Server Controller to access DHCP servers on remote computers, do the following:

If Men & Mice DHCP Server Controller is run as a local system service (the default), then it will only be able to manage the MS DHCP service on the same host.

Where to install Men & Mice DHCP Server Controller

If Men & Mice Central is installed on a Windows host, then one option is to install Men & Mice DHCP Server Controller on the same host. If this is not done, then the system will need to be told where to find the DHCP Server Controller when adding a new DHCP server to the system. This will be presented as connecting via proxy.
However, there are other considerations when deciding where to install Men & Mice DHCP Server Controller.

Managing Cisco IOS with DHCP Support

Men & Mice DHCP Server Controller can also manage Cisco IOS servers with DHCP support. There is no need to install any software on the Cisco device, but it is necessary to create a user account on the device that has the ability to telnet or SSH in. You will be asked for the username and password when adding the server.
When adding a Cisco IOS server to Men & Mice Suite, the options are very similar to those shown when adding an MS DHCP server; by default, if possible, Men & Mice Central will look for a copy of the DHCP Server Controller on the same server as itself, but you can also specify a particular installation to use as a proxy. It is recommended to use a copy of the DHCP Server Controller that is on the same network segment as the Cisco IOS server.

Men & Mice Management Console

Men & Mice Management Console is the primary client application for Men & Mice Suite. It is necessary to initially configure the Suite through this interface; this initial configuration cannot be performed through the command line or web interfaces. Therefore, it is necessary to have this component installed somewhere.

Men & Mice CLI

The archive contains two versions of the documentation for Men & Mice CLI, in both PDF and TXT formats, as well as the program itself. Copy the file mmcmd.exe to somewhere convenient.
If upgrading from version 5.1 or older, note that the new version has a new filename. Update any scripts using the CLI to use the filename mmcmd.exe instead of the old qdnscmd.exe.

Men & Mice Web Interface

The Men & Mice Web Interface for Windows Server requires Microsoft's IIS web server software. If you are using IIS 7, you must install the IIS 6 Management Compatibility and the ISAPI Extensions role services.
The installer will install and configure a small web server module to communicate with Men & Mice Central, as well as the files needed by web browsers to run the Web Interface.