Technical Specifications:
  • Same domain as the user account
  • Windows 2008R2, 2012R2 (64 bit), Windows 2016
  • 1.4 Ghz Dual-Core CPU
  • 1024 MB RAM
  • 20 GB hard disk space.
  • Mi-Token supports the use of virtualization – Vmware, Xen, or Hyper-V.
COMPONENTS FOR WINDOWS 2008 and 2008R2
  • Windows 2008 and 2008R2 are not supported.
COMPONENTS FOR WINDOWS 2012 and 2012R2
  • Network Policy and Access Services role with the Network Policy Server
  • Active Directory Lightweight Directory Services role
  • .NET Framework 4.5
COMPONENTS FOR WINDOWS 2016, 2019, 2022, 2025
  • Network Policy and Access Services role with the Network Policy Server
  • Active Directory Lightweight Directory Services role
  • .NET Framework 4.6

Mi-Token must be installed in a Windows Server installation that was created from scratch via ISO. Mi-Token does not work with pre-built, pre-configured images of Windows Server.

Please take into consideration that when building a replica server it is not possible to go from Windows Server 2016 to Windows Server 2022 or 2025 directly, there is an incompatibility issue in AD LDS. The replication must be performed from 2016 to 2019, and then from 2019 to 2022 or 2025 indistinctively.


Note that when installing Mi-Token on a domain controller or member server, domain administrator rights are necessary.

Firewall Configuration:

  • Between remote access device and RADIUS servers, UDP 1812 (RADIUS)
  • Between management PCs and RADIUS servers
  • ADAM/LDS LDAP ports
  • Between replicating RADIUS servers
  • ADAM/LDS LDAP ports
  • RPC endpoint mapper (TCP 135)
  • Dynamic RPC ports (TCP 1024-65535 by default although configurable)