In Windows Server 2012 and later versions, it is possible to not find the Heart-beat events recorded in the server Event Viewer.
This will cause to have an empty log under the Applications and Services Logs/Mi-Token (Heartbeats) entry, and if present, an empty panel inside the Mi-Token reporting website. The following is a sample screenshot of the Event viewer with no logs for heartbeats:
In order to make these events available, you have to manually enable the event-id 5136.
Verify the Mi-Token Audit Helper service is running:
Open the Local Group Policy Editor by running gpedit.msc
Browse the Computer Configuration tree until you reach the following route:
Computer Configuration/Windows settings/Security Settings/Advanced Audit Policy Configuration/System Audit Policies - Local Group Policy/DS Access
Double click the Audit DirectoryService Changes on the right panel:
Check the Configure the following audit events: box and enable Success and Failure. Click OK when done:
Close the Group policy editor.
Open a CMD window as an administrator and run the following command:
gpupdate /force
Check the Event Viewer once again. You should see the Mi-Token (Heartbeats) being populated.
You should also see the server status panel of the Text Reporting view of the reporting site showing data:
You may opt to use gpmc.msc (Group Policy Management Editor) and follow the same steps.
The general recommendation is to use gpedit.msc instead of gpmc.msc, as gpedit will affect only the local server. If when running gpedit you find the options disabled/grayed, then you will have to use gpmsc.msc with the appropriate domain privileges.