Installing Micetro DHCP Agents on Windows - Micetro - 25.2.0

Micetro Installation Guide
ft:locale
en-US
Product name
Micetro
Version
25.2.0
Note: For a list of compatible DHCP servers, refer to Adding a DHCP service.

Micetro DHCP Agent is the DHCP server agent and sits on each DHCP server machine (or in environments using MS DHCP, ISC Kea, Meraki, or cloud servers, on any machine in the network). The DHCP Agent manages the DHCP service on your behalf. Additionally, it handles communication with any cloud providers you are using.

The Micetro components for Windows are provided as exe files/executables consisting of multiple MSI components. The executeable must be installed as Windows Administrator (right-click on the exe file and select Run as Administrator). This extracts the MSI and starts the MSI installer.

The Micetro Agent installer for Windows contains three agents:

  • DNS Agent (Windows service name: Men and Mice DNS Server Controller)

  • DHCP Agent (Windows service name: Men and Mice DHCP Server Controller)

  • Update Agent (Windows service name: Men and Mice Updater)

You can install all components, i.e., all three agents, or select a custom installation, which allows you to select which agent you want to install.

Note: The Update Agent must be installed. For example, when you install the DNS Agent, install the Update Agent at the same time. Otherwise, Micetro will not be able to automatically update.

You can also run the installer executable as Windows Administrator in silent install mode. To do so, run silent install mode with the following parameters:

  • A full installation, including the DNS Agent, DHCP Agent, and Update Agent:
    Micetro_Controllers_x64_<version>.exe /s /v"/qn /L*V C:\temp\controllerInstall.log REBOOT=ReallySuppress ADDLOCAL=DHCP,DNS,Update"
  • A full installation, including the DNS Agent, DHCP Agent, and Update Agent, with runas.exe administrator in a Windows command:
    Note: The c:\temp directory for the controllerInstall.log file must be created before executing the installation.
    runas.exe /user:administrator "Micetro_Controllers_x64_11.0.4.exe /s /v\"/qn /L*V C:\temp\controllerInstall.log REBOOT=ReallySuppress ADDLOCAL=DHCP,DNS,Update\""

    Enter the password for administrator:

    Attempting to start Micetro_Controllers_x64_25.1.2.exe /s /v"/qn /LV C:\temp\controllerInstall.log REBOOT=ReallySuppress ADDLOCAL=DHCP,DNS,Update" as user "WIN-32QTB227IR8\administrator" ...
  • To install only the DHCP and the Update Agents:
    Micetro_Controllers_x64_<version>.exe /s /v"/qn /L*V C:\temp\controllerInstall.log REBOOT=ReallySuppress ADDLOCAL=DHCP,Update"
  • To install only the DNS and Update Agents:
    Micetro_Controllers_x64_<version>.exe /s /v"/qn /L*V C:\temp\controllerInstall.log REBOOT=ReallySuppress ADDLOCAL=DNS,Update"

Example: The following example is a full installation for Micetro version 25.1.2:

Micetro_Controllers_x64_<25.1.2>.exe /s /v"/qn /L*V C:\temp\controllerInstall.log REBOOT=ReallySuppress ADDLOCAL=DHCP,DNS,Update"

All agents are installed as a Windows Service and all services run by default under the Local System account. For information about how to change the account that runs the service, refer to Running Micetro DHCP Agent under a privileged user account.

Note: The installers will not touch the Windows firewall. The necessary ports must be allowed. Refer to Networking requirements for a list of services and their respective ports.

Agent-free installation

For an agent-free installation, in which an Agent is used as proxy to communicate with the Windows service, the Local System account is usually insufficient.

The DNS Agent service (service name: Men and Mice DNS Server Controller) runs under an Active Directory (AD) service account that is member of the DNSAdmins group in AD and is also local administrator on the machine running the agent.

With the Micetro DHCP Agent (service name: Men and Mice DHCP Server Controller), the serivce account typically runs under an AD service account that is member of the AD group DHCP Administrators. If the DHCP server role runs on a dedicated Windows domain member server (not on a Domain Controller), membership to the local DHCP Administrators group for the DHCP servers is required.

The Update Agent can also run on the Local System. Typically, no changes are needed for this agent type.

For more information about agent-free management, refer to Agent-free management of DNS/DHCP servers.

Running Micetro DHCP Agent under a privileged user account

Typically, the Micetro DHCP Agent is installed on one host in an Active Directory (AD) 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. For this to work, the service needs to run as a user that is a member of the Active Directory DHCP Administrators group.

To configure the Micetro DHCP Agent to access DHCP servers on remote computers:

  1. Start the Windows Services program and open the Properties dialog for the Micetro DHCP Agent.
  2. Click the Log On tab. The Local System account radio button is most likely selected.
  3. Click the This account radio button and enter the name and password of a Windows user who is a member of either the Administrators group or the DHCP Administrators group.
  4. Close the dialog and restart the Micetro DHCP Agent service.

If the Micetro DHCP Agent 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 the Micetro DHCP Agent

If Micetro Central is installed on a Windows host, you can install the Micetro DHCP Agent on the same host. If not, then the system must be told where to find the DHCP Agent 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 the Micetro DHCP Agent, such as:

  • For BIND or ISC DHCP, the Agent must be running on the same host as the DNS/DHCP server, including appliances.
  • For Microsoft DNS/DHCP, the Agent must be running on a machine in the same AD Domain as the DNS/DHCP server it controls, and be configured to use credentials that allow control of DNS/DHCP over RPC.
  • For any other service, the Agent can be installed anywhere, as long as you have the correct credentials. Using the agent on the Central host is simple, but if there's a reason that does not work (e.g., it isn't in the domain, there's a firewall blocking RPC/HTTP traffic, etc.), you can install the Agent on a different machine that proxies the communication between Micetro Central and the server.
Note: If you have already installed the DHCP Agent on localhost, make sure it is up-to-date and running. If you cannot update it from within Micetro, you can update using the Micetro Controllers installer.

Managing Cisco IOS with DHCP support

The Micetro DHCP Agent can manage Cisco IOS servers with DHCP support. There's 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 Micetro, the options are similar to those shown when adding an MS DHCP server. By default, if possible, Micetro Central will look for a copy of the DHCP Agent 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 Agent that is on the same network segment as the Cisco IOS server.

Managing cloud services

The Micetro DHCP Agent is also used to create a connection between Micetro and any cloud services you are using, thus allowing Micetro to manage those services.

For more information about managing cloud services in Micetro, refer to Integrating cloud services.

Meraki

With Meraki services, for example, the DHCP Agent creates a connection between Micetro and the Meraki dashboard. The DHCP Agent can be run anywhere as long as it can communicate with the dashboard API. Additionally, the DHCP Agent can be used to connect to multiple Meraki organizations/environments.

All Meraki communication uses HTTPS. Therefore, the DHCP Agent must be installed on a system with up-to-date CA certificates.

Note: The initial Meraki synchronization may take a while to process. The length of time depends on the number of networks and the overall amount of data being synchronized from Meraki into Micetro.