Managing services with Micetro Agents - User Guide - Micetro - 25.2.0

Micetro Admin Guide

ft:locale
en-US
Product name
Micetro
Version
25.2.0

Micetro requires an agent to handle communication with external services. The installation location of the agent depends on the service type and whether it operates on-premises or in the cloud. Agents are installed on the respective machine, the machine running Micetro Central, or any machine with the same domain as the DNS/DHCP servers.

A single agent can manage communication with multiple servers. For more information about agents and how to install them, refer to these topics:

On Windows:

On Linux:

Depending on the service type, you can install the agent on the following hosts:

  • Micetro Central host
  • The service host
  • A different host (for MS DNS/DHCP, ISC Kea, Cisco Meraki, and Cisco IOS services)

The following table defines the agent you can use when adding a service to Micetro, based on the service type:

Host location Services
Existing agents, if you have already added a service of this type
  • AuthServe
  • AWS
  • Azure
  • Cisco IOS
  • Kea
  • Meraki
  • Microsoft DNS
  • Microsoft DHCP
Service host, i.e., the agent installed on the server
  • Kea
  • Microsoft DNS
  • Microsoft DHCP
New agent, to be added when adding a new service
  • AuthServe
  • AWS
  • Azure
  • Cisco IOS
  • Kea
  • Meraki
  • Microsoft DNS
  • Microsoft DHCP
Note: When managing Microsoft DNS servers on remote computers using the DNS Agent, some actions for static zones may not be available, such as:
  • Disabling resource records
  • Enabling resource records
  • Viewing and editing record comments
  • Disabling zones

To perform these actions, you need to install the DNS Agent on the server and use that connection when adding the server.